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[devtools]: fixed duplicated backend activation with multiple renderers #26807

Merged

Conversation

hoxyq
Copy link
Contributor

@hoxyq hoxyq commented May 12, 2023

Summary

Initially reported in #26797. Was not able to reproduce the exact same problem, but found this case:

  1. Open corresponding codepen from the issue in debug mode
  2. Open components tab of the extension
  3. Refresh the page

Received multiple errors:

  • Warning in the Console tab: Invalid renderer id "2".
  • Error in the Components tab: Uncaught Error: Cannot add node "3" because a node with that id is already in the Store.

This problem has occurred after landing a fix in #26779. Looks like Chrome is keeping the injected scripts (the backend in this case) and we start backend twice.

@facebook-github-bot facebook-github-bot added CLA Signed React Core Team Opened by a member of the React Core Team labels May 12, 2023
@hoxyq hoxyq merged commit 67a05d0 into facebook:main May 12, 2023
36 checks passed
@hoxyq hoxyq deleted the devtools/fix-duplicated-backend-activation branch May 12, 2023 13:59
hoxyq added a commit that referenced this pull request May 17, 2023
Closes #26787,
#26793

Includes these changes:
* fix[devtools]: fixed duplicated backend activation with multiple
renderers ([hoxyq](https://github.com/hoxyq) in
[#26807](#26807))
EdisonVan pushed a commit to EdisonVan/react that referenced this pull request Apr 15, 2024
…erers (facebook#26807)

## Summary
Initially reported in facebook#26797.
Was not able to reproduce the exact same problem, but found this case:

1. Open corresponding codepen from the issue in debug mode
2. Open components tab of the extension
3. Refresh the page

Received multiple errors:
- Warning in the Console tab: Invalid renderer id "2".
- Error in the Components tab: Uncaught Error: Cannot add node "3"
because a node with that id is already in the Store.

This problem has occurred after landing a fix in
facebook#26779. Looks like Chrome is
keeping the injected scripts (the backend in this case) and we start
backend twice.
EdisonVan pushed a commit to EdisonVan/react that referenced this pull request Apr 15, 2024
Closes facebook#26787,
facebook#26793

Includes these changes:
* fix[devtools]: fixed duplicated backend activation with multiple
renderers ([hoxyq](https://github.com/hoxyq) in
[facebook#26807](facebook#26807))
bigfootjon pushed a commit that referenced this pull request Apr 18, 2024
…erers (#26807)

## Summary
Initially reported in #26797.
Was not able to reproduce the exact same problem, but found this case:

1. Open corresponding codepen from the issue in debug mode
2. Open components tab of the extension
3. Refresh the page

Received multiple errors:
- Warning in the Console tab: Invalid renderer id "2".
- Error in the Components tab: Uncaught Error: Cannot add node "3"
because a node with that id is already in the Store.

This problem has occurred after landing a fix in
#26779. Looks like Chrome is
keeping the injected scripts (the backend in this case) and we start
backend twice.

DiffTrain build for commit 67a05d0.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed React Core Team Opened by a member of the React Core Team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants