The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

Does the daemon responsible for the code-location when running `dagster dev -m ...`  intentionally periodically refresh? i notice the logs keep repeating as if the code location is being refreshed, is there any way to suppress this to only refresh when user explicitly requests a reload (e.g. via the UI)

hey <@U04JLJC7FGU> what logs are you seeing repeated?

Essentially
```2023-03-22 08:02:55,285 INFO [api.py:742] Started Dagster code server for module code_locations in process 78498```
There is a good amount of processing that happens to generate the assets in our `Definition`(which ideally only happens once) and i can see all the logs associated with that also repeating after the above line

ok cool. checking with the team to see if this in intentional or a bug

Hey Clement - you can control this more explicitly by running your own gRPC server separately: <https://docs.dagster.io/concepts/code-locations/workspace-files#running-your-own-grpc-server>

Then dagit and the daemon will access that server, and you can choose when to shut it down and restart it - but if you don't do that, there isn't currently a way to manage the reload behavior

I see so in this case do i also need to the spin up dagit and the dagster-daemon separately myself or can i still use the `dagster dev` and configure it somehow, though i don't really see an option so maybe not

You can still use dagster dev with a workspace.yaml file