Use a single code server

[dpeng817]

Summary & Motivation

How I Tested These Changes

Changelog

Insert changelog entry or delete this section.

[dpeng817]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• Use a single code server #26818 👈 (View in Graphite)
• Use code server start in process context use cases #26816
• [single-grpc-server][rfc] introduce a heartbeat to proxy server #26777
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[gibsondan]

i think I put this on sean's original PR too - the main downside I see after this change is that if the proxy server process crashes, there is nothing that will detect that and restart it now. Before, if that happened, you could reload things from the webserver UI, and the daemon was restarting every 60 seconds anyway.

I'm not sure if that is a blocking concern or not, but I do know that there are some people who use 'dagster dev' in a non dev context, for better or worse, and that change in behavior could affect them. One possibility would be to make this new thing opt in or opt out in some fashion. Another would be to add something that monitors the proxy server process and restarts it automatically on the same port if that is detected.