You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to keep the Heroku Dyno alive there needs to be one request every 5 minutes. Therefore I added a skill that uses match_crontab to hit the status API every 5 minutes to keep itself awake.
However, I was lazy and just used requests (not async) to make a get request. This means that when opsdroid runs the skill it blocks the event loop on the requests call which stops the web server from being able to respond to the call and eventually times out.
The fix for this is to use aiohttp to make the call or run requests in an executor.
The text was updated successfully, but these errors were encountered:
Well this is a fun little bug.
In order to keep the Heroku Dyno alive there needs to be one request every 5 minutes. Therefore I added a skill that uses
match_crontab
to hit the status API every 5 minutes to keep itself awake.However, I was lazy and just used requests (not async) to make a get request. This means that when opsdroid runs the skill it blocks the event loop on the requests call which stops the web server from being able to respond to the call and eventually times out.
The fix for this is to use aiohttp to make the call or run requests in an executor.
The text was updated successfully, but these errors were encountered: