Failed to execute 'insertBefore' on 'Node' #3676
Replies: 4 comments 2 replies
-
Could be a rollup issue, but seems specific to huggingface. Can you reproduce it locally? Can you observer it on the demo HF page? https://librechat-librechat.hf.space/login
I can imagine this happening with the recent change of the app pinging the backend to help keep connections alive between revisiting the app after idling, which seems to be case for you. Huggingface may not like this since it benefits from server cold starts. To further debug the issue would be pretty technical, not sure if you'd be willing to try. Would need to load the app in "dev" mode with source map enabled, and not even sure if it would work on Huggingface. |
Beta Was this translation helpful? Give feedback.
-
Some of our users have the same Problem with LibreChat 0.7.5. It is a simple installation with just one modelSpec and without bookmarks, plugins and assistants. It is completely random and unfortunately not reproducable. Unerwarteter Anwendungsfehler! Fehler beim Ausführen von 'removeChild' auf 'Node': Der zu entfernende Knoten ist kein untergeordnetes Element dieses Knotens. NotFoundError: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node. |
Beta Was this translation helpful? Give feedback.
-
It is not specific to huggingface and I still have it on multiple devices. E.g. I installed LibreChat on a fresh device, latest version, and I started having this error there from time to time. |
Beta Was this translation helpful? Give feedback.
-
What happened?
Periodically, when I use librechat, I get the following error message. It appears a couple of times a day and disappears only after I reload the page.
I updated the huggingface space to the latest version with the factory reset, which did not fix the issue.
I didn't do anything unusual when setting up the space, just set the environment variables according to the instructions.
Steps to Reproduce
Use the huggingface space for a while. The error appears at a completely random time.
What browsers are you seeing the problem on?
No response
Relevant log output
No response
Screenshots
No response
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions