Repository navigation
fix: enforce provider cooldown and preserve transport failures - #351
Merged
Merged
Conversation
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
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.
Queued provider calls could bypass a sibling's rate-limit cooldown, and a producer failure could replace an earlier concurrent task failure. Publish cooldowns before releasing capacity, recheck extended cooldowns after queueing, and propagate the execution scope's first failure.
Errored SSE readers now propagate their transport error without misclassifying
cancel()'s stored stream error as a cleanup timeout. AddcreateJsonRequestso embedding hosts can reuse the same full-response retry, deadline, cancellation and retained-capacity policy. JSON parsing and business validation failures do not trigger transport replay.Validation: 44 runtime regression tests; full workspace regression (228 files, 1537 passed, 4 skipped); workspace lint, typecheck and format checks; workspace build; standalone package installation smoke. The private host's 16 LLM/embedding adapter tests also pass under Node 22 using the current runtime build.