Hi Everyone! I am getting strange error while setting up concurrency configurations: dagster.yaml

scheduler:
  module: dagster.core.scheduler
  class: DagsterDaemonScheduler


run_coordinator:
  module: dagster.core.run_coordinator
  class: QueuedRunCoordinator
  config:
    max_concurrent_runs: 25
    tag_concurrency_limits:
      [
        { key:"test", value:"two", limit:2 }
      ]

While running the program it says following:

raise DagsterInvalidConfigError(
dagster.core.errors.DagsterInvalidConfigError: Errors whilst loading configuration for {'max_concurrent_runs': Field(<dagster.config.config_type.Int object at 0x7fd295c8ea30>, default=@, is_required=False), 'tag_concurrency_limits': Field(<dagster.config.config_type.Noneable object at 0x7fd29b096dc0>, default=@, is_required=False), 'dequeue_interval_seconds': Field(<dagster.config.config_type.Int object at 0x7fd295c8ea30>, default=@, is_required=False)}.
    Error 1: Received unexpected config entries "['key:"test"', 'limit:2']" at path root:tag_concurrency_limits[0]. Expected: "['key', 'limit', 'value']."
    Error 2: Missing required config entries "['key', 'limit']" at path root:tag_concurrency_limits[0]".
    Error 3: Received unexpected config entries "['key:"test1"', 'limit:5']" at path root:tag_concurrency_limits[1]. Expected: "['key', 'limit', 'value']."
    Error 4: Missing required config entries "['key', 'limit']" at path root:tag_concurrency_limits[1]".

I am using the exact syntax based on docs: https://docs.dagster.io/overview/pipeline-runs/limiting-run-concurrency#main

This is strange. Could you try copying the exact config block from the docs just to sanity check

Hi Waqas - try this instead:

run_coordinator:
  module: dagster.core.run_coordinator
  class: QueuedRunCoordinator
  config:
    max_concurrent_runs: 25
    tag_concurrency_limits:
      - key: 'test'
        value: 'two'
        limit: 2

This is likely a formatting issue in the docs, we'll fix that up or make sure the example there works.

I ran into the same problem, there needs to be spaces after the colons when defining key, value and limit:

Thanks both, fixing the issue on the docs.

Thanks @Cameron Gallivan it worked for me.