So I'm trying to manually raise a `RetryRequested`...
# ask-community
z
So I'm trying to manually raise a
RetryRequested
exception from within a custom
StepLauncher
and it seems to be able to submit retries for the step it's launching just fine, but I noticed that the op's
context.retry_number
doesn't seem to get incremented. Is this expected when raising
RetryRequested
from within a
StepLauncher
instead of an op?
🤖 1
a
could you file an issue? This sounds like an somewhat unsurprising bug. Step launchers have a separate init path which can cause desync issues like this
z
sure thing!
a
a custom StepLauncher
actually, could be an impl issue in your custom launcher, here is the line where that information threads through: https://github.com/dagster-io/dagster/blame/master/python_modules/dagster/dagster/core/execution/plan/external_step.py#L275
z
hmm that does look promising, I'll dig into that and let you know if that seems to be it
thanks!