-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Bug: Node.js ERR_INTERNAL_ASSERTION error when updating and saving content with Strapi [v4.15.0] #50436
Comments
Duplicate of #47644. |
cc: @ShogunPanda |
Thanks. All it seems to be related to timeout handling. I hope to have a fix soon. |
This should have been fixed in #51045. Once it gets in 21.x or 20.x please let me know if you have additional problems. |
MongoDB Compass has encountered an unexpected error |
@naveenjpr Which Node version are you on? |
My node version v20.13.1
…On Thu, 27 Jun 2024, 12:33 pm Paolo Insogna, ***@***.***> wrote:
@naveenjpr <https://github.com/naveenjpr> Which Node version are you on?
—
Reply to this email directly, view it on GitHub
<#50436 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7GWXHUHTBFJXXIJRIOEVV3ZJO2N7AVCNFSM6AAAAABJ7GF4R6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJTHE2DQMZWGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
my node version v20.13.1 |
@naveenjpr lets continue here: #50893 (comment) |
Version
20.8.1
Platform
Windows 10 x64
Subsystem
No response
What steps will reproduce the bug?
-Reproduction Steps:
ERR_INTERNAL_ASSERTION
error.How often does it reproduce? Is there a required condition?
The ERR_INTERNAL_ASSERTION error does not occur every time. It is infrequent and does not consistently manifest
What is the expected behavior? Why is that the expected behavior?
I expected the content to be updated and saved without any errors.
What do you see instead?
Instead, I encountered the
ERR_INTERNAL_ASSERTION
error.Full Error details below:
Additional information
This issue seems to have emerged after updating content within Strapi, and I suspect it may be related to the Node.js environment. I appreciate any assistance in diagnosing and resolving this issue. Please let me know if there are additional details or information needed to investigate further.
Thank you for your support in addressing this problem.
The text was updated successfully, but these errors were encountered: