fix(sdk): prevent stale client closure in useStream hook#1895
Open
sivashankar0398-cmyk wants to merge 1 commit intolangchain-ai:mainfrom
Open
fix(sdk): prevent stale client closure in useStream hook#1895sivashankar0398-cmyk wants to merge 1 commit intolangchain-ai:mainfrom
sivashankar0398-cmyk wants to merge 1 commit intolangchain-ai:mainfrom
Conversation
|
| if (options.passthrough) return Promise.resolve([]); | ||
|
|
||
| const client = clientRef.current; | ||
| const key = getFetchHistoryKey(client, threadId, limit); |
Member
There was a problem hiding this comment.
Is this still needed then?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #1840.
This change prevents the
useStreamhook from capturing a stale client referenceafter a token refresh. The callback is now updated when the client configuration
changes, ensuring fresh authentication is always used and avoiding 403 errors.
Tests: