This is a regression of an old bug wherein if a branch was deleted or renamed and another user was on it, the user can’t perform operations anymore
Attempting to switch a commit or branch in my GUI client gives me a dialog saying “An unexpected error has occurred.”:
On the command line a switch gives the following output:
> cm switch cs:10303
Searching for changed items in the workspace...
Error: Object reference not set to an instance of an object.
Refreshing in pending changes does this:
My solution to this is very low level and I have to edit the .plastic/plastic.selector file directly and change smartbranch to the new name. I’m assuming changing this to /main or something in the case of a deleted branch would at least allow the tooling to work well enough to get back to a good commit (though I haven’t tried it)
Allowing another user to perform operations that completely wedge users is less than ideal.
