Repository navigation
fix(api): stream large request timelines without expanding JSON - #1376
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Oct 16, 2026
This branch was successfully deployed
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.
The full timeline endpoint runs out of Vercel function memory for the newly ingested c6656 point because it expands the complete timeline, caches another JSON copy, and serializes it again for the response.
Stream current stored gzip timelines directly in bounded database reads, preserving the complete JSON response and existing cache headers. Keep the existing fallback for older timelines and stop reading when the client disconnects.
Follow-up to #1375. The production ingestion succeeded; this fixes serving those complete timelines without another ingestion or benchmark run.
Verified the deployed preview against the real c5120 and c6656 production records: both timeline requests return HTTP 200, preserve the exact stored gzip bytes (SHA-256 and CRC checked), and contain all 665,379 and 856,543 requests respectively. The full downloads completed in 2.1s and 2.8s. c5120 preview endpoint · c6656 preview endpoint.
Browser integration run passed in Chrome and Firefox.