-
Notifications
You must be signed in to change notification settings - Fork 561
Open
Description
I am receiving the same error as mentioned in issue #269, but the solution mentioned there does not fix the problem for me.
I'm using twit version 2.2.4, with the following configuration:
const keys = {
consumer_key : process.env.TWITTER_CONSUMER_KEY,
consumer_secret : process.env.TWITTER_CONSUMER_SECRET,
access_token : process.env.TWITTER_ACCESS_TOKEN,
access_token_secret : process.env.TWITTER_ACCESS_TOKEN_SECRET,
timeout_ms: 60*1000,
};
I've tried it both with and without the trailing comma at the end. It works for an extended period of time (usually a day or two), but then fails abruptly with this error:
events.js:160
throw er; // Unhandled 'error' event
^
Error: unexpected end of file
at Zlib._handle.onerror (zlib.js:370:17)
The tweet emitter is started and consumed using the following functions (I was testing different geographic areas, hence the geo filter that covers the whole planet):
const client = new Twitter(keys);
const twitEmitter = client.stream('statuses/filter',
{locations: '-180,-89,180,89'});
twitEmitter.on('tweet', (tweet) => {
filterForwardLog(tweet);
});
twitEmitter.on('disconnect', (disconnectMessage) => {
winston.log('warning', 'Connection terminated: ');
reject(disconnectMessage);
});
twitEmitter.on('connect', () => {
winston.log('info', 'Connection attempted.');
});
twitEmitter.on('connected', () => {
winston.log('info', 'Connection successful.');
});
twitEmitter.on('reconnect', (req, res, interval) => {
winston.log('notice', `Reconnecting in ${interval / 1000.0} seconds`);
});
twitEmitter.on('warning', (warning) => {
winston.log('warn', warning);
});
OtacilioN
Metadata
Metadata
Assignees
Labels
No labels