19913d85-f662-4518-a9a1-7adc1793dfd4.png){kind=small}
Channels
dagster-de
dagster-cube
gigs-freelance
dagster-wandb
dagster-machine-learning
dagster-bigquery
tools
dagster-dask
dagster-snowflake
dagster-releases
data-platform-design
events
dagster-serverless
dagster-noteable
introductions
dagster-airflow
dagster-cloud
random
dagster-dbt
faq-read-me-before-posting
dagster-airbyte
dagster-spatial
dagster-support
announcements
github-discussions
豆瓣酱帮
dagster-feedback
dagstereo
dagster-ecs
dagster-kubernetes
jobs
dagster-showcase
Title
f
Fraser Marlow
05/17/2023, 2:54 AMhttps://dagster.io/blog/surfacing-errors
❤️ 6
:dagster: 2
m
Mark Fickett
05/17/2023, 1:19 PMThanks! Investments like this in the dev experience with Dagster are a big part of what makes it great.
:next-level-daggy: 1
Typo: "If it detects that the run has moved into a problematic, it ..." maybe "problematic state"?
🙏 1
f
Fraser Marlow
05/17/2023, 3:10 PMHa ha, yeah - Grammerly was insisting on “moved into a problem…“.
Thanks for the head’s up - let me check with the author - I think this was intentional, but I will ask him.
d
daniel
05/17/2023, 4:35 PMsorry, my grammar skills moved into a problematic
😂 1
m
Mark Fickett
05/18/2023, 7:13 PMThe blog post says these should be visible in the 1.3 release. We're on Dagster Cloud hybrid, and are running v1.3.4 in our agent and code location, but I still got a generic error when some pods got evicted for DiskPressure (failed health check: Discovered failed Kubernetes job etc). Should I be seeing the cool new error messages / what other info can I provide?
d
daniel
05/18/2023, 7:14 PMThe main places it's in place now in hybrid are on issues with code locations starting up
still on my list to add it to run failures, then step failures
m
Mark Fickett
05/18/2023, 7:15 PMAh, OK. I'll look forward to it then!