Hello everyone, please help to see the following error is what?

[Pythoneryeah]

[06:05:24] [110.184.126.98][00bc765c][ManagementConnection] The client has reconnected.
Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
at new NodeError (internal/errors.js:322:7)
at afterWrite (internal/streams/writable.js:470:24)
at onwrite (internal/streams/writable.js:446:7)
at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:89:12) {
code: 'ERR_STREAM_DESTROYED'
}
Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
at new NodeError (internal/errors.js:322:7)
at afterWrite (internal/streams/writable.js:470:24)
at onwrite (internal/streams/writable.js:446:7)
at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:89:12) {
code: 'ERR_STREAM_DESTROYED'
}
Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
at new NodeError (internal/errors.js:322:7)
at afterWrite (internal/streams/writable.js:470:24)
at onwrite (internal/streams/writable.js:446:7)
at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:89:12) {
code: 'ERR_STREAM_DESTROYED'
}
Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
at new NodeError (internal/errors.js:322:7)
at afterWrite (internal/streams/writable.js:470:24)
at onwrite (internal/streams/writable.js:446:7)
at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:89:12) {
code: 'ERR_STREAM_DESTROYED'

[code-asher]

Probably trying to write to the previously closed connection. Sounds like a bug, although I think it eventually cleans up so it might not be something to worry about. Are you able to reproduce this consistently, and if so can you provide reproduction steps? Thanks!

[xiaobinqt]

I have the same issue when I try to download a large file from a webpage, such as a 200MB file.

[code-asher]

Interesting, it looks like there is a reconnect which might be interrupting the download. I am not sure how easy it is to implement resumable downloads but that would probably be the proper way to fix this.