[codex] Move tx history backfill commits#85
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Coverage report
Show new covered files 🐣
Show files with reduced coverage 🔻
Test suite run success933 tests passing in 168 suites. Report generated by 🧪jest coverage report action from 23bdc28 |
📦 Next.js Bundle Analysis for eternalsafe-walletThis analysis was generated by the Next.js Bundle Analysis action. 🤖
|
| Page | Size (compressed) |
|---|---|
global |
1.14 MB (🟡 +3.32 KB) |
Details
The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!
Four Pages Changed Size
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load |
|---|---|---|
/settings/environment-variables |
4.94 KB (🟡 +255 B) |
1.15 MB |
/transactions |
44.98 KB (🟡 +325 B) |
1.19 MB |
/transactions/history |
44.96 KB (🟡 +327 B) |
1.19 MB |
/transactions/queue |
44.97 KB (🟡 +330 B) |
1.19 MB |
Details
Only the gzipped size is provided here based on an expert tip.
First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this.
Summary
Moves the transaction history backfill work off the eternalsafe branch into a dedicated feature branch.
This PR contains the 19 commits that were local-only on eternalsafe, covering tx history query settings, cursor persistence and hydration hardening, bounded parallel log backfill helpers, resumable backfill loading, and the final tx history backfill UI.
Validation
No code tests were run because this task only moved existing commits between branches.