Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed

235
April 25, 2019, at 02:40 AM

Context:

I've created what I called a softmodem-poetry machine, using two softmodems transmitters to transmit synchronously two different twitter streams at the same baud rate, creating an entanglement of quasi-gibberish/quasi-legible signals coming both from softmodem 1 and softmodem 2. These programs were running three months ago.

Problem:

When I try running these programs now, I have this Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed as soon as I connect to my socket.

Here's the relevant code I think:

twit.stream("statuses/filter", { track: randomTitle}, function(stream) {
      stream.on("data", function(data) {
        socket.emit("tweet", data.text);
        child.stdin.write(data.text);
      });
});`

Here's the entire code: https://github.com/cyruslk/twitter_minimodem/blob/master/app.js

READ ALSO
No'Access-Control-Allow-Origin

No'Access-Control-Allow-Origin

localhost/:1 Access to XMLHttpRequest at 'http://18550

59
Is there any way to use the same es6 module import paths for Node and browsers without bundling?

Is there any way to use the same es6 module import paths for Node and browsers without bundling?

I've been playing around with using es6 modules directly, without using Webpack, rollup, etcAfter reading this article, I settled on the following:

76
Hyperledger fabric 1.2 capabilities error

Hyperledger fabric 1.2 capabilities error

I am trying to use hyperledger fabric sample network with my own chaincodeI am using balance-transfer but my chaincode requires collections config file because It is using private data

84
No Output fast-csv writeToPath

No Output fast-csv writeToPath

I am writing a script which at its core parses acsv file for certain columns storing them in an array and then writes the contents to another

112