gibsondan
gibsondan
I think https://github.com/dagster-io/dagster/pull/22016 and https://github.com/dagster-io/dagster/pull/22014 is the play here instead
I've seen this error happen when a run fails at the very end, after every step has been completed, and you try to retry it (so the retry doesn't actually...
Re: "bans using the object like a plain tuple (iteration and [] access)" - is that something we could make toggleable somehow? I agree the default should be banned, i...
Could https://github.com/dagster-io/dagster/pull/22267 (which went out in 1.7.10) have somehow caused this? The intention there was to change the formatting of warnings, not the frequency, but I’m wondering if it has...
linking the similar report in https://github.com/dagster-io/dagster/discussions/22460 for context
Hi @jobicarter - thanks for sending this out. I think the use case here is 100% reasonable, but the other angle that I'd like to explore with here is what...
to start, what do you think about splitting the addition of the START_TIMEOUT failure reason into its own smaller PR? That seems totally uncontroversial and would open up some of...
I can take a look, sure - this actually does not show up in my graphite queue though since jamie already accepted the PR
when you say “set via the UI” - which screen are you referring to? The NUX when you add a new code location? On Mon, Jun 24, 2024 at 1:41 ...
You don’t need to use the UI at all to add a new code location (in either serverless or hybrid). If you create a new GitHub repo and follow the...