Channels
dagster-de
topic-async-execution
dagster-jp
dagster-cube
gigs-freelance
dagster-wandb
dagster-feedback
dagster-machine-learning
dagster-bigquery
dagster-support
dagster-dask
dagster-snowflake
dagster-releases
dagster-dbt
faq-read-me-before-posting
tools
dagster-pipes
project-flexible-range-backfills
data-platform-design
events
dagster-serverless
dagster-noteable
introductions
dagster-airflow
dagster-cloud
random
dagster-airbyte
dagster-spatial
announcements
github-discussions
豆瓣酱帮
dagstereo
dagster-ecs
dagster-kubernetes
jobs
dagster-showcase
data-quality-asset-checks
Powered by
#announcements
Title
s
schrockn
12/05/2018, 1:22 AM
@Ben Gotow
there seems to be a regression in the config editor. contexts refuse to autocomplete
it blames to a865cbc6d4bbc196329ea7d3bc6134f9e6e09c28
b
Ben Gotow
12/05/2018, 4:13 PM
hmm this is working fine for me on master - what pipeline is this?
s
schrockn
12/05/2018, 4:21 PM
@Ben Gotow
allscripts_fileload pipeline
you don’t have access to it
b
Ben Gotow
12/05/2018, 4:22 PM
hmm I’d look at the graphql response and see what the schema looks like
it’s also possible it’s underlining line 1 because of missing keys in the root dict
that’s the new behavior
Post