Repository navigation
Paginate controller details and preserve complete ZIP exports - #19
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
Large jobs currently load every detail row when the controller opens. Start files, content nodes, work items and events at 50 rows each, with stable timestamp/UUID or sequence/UUID cursors, exact totals, independent Load more/retry and refresh/job-switch guards. ZIP actions collect every matching stored-file page before signing/downloading; cached old clients receive reload guidance to prevent partial exports.
Generated PostgreSQL fixtures preserve all IDs across ties and microseconds. A 2,000-row-per-section fixture reduced the initial serialized response from 3,701,322 to 65,901 bytes (98.2%); typed query plans use existing indexes, so no migration is included. Six-language copy and current handovers are updated; blogs/visuals and backend/cron/retention settings are unchanged.
Validation: all seven GitHub CI jobs passed, including all 278 frontend tests and production build. Locally, 276/278 frontend tests passed in the sandbox; the two temporary-Git tests passed on an elevated rerun after config-write failures. Twelve focused service/transport/route/React/export/tree checks, lint, dictionary/SQL/blog consistency, local production build and whitespace checks passed.
Resolve the Vercel Google-font loader failure by bundling the exact existing 16 WOFF2 assets, preserving all 25 face declarations, subsets, weights, fallback metrics and three Latin preloads. Versioned local URLs retain immutable caching; official licenses and integrity tests accompany the assets. No framework upgrade, extra runtime dependency or blog source/visual change is included. Clean local build with invalid HTTP proxies and 13 focused tests passed; updated CI passed all seven jobs and 279 frontend tests/build before and after merge. The corrected Vercel preview and all six production statuses passed.
Released frontend revision:
efbeab60026b0e77a71a3d16822d81bbe6f81f2b. Authenticated production traversal matches every baseline ID: 73 nodes (initially bounded to 50), four files, one work item and two events. All four ACTIVE files were signed/fetched and reopened in a complete assembled ZIP. Expected 401/409/400 responses/private headers, all 16 font hashes/cache headers, local preloads/CSS and 20 public HTTP checks passed; uncached wake returned 2/2 in all pools. One generated baseline job retains normal 48-hour retention. Native browser layout, destructive admin/cleanup and backend revision/capacity acceptance remain separate.