-
|
I stored the thread_id in the State and had some assertions to check whether the thread_id somehow got changed. Now they are causing some AssertionErrors. Not really a big deal though. just interested in why this change is made. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
@Glinte the thread ID should not change for the parent graph. node name is appended to thread ID only for nested graphs, this is needed for using the same checkpointer with nested graphs (as part of the nested graph interrupt / resume functionality we're working on) |
Beta Was this translation helpful? Give feedback.
-
|
@vbarda the thread id is actually changed if you check it in the node right now (not just if you enter a nested graph) fwiw. Leads to some issues if you are using this in your own code that makes assumptions on it being a valid uuid (like if you had been using it as a foreign key in a db or storing it in some external state) |
Beta Was this translation helpful? Give feedback.
-
|
ah, i see. definitely need to look into it! |
Beta Was this translation helpful? Give feedback.
-
|
@Glinte this should be fixed in |
Beta Was this translation helpful? Give feedback.
@Glinte the thread ID should not change for the parent graph. node name is appended to thread ID only for nested graphs, this is needed for using the same checkpointer with nested graphs (as part of the nested graph interrupt / resume functionality we're working on)