does a dagster local deployment auto-reload when code in the workspace has changed?

In a local Dagster deployment, the behavior regarding auto-reloading when code in the workspace has changed can vary depending on how you are running Dagster. If you are running Dagster locally using

dagster dev

, Dagster typically manages your code servers as subprocesses, and pressing the "Reload" button on the Code Locations tab in the Dagster UI will start a new code server and reload your code. This allows you to reload definitions without needing to restart the whole server. However, if you are running your code servers separately using the

dagster api grpc

command, the only way to reload your definitions is to restart the process, which typically requires restarting the container or pod on which it is running. In this case, pressing the "Reload" button in the Dagster UI does not actually reload your code. Starting from the dagster 1.3.6 release, an experimental

dagster code-server start

command was added that can be used instead of

dagster api grpc

and has identical arguments. This new command runs user code in a subprocess and proxies API calls from Dagster system components to that subprocess. When running this command, pressing "Reload" from the Code Locations tab in the Dagster UI will restart the subprocess, allowing you to reload your definitions without needing to restart the whole server. For more details on how to set up and use these features, you should refer to the Dagster documentation and the specific version notes to ensure compatibility with your deployment.