Thanks! Investments like this in the dev experience with Dagster are a big part of what makes it great.
Typo: "If it detects that the run has moved into a problematic, it ..." maybe "problematic state"?
05/17/2023, 3:10 PM
Ha 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.
05/17/2023, 4:35 PM
sorry, my grammar skills moved into a problematic
05/18/2023, 7:13 PM
The 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?
05/18/2023, 7:14 PM
The 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