Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(db): fix seed script #654

Merged
merged 4 commits into from
Nov 28, 2024
Merged

chore(db): fix seed script #654

merged 4 commits into from
Nov 28, 2024

Conversation

PJColombo
Copy link
Member

@PJColombo PJColombo commented Nov 28, 2024

Checklist

  • My change requires a documentation update, and I have done it.
  • I have added tests to cover my changes.
  • I have filled out the description and linked the related issues.

Description

It does the following:

  • It fixes an issue where the seed script wasn't creating the address category info db entities correctly.
  • It also generates blob data for every created blob.
  • It improves the script's logs
  • It replaces ts-node by tsx as former resolves modules to commonjs which was giving problems with certain esm-only packages (e.g. ora)

Motivation and Context (Optional)

Related Issue (Optional)

Screenshots (if appropriate):

Copy link

changeset-bot bot commented Nov 28, 2024

⚠️ No Changeset found

Latest commit: e524eac

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

vercel bot commented Nov 28, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
blobscan-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 28, 2024 7:27am
blobscan-staging ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 28, 2024 7:27am
4 Skipped Deployments
Name Status Preview Comments Updated (UTC)
blobscan-gnosis ⬜️ Ignored (Inspect) Nov 28, 2024 7:27am
blobscan-holesky ⬜️ Ignored (Inspect) Nov 28, 2024 7:27am
blobscan-mainnet ⬜️ Ignored (Inspect) Nov 28, 2024 7:27am
blobscan-sepolia ⬜️ Ignored (Inspect) Visit Preview Nov 28, 2024 7:27am

Copy link

codecov bot commented Nov 28, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.76%. Comparing base (bcf780a) to head (e524eac).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #654   +/-   ##
=======================================
  Coverage   88.76%   88.76%           
=======================================
  Files         159      159           
  Lines       10863    10863           
  Branches     1204     1204           
=======================================
  Hits         9643     9643           
  Misses       1220     1220           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

📦 Next.js Bundle Analysis for @blobscan/web

This analysis was generated by the Next.js Bundle Analysis action. 🤖

⚠️ Global Bundle Size Increased

Page Size (compressed)
global 332.25 KB (🔴 +86.64 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!

New Pages Added

The following pages were added to the bundle from the code in this PR:

Page Size (compressed) First Load % of Budget (350 KB)
/block_neighbor 251 B 332.5 KB 95.00%
/stats 348 KB 680.25 KB 194.36%

Eight Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page Size (compressed) First Load % of Budget (350 KB)
/ 353.03 KB 685.29 KB 195.80% (🟢 -4.66%)
/address/[address] 28.54 KB 360.79 KB 103.08% (🟢 -4.34%)
/blob/[hash] 29.21 KB 361.47 KB 103.28% (🟢 -3.78%)
/blobs 79.07 KB 411.33 KB 117.52% (🟡 +13.22%)
/block/[id] 14.9 KB 347.16 KB 99.19% (🟢 -3.99%)
/blocks 76.77 KB 409.03 KB 116.87% (🟡 +13.20%)
/tx/[hash] 17.22 KB 349.47 KB 99.85% (🟡 +1.13%)
/txs 76.28 KB 408.53 KB 116.72% (🟡 +11.20%)
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

The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your 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. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.

@PJColombo PJColombo merged commit 07a6d5d into main Nov 28, 2024
14 checks passed
@PJColombo PJColombo deleted the chore/fix-seed-script branch November 28, 2024 08:39
Copy link
Collaborator

@xFJA xFJA left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice job 💯

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants