rfbomb/twitch-watcher

Automatic watching the twitch to get Valorant drop

twitch-watcher's Issues

[Docker] ChannelName_3 is interpreted as UserTimezone

In the app.js at line 102 you are initializing the var UserTimeZone with the Enviroment Variable ChannelName_3:
UserTimeZone = (process.env.ChannelName_3 || 'America/New_York');

So if the ChannelName_3 Var is used in e.g. the docker-compose.yml, the twitch-watcher will not start: "Error: RangeError: Invalid time zone specified: warframe"

This only affects Docker-Container, because normally the code in Line 119 would be executed:
UserTimeZone = (await UserSettings.ReadConfigSetting('UserTimeZone') || 'America/New_York');

UserTimeZone could then also be mentioned in the docker-compose-example.yml file :)

[Docker] Request to https://api.twitch.tv/helix/streams failed

=========================
🔎 Checking config file...
✅ Env config found

=========================
📱 Launching browser...
🔧 Setting User-Agent...
🔧 Setting auth token...
⏰Setting timeouts...
----------- Loaded Variables ------------
ChannelName_1 - nmplol
ChannelName_2 -
ChannelName_3 -
streamersUrl - https://www.twitch.tv/directory/game/iRacing
TimeZone - America/New_York
minWatching - 15
maxWatching - 30
IgnoreRandomChannels - true
----------- End of Loaded Variables ------------
🤬 Error: FetchError: request to https://api.twitch.tv/helix/streams failed, reason: getaddrinfo EAI_AGAIN api.twitch.tv
at ClientRequest. (/usr/src/app/node_modules/node-fetch/lib/index.js:1461:11)
at ClientRequest.emit (events.js:315:20)
at TLSSocket.socketErrorListener (_http_client.js:432:9)
at TLSSocket.emit (events.js:315:20)
at emitErrorNT (internal/streams/destroy.js:84:8)
at processTicksAndRejections (internal/process/task_queues.js:84:21) {
message: 'request to https://api.twitch.tv/helix/streams failed, reason: getaddrinfo EAI_AGAIN api.twitch.tv',
type: 'system',
errno: 'EAI_AGAIN',
code: 'EAI_AGAIN'
}
(node:25) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'error' of undefined
at Object.TestAPIToken (/usr/src/app/HelixAPI.js:98:14)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async SetupVariables (/usr/src/app/app.js:156:9)
at async main (/usr/src/app/app.js:644:3)
(node:25) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:25) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.