Note: this was using the interactive window
Step 1: Set to local server start up
Step 2: Start up Interactive Window connect to a kernel (I used 2.7 since that was only on this machine)
Step 3: Set remote server to my Mac machine
Step 4: Execute something in the input box of the interactive window
Result:
Jupyter server has updated from local to the address of my mac machine. But the kernel next to it is still my windows box local 2.7 kernel, and I'm still on my windows machine.
Unfortunately I still (inspite of the detailed steps) don't understand the issue, sorry.
@DonJayamanne . The text next to "Jupyter Server" was (before my change) being pulled from the Jupyter URI VS Code setting, not from the current connection. So if you started up a session and made a location connection, then changed the jupyter URI setting to a remote URI, then executed code that "Jupyter Server" text would update to the remote URI. However you are still in the local connection session. So the text was incorrect. I changed it to pull the text from the currently active connection instead of the setting. Does that explain it better?
Yup, in that case validated.
Thanks for the clarification.
Most helpful comment
@DonJayamanne . The text next to "Jupyter Server" was (before my change) being pulled from the Jupyter URI VS Code setting, not from the current connection. So if you started up a session and made a location connection, then changed the jupyter URI setting to a remote URI, then executed code that "Jupyter Server" text would update to the remote URI. However you are still in the local connection session. So the text was incorrect. I changed it to pull the text from the currently active connection instead of the setting. Does that explain it better?