[v6.0] fix(ai): tag step/chunk timeout aborts with TimeoutError reason#16803
Merged
Conversation
Manual backport of #14943 to release-v6.0: step and chunk timeouts previously called abort() with no reason, so consumers could not distinguish timeouts from user aborts. Introduces the self-contained setAbortTimeout util that aborts with a TimeoutError DOMException, matching AbortSignal.timeout(ms). Tests adapted to v6 (MockLanguageModelV3). (cherry picked from commit 47e65d6079913b0e96eddea7cae1a02fddda109c)
gr2m
added
the
backport
github-actions
Bot
removed
the
backport
Contributor
|
|
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
2 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.
Manual backport of #14943 to
release-v6.0(the surrounding stream-text/generate-text code diverged, so the hunks were applied by hand; the newsetAbortTimeoututil and its tests came over verbatim). Step/chunk timeouts now abort with aTimeoutErrorDOMException— matchingAbortSignal.timeout(ms)— instead of an undefined reason. Tests adapted to v6 (MockLanguageModelV3); 551 tests across the three touched test files pass locally.Part of the v6.0 backport tracking issue #16767.