A few questions: 1. I'm getting a heartbeat timeout because I'm creating ~10M static partitions on start-up (take about 30 seconds and the default heartbeat timeout is 20 seconds). I run my dagster with

dagster dev

- is there a way to specify the heartbeat in some config. Maybe

dagster.yaml

? 2. I have the

dagster.yaml

in my code repo and I have a

pyproject.toml

with this section

[tool.dagster]
module_name = "redacted.redacted"

would it be possible to specify the dagster.yaml path here so I don't have to rely on ensuring the developer copied it into their DAGSTER_HOME dir?

Hi Nima - i want to make sure we are talking about the same heartbeat, can you share the error message that you're seeing? You can increase the amount of time dagster will wait for your code to load here: https://docs.dagster.io/deployment/dagster-instance#grpc-servers That said, I'm not sure its advisable to have a lot of side effects that run whenever your dagster code is loaded, because your definitions are also loaded every time a run starts (and in many cases every time an op starts) - maybe what you're describing could be a separate script that runs before 'dagster dev' runs? for 2 - this is not currently possible, maybe you could have a helper script that the developer runs that sets the env var locally and then runs 'dagster dev'?