Namespace prefix 'beh' is not defined error

[ChucklesOnGitHub]

I was working on a file in Bonsai 2.9 yesterday and today I cannot open it, the error is this one:

Would you be able to let me know how I can recover the workflow please? Here is the file:
behavior_inputexpander.zip

I've also had this issue with other files that worked fine in Bonsai 2.8.5 and stopped working in either once I attempted to open them in Bonsai 2.9

Thank you

[banchan86]

Hi @ChucklesOnGitHub seems like the namespace prefix declarations beh for Harp.Behavior was somehow dropped from the .bonsai workflow XML file. I am not sure if this is the right way to solve it (since there are now duplicate namespace prefix entries for Harp.Behavior) but adding it back fixed it.

behavior_inputexpander_fixed.zip

If this error happens in the future, I think you can open the workflow file in a code editor like Visual Studio Code, look for the section at the top that looks like this:

<WorkflowBuilder Version="2.9.0"
                 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                 xmlns:rx="clr-namespace:Bonsai.Reactive;assembly=Bonsai.Core"
                 xmlns:harp="clr-namespace:Bonsai.Harp;assembly=Bonsai.Harp"
...

And add in the missing reference (if you don't know what the missing reference is, you can create a separate bonsai workflow file, add a node from the package, save the file and check the namespace declaration).

I think this might be a bug (maybe something during the workflow upgrade process?), so if you can reproduce the steps leading up to the error with one of those other files that you mentioned and attach a description/the file that would help us track it down!

[ChucklesOnGitHub]

Thanks, this is just what I needed. I repeated the procedure with the other corrupted files and fixed them.
I made the edit:

And after saving it the references sorted themselves out and I had no further issues.

I couldn't reproduce what lead to this, but I think all of these used the Spinnaker node which I was playing around with. I have to have these functional for now so I can't try to break them intentionally atm to try and provide more info, sorry.