You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When executing a node-migration to change the nodeType of a NodeAggregate, a workspace with a uuid-like name is left behind. After switching the current workspace to this workspace, it is not possible to switch the base workspace back to "live".
The request to https://neos.ddev.site/neos/ui-services/change-base-workspace simply times out and nothing happens.
There are no exceptions thrown and no log-entries appear.
Expected Behavior
After running a node-migration, the changes should be published to the live workspace and the temporary import-workspace should be discarded.
Changing into a workspace should not cause a user to be stuck on this workspace.
It seems as if there is a while condition in WorkspaceCommandHandler::requireNonCircularRelationBetweenWorkspaces that doesn't seem to terminate when I try to change back to the live workspace.
I additionally tried testing this by creating another internal workspace and switching to this workspace but this fails in the same manner. I don't know however if this happens because the "import" workspace that I initially changed to is broken in some way.
Furthermore, apparently this leaves a user in a broken state, I can't change back to the live workspace, I can't change into any other workspace and also I can't delete my user workspace and recreate it, essentially breaking my user permanently.
Is there an existing issue for this?
Current Behavior
When executing a node-migration to change the nodeType of a NodeAggregate, a workspace with a uuid-like name is left behind. After switching the current workspace to this workspace, it is not possible to switch the base workspace back to "live".
The request to
https://neos.ddev.site/neos/ui-services/change-base-workspace
simply times out and nothing happens.There are no exceptions thrown and no log-entries appear.
Expected Behavior
After running a node-migration, the changes should be published to the live workspace and the temporary import-workspace should be discarded.
Changing into a workspace should not cause a user to be stuck on this workspace.
Steps To Reproduce
No response
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: