ops can not be used as a config entry in place of solids in the Playground run config

Summary

Release 0.12.4 added:

ops can now be used as a config entry in place of solids.

It works in config you provide in the code, but not in the Playground run config.

Reproduction

Simple example test_ops.py:

from dagster import op, graph, repository


@op
def op1(context, input1: int):
    context.log.info(f"Ran for {input1}")


@graph
def graph1():
    op1()


@repository()
def repo1():
    job1 = graph1.to_job(config={"ops": {"op1": {"inputs": {"input1": 12}}}})
    return [job1]

Run: dagit -f test_ops.py

The “Launch Execution” button remains gray and this error is displayed:

Received unexpected config entry “ops” at the root. Expected: “{ solids?: { op1: { config?: Any inputs: { input1: (Int | { json: { path: String } pickle: { path: String } value: Int }) } outputs?: [{ result?: { json: { path: String } pickle: { path: String } } }] } } }”.

Workarounds:

• leave the Playground run config blank so it uses the one from the code
• replace ops with solids in the Playground run config.

---

Message from the maintainers:

Impacted by this bug? Give it a 👍. We factor engagement into prioritization.

[dpeng817]

Hey @NicolasPA, apologies for the thrash. You are correct that default config should be showing up in the playground for the job.

Turned out to be a bug in the default config buildup; after resolving, the default config no longer errors from the playground, as expected:

Thanks again for surfacing! A fix should be out for next release.

One thing to note, an unfortunate side affect of allowing for both config entries is that (for now), config errors related to op config are surfaced in terms of solid.

[dpeng817]

Closed by https://github.com/dagster-io/dagster/commit/3751d986cf7025997044b4e813ce36be7df50dd4