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

fix: Duplicate key in Settings and Privacy #11664

Merged
merged 5 commits into from
Oct 9, 2024

Conversation

gambinish
Copy link
Contributor

Description

ERROR  Warning: Encountered two children with the same key, `0x89`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version.

Related issues

Fixes: No issue, found while developing

Manual testing steps

  1. Add Polygon, and add a custom RPC Polygon
  2. Go to Network Settings
  3. Should not see duplicate key error in logs

Screenshots/Recordings

N/A

Pre-merge author checklist

Pre-merge reviewer checklist

  • I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
  • I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

Copy link
Contributor

github-actions bot commented Oct 7, 2024

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.

@gambinish gambinish marked this pull request as ready for review October 7, 2024 17:25
@gambinish gambinish requested a review from a team as a code owner October 7, 2024 17:25
@gambinish gambinish added Run Smoke E2E Triggers smoke e2e on Bitrise and removed team-assets labels Oct 7, 2024
@gambinish gambinish requested a review from a team October 7, 2024 17:26
Copy link
Contributor

github-actions bot commented Oct 7, 2024

https://bitrise.io/ Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 8917aed
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/530ba2fc-4578-4ea8-ae7d-e935550b9340

Note

  • You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

tommasini
tommasini previously approved these changes Oct 7, 2024
Copy link
Contributor

@tommasini tommasini left a comment

Choose a reason for hiding this comment

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

LGTM! I believe this will change by Network Controller upgrade!

vinnyhoward
vinnyhoward previously approved these changes Oct 7, 2024
andreahaku
andreahaku previously approved these changes Oct 7, 2024
Copy link
Contributor

@andreahaku andreahaku left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Contributor

@NicolasMassart NicolasMassart left a comment

Choose a reason for hiding this comment

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

should line 712 also be fixed?

sahar-fehri
sahar-fehri previously approved these changes Oct 7, 2024
@gambinish gambinish added Run Smoke E2E Triggers smoke e2e on Bitrise and removed Run Smoke E2E Triggers smoke e2e on Bitrise labels Oct 7, 2024
Copy link
Contributor

github-actions bot commented Oct 7, 2024

https://bitrise.io/ Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 0aa3794
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/e7bad620-aadf-4976-aa3c-f40a4bbe999b

Note

  • You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

@codecov-commenter
Copy link

codecov-commenter commented Oct 7, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 54.13%. Comparing base (bda40a6) to head (46d323f).
Report is 9 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #11664      +/-   ##
==========================================
+ Coverage   54.02%   54.13%   +0.11%     
==========================================
  Files        1679     1687       +8     
  Lines       38500    38533      +33     
  Branches     4702     4703       +1     
==========================================
+ Hits        20798    20859      +61     
+ Misses      16266    16236      -30     
- Partials     1436     1438       +2     

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

NicolasMassart
NicolasMassart previously approved these changes Oct 7, 2024
Copy link
Contributor

@NicolasMassart NicolasMassart left a comment

Choose a reason for hiding this comment

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

Looks good to me. Thanks!

@gambinish gambinish added Run Smoke E2E Triggers smoke e2e on Bitrise and removed Run Smoke E2E Triggers smoke e2e on Bitrise labels Oct 8, 2024
Copy link
Contributor

github-actions bot commented Oct 8, 2024

https://bitrise.io/ Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 46d323f
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/0d8a6aa5-bb63-4fb8-89b2-14f51e5a0f9c

Note

  • You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Copy link

sonarqubecloud bot commented Oct 8, 2024

@gambinish gambinish added this pull request to the merge queue Oct 9, 2024
Merged via the queue into main with commit 9e3d268 Oct 9, 2024
43 checks passed
@gambinish gambinish deleted the fix/duplicate-key-error-privacy-settings-chainId branch October 9, 2024 00:20
@github-actions github-actions bot locked and limited conversation to collaborators Oct 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

8 participants