-
Notifications
You must be signed in to change notification settings - Fork 462
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
request error Context conflict #1984
Comments
@kazupon can you please provide a workaround? |
same! @kazupon please we need your help, it is blocking issue |
@kazupon useCookie is not the issue, i tried without and the same error happened |
I don't know how to further debug the problem. I hope someone can help. The problem is affecting us in production and we urgently need to solve it @kazupon |
For me removing useCookie helps, but I need it |
Hi! I would like you to sepelate this issue if this issue can be reproduced with your cusomt module without using nuxt i18n first. 🙏 |
👍 thx @kazupon after digging deeper it stuck in the app:render hook. The unctx is checking the currentContext vs instance ctx and throws an 500 error. I dont think ist ein i18n issue |
can you please try below Nuxt 3.3.2? See: nuxt/nuxt#19753 |
@c-schwan you're right. in version 3.3.0 it doesn't happen. |
How can we resolve it? |
fixed: nuxt/nuxt#20510 version 3.4.3 |
Environment
production and dev
Reproduction
https://stackblitz.com/edit/nuxt-issue-20070
It is also related to the package "@nuxtjs/i18n" and "useCookie".
1. On a clean nuxt 3 project, install:
"@nuxtjs/i18n": "^8.0.0-beta.10"
2. Create global middleware like this:
3. Use siege and gtimeout to send multiple concurrent requests:
brew install siege
brew install coreutils
gtimeout 30 siege -c 5 http://localhost:3000
then sometimes I will get the error:
[nuxt] [request error] [unhandled] [500] Context conflict
Describe the bug
Error appears in production and local logs:
[nuxt] [request error] [unhandled] [500] Context conflict
Additional context
No response
Logs
The text was updated successfully, but these errors were encountered: