fix: network verification for collision network + local network#23802
fix: network verification for collision network + local network#23802
Conversation
|
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
d5ffde2 to
3d00c7a
Compare
3d00c7a to
bc02fe5
Compare
Builds ready [bc02fe5]
Page Load Metrics (578 ± 426 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #23802 +/- ##
===========================================
+ Coverage 67.47% 67.50% +0.03%
===========================================
Files 1257 1258 +1
Lines 49228 49261 +33
Branches 12819 12829 +10
===========================================
+ Hits 33216 33251 +35
+ Misses 16012 16010 -2 ☔ View full report in Codecov by Sentry. |
|
any update ? |
@wethioproject the PR is under review process and should be merged soon |
|
thanks for update
Le mer. 3 avr. 2024 à 09:29, salimtb ***@***.***> a écrit :
… any update ?
@wethioproject <https://github.com/wethioproject> the PR is under review
process and should be merged soon
—
Reply to this email directly, view it on GitHub
<#23802 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALHLZ6PFZMK7RD4GSYF4XGDY3PDXBAVCNFSM6AAAAABFOF5HW2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZUGAZTKOBQGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
LGTM !Thanks for the fix ! |
cc4aec2 to
378a5ff
Compare
Builds ready [378a5ff]
Page Load Metrics (264 ± 284 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
49503b2 to
c1ea75f
Compare
Builds ready [c1ea75f]
Page Load Metrics (1506 ± 691 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
|
Any eta to resolve issue ? |
c1ea75f to
958643a
Compare
|
LGTM! |
Builds ready [958643a]
Page Load Metrics (620 ± 533 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
|
Could we write an E2E test here to automate this? One basic network add and one collision case? This would make me much more comfortable. |
Builds ready [d9a968c]
Page Load Metrics (704 ± 534 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
app/scripts/lib/rpc-method-middleware/handlers/add-ethereum-chain.js
Outdated
Show resolved
Hide resolved
8c9a58b to
e0dc2a5
Compare
Builds ready [e0dc2a5]
Page Load Metrics (744 ± 566 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
Description
here are the different fixes that this PR contains:
collision of two networks with the same chainId but with two different symbols ==> solution: manage this as a special case, add the other network and extend the list https://chainid.network/chains.json
scam warning displayed for networks running on localhost ==> exclude from network verification all networks running on localhost.
Related issues
Fixes: #23242
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist