As of commit a7351df the connect command adds the requested computer to the context's connectionChain, but the change is not reflected anywhere outside of that command's execution run.
Subsequent runs do not reflect the changes either. Changes are lost after the command completes execution.
This could be caused by the worker handling the command being separate from the server with the context variable, or the ws variable being deep copied somewhere vs shallow copied, or all these could be wrong.
Most likely, the solution here is to make a service around interacting with the context.
As of commit a7351df the connect command adds the requested computer to the context's connectionChain, but the change is not reflected anywhere outside of that command's execution run.
Subsequent runs do not reflect the changes either. Changes are lost after the command completes execution.
This could be caused by the worker handling the command being separate from the server with the context variable, or the
wsvariable being deep copied somewhere vs shallow copied, or all these could be wrong.Most likely, the solution here is to make a service around interacting with the context.