2019-03-03T17:06:41.190434+00:00 app[web.1]: Connecting to Discord...
2019-03-03T17:06:42.652189+00:00 app[web.1]: Connected! Now listening to DMs.
2019-03-03T17:07:06.223947+00:00 app[web.1]: [NOTE] Creating new thread channel emivg-8019
2019-03-03T17:07:14.119343+00:00 app[web.1]: Closing thread c0eeb070-bfba-47bc-aac3-eba9b2263483
2019-03-03T17:07:14.389143+00:00 app[web.1]: Deleting channel 551812811072733185
2019-03-03T17:07:23.081908+00:00 app[web.1]: [NOTE] Creating new thread channel emivg-8019
2019-03-03T17:07:36.148843+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2019-03-03T17:07:36.148843+00:00 heroku[web.1]: Stopping process with SIGKILL
2019-03-03T17:07:36.251152+00:00 heroku[web.1]: Process exited with status 137
2019-03-03T17:07:37.235322+00:00 heroku[web.1]: State changed from crashed to starting
2019-03-03T17:08:01.207351+00:00 heroku[web.1]: State changed from starting to crashed
2019-03-03T17:08:01.286121+00:00 heroku[web.1]: State changed from crashed to starting
2019-03-03T17:08:03.704795+00:00 heroku[web.1]: Starting process with command `npm start`
2019-03-03T17:08:05.393310+00:00 app[web.1]:
2019-03-03T17:08:05.393334+00:00 app[web.1]: > modmailbot@2.18.0 start /app
2019-03-03T17:08:05.393335+00:00 app[web.1]: > node src/index.js
2019-03-03T17:08:05.393337+00:00 app[web.1]:
2019-03-03T17:08:06.100106+00:00 app[web.1]: Use async .hasTable to check if table exists and then use plain .createTable. Since .createTableIfNotExists actually just generates plain "CREATE TABLE IF NOT EXIST..." query it will not work correctly if there are any alter table queries generated for columns afterwards. To not break old migrations this function is left untouched for now, but it should not be used when writing new code and it is removed from documentation.
2019-03-03T17:08:06.113180+00:00 app[web.1]: Use async .hasTable to check if table exists and then use plain .createTable. Since .createTableIfNotExists actually just generates plain "CREATE TABLE IF NOT EXIST..." query it will not work correctly if there are any alter table queries generated for columns afterwards. To not break old migrations this function is left untouched for now, but it should not be used when writing new code and it is removed from documentation.
2019-03-03T17:08:06.118764+00:00 app[web.1]: Use async .hasTable to check if table exists and then use plain .createTable. Since .createTableIfNotExists actually just generates plain "CREATE TABLE IF NOT EXIST..." query it will not work correctly if there are any alter table queries generated for columns afterwards. To not break old migrations this function is left untouched for now, but it should not be used when writing new code and it is removed from documentation.
2019-03-03T17:08:06.120667+00:00 app[web.1]: Use async .hasTable to check if table exists and then use plain .createTable. Since .createTableIfNotExists actually just generates plain "CREATE TABLE IF NOT EXIST..." query it will not work correctly if there are any alter table queries generated for columns afterwards. To not break old migrations this function is left untouched for now, but it should not be used when writing new code and it is removed from documentation.
2019-03-03T17:08:06.154106+00:00 app[web.1]: Loading modules...
2019-03-03T17:08:06.165787+00:00 app[web.1]: Connecting to Discord...
2019-03-03T17:08:08.013035+00:00 app[web.1]: Connected! Now listening to DMs.
2019-03-03T17:08:26.643049+00:00 app[web.1]: [NOTE] Creating new thread channel emivg-8019
2019-03-03T17:09:04.018557+00:00 heroku[web.1]: State changed from starting to crashed
2019-03-03T17:09:03.931207+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2019-03-03T17:09:03.931247+00:00 heroku[web.1]: Stopping process with SIGKILL
2019-03-03T17:09:04.000373+00:00 heroku[web.1]: Process exited with status 137