Got an 0.7.13 -> 0.8.5 upgrade issue I'm scratching my head over. Getting a 2m hang and then this error when I try to execute a pipeline from dagit's web UI:

dagster.core.errors.DagsterLaunchFailedError: Host <http://127.0.0.1:9090> failed sanity check. It is not a dagit server.
  File "/usr/local/lib/python3.7/site-packages/dagster_graphql/implementation/utils.py", line 14, in _fn
    return fn(*args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/dagster_graphql/implementation/execution/launch_execution.py", line 19, in launch_pipeline_execution
    return _launch_pipeline_execution(graphene_info, execution_params)
  File "/usr/local/lib/python3.7/site-packages/dagster_graphql/implementation/execution/launch_execution.py", line 49, in _launch_pipeline_execution
    run = do_launch(graphene_info, execution_params, is_reexecuted)
  File "/usr/local/lib/python3.7/site-packages/dagster_graphql/implementation/execution/launch_execution.py", line 40, in do_launch
    pipeline_run.run_id, external_pipeline=external_pipeline
  File "/usr/local/lib/python3.7/site-packages/dagster/core/instance/__init__.py", line 964, in launch_run
    return self._run_launcher.launch_run(self, run, external_pipeline=external_pipeline)
  File "/usr/local/lib/python3.7/site-packages/dagster_graphql/launcher/__init__.py", line 80, in launch_run
    self.validate()
  File "/usr/local/lib/python3.7/site-packages/dagster_graphql/launcher/__init__.py", line 74, in validate
    host=self._address

My dagster.yaml config:

run_launcher:
  module: dagster_graphql.launcher
  class: RemoteDagitRunLauncher
  config:
    address: "<http://127.0.0.1:9090>"

dagit:
  execution_manager:
    disabled: False
    max_concurrent_runs: 4

This worked fine before on 0.7.13.

ya

0.8.0

had a number of significant changes , https://github.com/dagster-io/dagster/blob/master/CHANGES.md and https://github.com/dagster-io/dagster/blob/master/080_MIGRATION.md worth peaking at if you haven’t yet

Yeah, been working thru that doc. I’ll try to clear those settings and report back if didn’t help, thanks!

Sounds good, the

max_concurrent_runs

queueing is gone temporarily (working on adding it back) but otherwise I would expect the new default run launcher to work just fine for you. Let me know if you have any issues.

....was this accidentally sent?

Yes sorry