Fix disconnected stream retention#683
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
1 participant
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.
Summary
Fixes memory retention after clients disconnect from long-running web LLM streams.
DeepSeek V4 Flash streams now cancel immediately on disconnect and intentionally skip billing because that model is cheap and free-mode only, while OpenRouter streams keep draining until fallback billing is possible before cancellation.
Limited free-mode provider errors omit full message payloads from telemetry to reduce memory and log pressure.
Validation
bun run --cwd web typecheckgit diff --checkbun run --cwd web test --testPathPattern=deepseek-image-compat