-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Fixing up StrictMode errors in the e2e tests. #17355
Comments
Test:
|
Test:
|
(I don't know if the Test:
|
Test:
|
Test:
|
I'm seeing these (or possibly related) errors when using a RichText component inside the It looks like the errors are coming from the Toolbar components on the RichText control, but I'm not positive. I've been trying to figure out if I'm doing something wrong (ie trying to mount the components on an unmounted component) but I'm really not a React expert (yet) and I don't know exactly what this means or how to debug it further. Is this something that's actually coming from a core package or, if this is on me, do you have any advice or recommendations for me on either where to look to learn more about how to do this properly? Thanks! Full error (in case it helps):
|
@gziolo Is this still the case, I think you worked on related things lately? |
I was working on different issues lately. This is still valid and it's blocking #14845 - use SCRIPT_DEBUG in end-to-end test environment. |
@talldan are you still working on it? |
@gziolo Sorry, missed the ping. I think I lost track that I was supposed to be working on this. Sorry! |
#19642 looks like another one related to Slot, might be the same issue. |
I'm still seeing those By the way, #19242 (slot fill refactor) is kind of done and is blocking other tasks (#20008). I would appreciate any review there! 😆 |
BTW, the slot fill issue still exists:
|
I'm also seeing another state update on master:
You can trigger it by going to |
I wonder if it happens here? It seems to fit the stack trace:
|
@noahtallen Does this happen before #20008? |
No, I checked out the commit previous to that merge and it does not happen before that PR. I used the same post/post content to test as well. repro steps:
before that PR, step 4 doesn't happen. no warning displays |
Thanks! :) |
thanks for noticing! |
Created a simple reproduction here: https://codesandbox.io/s/wordpress-slotfill-memory-leak-warning-nmcmc?file=/src/App.js It doesn't seem to happen when It also doesn't happen when we memoize the gutenberg/packages/components/src/slot-fill/fill.js Lines 35 to 40 in d15a208
React elements ( |
I'm going to close this issue. Why?
|
Blocks #14845.
Describe the bug
Turning on
StrictMode
gives a bunch of errors, this is a tracking ticket to list them out.I'll list one per comment, along with an e2e test that generates the error.
To reproduce
Run the e2e tests with
SCRIPT_DEBUG
set totrue
.The text was updated successfully, but these errors were encountered: