-
Notifications
You must be signed in to change notification settings - Fork 491
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
azure: setHeaders throws exception #351
Comments
A similar issue happens for IncomingMessage as well:
with points to https://github.com/nodejs/node/blob/ba67fe66eb7777d5055c785be153374843fc647e/lib/internal/streams/readable.js#L856, i.e. |
And similarly
|
I too got stuck in this issue . This issue happens because, If my understanding is correct, this issue can be reproduced by mounting and running and ExpressJs application using |
As a workaround, you can overwrite the implementation of the offending methods with the node implementations. See eg the lines following https://github.com/JabRef/JabRefOnline/blob/036a7c3697713e9b998c708fa1f5e9ba4f0a0637/server/api/index.ts#L11 |
I'm facing a similar issue and It is very likely related to server side rendering when fetch is performed on on server. It is working correctly when fetched client side. Very likely related to below issue as well: nuxt/nuxt#12720 |
Hi. I'm not sure if it is something we should include to the core considering the cause backs to express incompatibility and patching native node |
Environment
Linux
v16.16.0
3.0.0-rc.5
yarn@1.22.19
vite
alias
,nitro
,ssr
,meta
,css
,tailwindcss
,modules
,watch
,runtimeConfig
,serverHandlers
,storybook
,hooks
@nuxtjs/tailwindcss@5.1.3
,@pinia/nuxt@0.3.0
,./modules/storybook
,-runtime-compiler-module
-
Reproduction
I still have to find a way to reproduce this in a minimal enviroment.
For now you can run
yarn dev:azure
in https://github.com/JabRef/JabRefOnline.Describe the bug
I get the following error when the app is deployed to azure (using nuxt):
The errorhandler is pointing to
nitro/src/runtime/error.ts
Line 40 in 5ab1041
setHeader
in a middleware).Additional context
The line
ServerResponse.setHeader (node:_http_outgoing:585:45)
is pointing to https://github.com/nodejs/node/blob/main/lib/_http_outgoing.js#L612. And indeed, this particular server response object contains only thekCapture
symbol, but no other symbols (i.e. no kOutHeaders as normally).Moreover, it might be related to unjs/h3#21.
Logs
No response
The text was updated successfully, but these errors were encountered: