-
Notifications
You must be signed in to change notification settings - Fork 345
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
Enable lazy-loading by default #2978
Merged
Merged
Conversation
This file contains 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
WASM runtime size check:Compared to target branchMoonbase runtime: 2196 KB (no changes) ✅ Moonbeam runtime: 2140 KB (no changes) ✅ Moonriver runtime: 2132 KB (no changes) ✅ Compared to latest release (runtime-3200)Moonbase runtime: 2196 KB (+236 KB compared to latest release) Moonbeam runtime: 2140 KB (+216 KB compared to latest release) Moonriver runtime: 2132 KB (+208 KB compared to latest release) |
RomarQ
added
B5-clientnoteworthy
Changes should be mentioned in any downstream projects' release notes
D3-trivial
PR contains trivial changes in a runtime directory that do not require an audit
and removed
D3-trivial
PR contains trivial changes in a runtime directory that do not require an audit
labels
Sep 26, 2024
RomarQ
added
not-breaking
Does not need to be mentioned in breaking changes
D2-notlive
PR doesn't change runtime code (so can't be audited)
labels
Sep 26, 2024
Coverage Report@@ Coverage Diff @@
## master rq/enable-lazy-loading +/- ##
==========================================================
- Coverage 79.22% 79.18% -0.04%
Files 299 299
- Lines 87253 87233 -20
==========================================================
- Hits 69118 69075 -43
+ Misses 18135 18158 +23
|
librelois
approved these changes
Sep 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A8-mergeoncegreen
Pull request is reviewed well.
B5-clientnoteworthy
Changes should be mentioned in any downstream projects' release notes
D2-notlive
PR doesn't change runtime code (so can't be audited)
lazy-loading
These changes affect the lazy loading feature
not-breaking
Does not need to be mentioned in breaking changes
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.
What does it do?
This PR enabled the
lazy-loading
feature by default in the client.What important points reviewers should know?
Is there something left for follow-up PRs?
What alternative implementations were considered?
Are there relevant PRs or issues in other repositories (Substrate, Polkadot, Frontier, Cumulus)?
What value does it bring to the blockchain users?