Minified React error #300; visit Minified React error #300 – React for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
To ensure this was not due to pending updates, I updated the Navigator this morning (v 2.6.2) , as well as Jupyter Lab (v 2.0.11) and Toolbox (v 4.0.15).
Thank you for reporting this bug. Unfortunately, the error messages in the current release are not as helpful as they could be. The upcoming release should have a more helpful error message. If the issue you are experiencing is what we suspect, it should be resolved next week on Cloud Notebooks - and then hopefully soon after for those using the Assistant locally. It is also possible you are hitting the rate limit - and the current error message does not make that clear.
Minified React error #300; visit Minified React error #300 – React for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Looking it up at the site given, it further explains: Rendered fewer hooks than expected. This may be caused by an accidental early return statement.
Minified React error #300; visit Minified React error #300 – React for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
I’m getting the same error running Jupyterlab locally. It was working fine up to a few days ago then it was like a switch turned off and it stopped working. Tried most things AA suggested (using the cloud version). Update, reinstall, disabled brower plugins, rebuild, checked the plugins, tried different browsers.
I’m working in Safari, macOS 14.4.1.
This was meant to be fixed back in August, yes? Any progress on that? What about an updated and more useful error message? Looks like that didn’t happen either.
I’ve tried it in Chrome, Safari and Brave with no result. Is it possible they all use the same backend , and maybe it got updated and broke the local version of AA? It’s strange it doesn’t matter what browser I use, yet it comes up as a React issue.