Is anyone having problems running `dagit` with the...
# announcements
c
Is anyone having problems running
dagit
with the
โ€“path-prefix
option to set a different root path than
/
? The "Playground" tab of the pipeline view that would let me edit the config and launch a run fails with a blank page in the browser (Firefox or Safari), and I see the errors in the screenshot in browser console. It looks like the path prefix doesn't take for the static resources, and the browser makes requests to
/static/css/...
and
/static/js/...
paths. This is on Dagster
0.10.5
and with the non-empty prefix
/pipelines
.
a
I can repro locally doing
dagit --path-prefix foo
and navigating to the playground cc @dish
d
Ack, ๐Ÿ‘€
a
thanks for the report, definitely a real issue. We expect to have a fix in for the release on Thursday.
0.10.0
does not have the problematic change, so you could try that
๐Ÿ‘ 1
d
Opened https://github.com/dagster-io/dagster/issues/3696 to track the issue, pushing up a fix now. Thanks for the report!
c
Sounds great, thx for quick help!
d
Just following up โ€” this is fixed in 0.10.6 ๐Ÿ™‚