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
When a graph doesn't have a checkpointer set and a node interrupts, we should throw a useful error.
Current behavior
Repeated calls to invoke or stream behave as though the graph was interrupted with a checkpointer present. It's only if the user happens to call getState to check for interrupts (not included in our examples/docs, IIRC) that they'll see a helpful error (No checkpointer set.).
The text was updated successfully, but these errors were encountered:
Problem
Interrupts only work when a checkpointer is set.
Expected behavior
When a graph doesn't have a checkpointer set and a node interrupts, we should throw a useful error.
Current behavior
Repeated calls to
invoke
or stream behave as though the graph was interrupted with a checkpointer present. It's only if the user happens to callgetState
to check for interrupts (not included in our examples/docs, IIRC) that they'll see a helpful error (No checkpointer set.
).The text was updated successfully, but these errors were encountered: