-
Notifications
You must be signed in to change notification settings - Fork 15
Closed
Labels
bugSomething isn't workingSomething isn't working
Milestone
Description
This doesn't seem easy to reproduce, I stumble on it once in a while on my machine. Some starting point might be that this error is logged in the sdk stderr:
========================= START LOG =========================
node:events:491
throw er; // Unhandled 'error' event
^
Error: read ECONNRESET
at TCP.onStreamRead (node:internal/stream_base_commons:217:20)
Emitted 'error' event on ServerHttp2Stream instance at:
at ServerHttp2Stream.onerror (node:internal/streams/readable:785:14)
at ServerHttp2Stream.emit (node:events:513:28)
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
errno: -104,
code: 'ECONNRESET',
syscall: 'read'
}
Node.js v18.16.0
And afterwards the runtime ends up stuck in a loop trying to connect to the sdk.
dev.restate.e2e.node.VerificationTest_killingTheRuntime_20230608_174237.zip
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working