-
Notifications
You must be signed in to change notification settings - Fork 24
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
Describe the bug
When currently running latest version, an HTTP error is produced in the console:
events.js:292
throw er; // Unhandled 'error' event
^
Error [ERR_STREAM_WRITE_AFTER_END]: write after end
at writeAfterEnd (_http_outgoing.js:668:15)
at ServerResponse.end (_http_outgoing.js:788:7)
at e.serveWebsite (/home/mitsos/Documents/Projects/parse-mem-captures/node_modules/nodeplotlib/dist/lib/index.js:1:3735)
at Server.<anonymous> (/home/mitsos/Documents/Projects/parse-mem-captures/node_modules/nodeplotlib/dist/lib/index.js:1:2989)
at Server.emit (events.js:315:20)
at parserOnIncoming (_http_server.js:874:12)
at HTTPParser.parserOnHeadersComplete (_http_common.js:126:17)
Emitted 'error' event on ServerResponse instance at:
at writeAfterEndNT (_http_outgoing.js:727:7)
at processTicksAndRejections (internal/process/task_queues.js:81:21) {
code: 'ERR_STREAM_WRITE_AFTER_END'
}
This happens due to the fact that a request for /data/[plotId] is received from here and it reaches to an unknown endpoint so the server replies with 404.
The problem is that the request seems to be already served by here, so the error is correctly thrown
The plot is successfully drawn though...
To Reproduce
Steps to reproduce the behavior:
- Just run a script that plots and watch the terminal
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Add any other context about the problem here.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working