Checkpointer creates individual subset of steps for every flow under same thread

[KannanDhandapani-Moodys]

I'm not able to recollect which version this was broken, but in previous version's checkpoints table starts with step -1 and for same thread, checkpoint_ns and the step in incremental order and do continuous increment for this combination. with recent version I see for every question even with same thread and namespace it always resets to -1 and starts with -1 for each question I post. checkpointer reset the step value with latest version.

1. what was the reason this implementation was changed ?
2. do we have any plan to bring the threads in incremental order so steps will start with -1, 0, 1,2,3.... n ?
3. can we get which version of langgraph, langgraph-core, langgraph-checkpoint it was broken ?

[nfcampos]

Can you confirm whether checkpoint_ns is the same for all checkpoints in your screenshot? It's grayed out so I can't see

[hinthornw]

Could you try omitting the checkpoint_ns? It isn't intended to be passed in externally, and it certainly shouldn't be an email or arbitrary string

[KannanDhandapani-Moodys]

ok @hinthornw , but we need the checkpoint-ns to isolates the thread initiated by users so they can get their thread list and load all their thread histories using it.

[KannanDhandapani-Moodys]

@hinthornw this checkpoint_ns was working with simple string or email and also checkpoint documentation states that checkpoint_ns is used to segregate the under one set of activities. (corrected from threads by user account or application etc to "under one set of activities.") .

in previous version when we persist namespace like below it used to work
[email protected]
{orgname}.{applicationname}.{userid} format ex: google.chrome.kannan

1. what is the use of checkpoint_ns if its not indented to this ?

[nfcampos]

Where does the documentation state checkpoint_ns is to be used for segregating threads per user? This is not true, and has never been true. checkpoint_ns is used for checkpointing subgraphs. To segregate threads per user please use metadata, which you should be able to filter on in postgres easily enough.

[KannanDhandapani-Moodys]

sure @nfcampos I corrected my previous statement not intended to say like by user account, was trying to say like under keep group of threads under one subset and can't namespace can be used? and it was working with older version even after we filled up checkpoint_ns either with simple string or any format.
but nevertheless we pushing those information into "metadata" we will use that for filtering and ll leave checkpoint_ns empty.

Just curious how and when this "checkpoint_ns" will be filed up and by what node etc? so in future will try to utilize if any use cases arise. thanks!