We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We're using a healthcheck the same as added in #50, but running https://github.com/libero/article-store locally I'm seeing a lot of:
console_1 | 3:01:30 PM: Middleware error console_1 | Error: read ECONNRESET console_1 | at TCP.onStreamRead (internal/stream_base_commons.js:201:27)
and
console_1 | 3:01:15 PM: Middleware error console_1 | Error: write ECONNRESET console_1 | at afterWriteDispatched (internal/stream_base_commons.js:150:25) console_1 | at writeGeneric (internal/stream_base_commons.js:141:3) console_1 | at Socket._writeGeneric (net.js:771:11) console_1 | at Socket._write (net.js:783:8) console_1 | at doWrite (_stream_writable.js:431:12) console_1 | at clearBuffer (_stream_writable.js:551:7) console_1 | at Socket.Writable.uncork (_stream_writable.js:325:7) console_1 | at connectionCorkNT (_http_outgoing.js:656:8) console_1 | at processTicksAndRejections (internal/process/task_queues.js:80:21)
This might explain libero/article-store#166 (comment).
/cc @giorgiosironi
The text was updated successfully, but these errors were encountered:
I don't know where it comes from. Saw it once but failed to repeat 🤔
Is this only happening locally you say?
Sorry, something went wrong.
Saw it again yesterday, but tried this morning to see if I could debug and nothing. 😅
Will do it next time I see it.
Wonder if this is nodejs/node#27916.
No branches or pull requests
We're using a healthcheck the same as added in #50, but running https://github.com/libero/article-store locally I'm seeing a lot of:
and
This might explain libero/article-store#166 (comment).
/cc @giorgiosironi
The text was updated successfully, but these errors were encountered: