You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having a node that was interrupted with interrupt and then resumed with Command(resume=...), when start with that checkpoint again and try to resume with a different value, the new value won't apply.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Problem
Having a node that was interrupted with
interrupt
and then resumed withCommand(resume=...)
, when start with thatcheckpoint
again and try to resume with a different value, the new value won't apply.Minimal example:
Output i expect:
What i get:
Curiously enough the checkpoint after second resume contains following
pending_writes
:Don't know what that means exactly. But apparently the first
__resume__
somehow sticks.Am i doing it wrong? What are the cleanest way to work it around?
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions