-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Worker timeout #39
Comments
You did a great Tool !!! But this timeout thing is really bad - any workaround for this maybe? |
Hey! So there could be several reasons for this, depending on the logic of the The issue is more or less: Signal Gets to Action/Event The "stuff" could be stuck somewhere. I will be adding a "timeout" option to increase the default timeout time to something more than 30 seconds. (usually more than this amount of time indicates an issue though) |
Hi! I found the same workaround: in line 62 i added a timeout to the server with 1 second: run(f'gunicorn --bind {host}:{port} --timeout 1 wsgi:app'.split(' ')) As i set the timeout to 600, it wouldnt time out again, but the stuckness every about 30 seconds (meaning taking no new webhooks) remained. with 1 second, it reboots often but is therefore more available because stuckness is limited to one second. doesnt solve the root cause though.. |
Hmm, in that case, I may try to change actions to be run with async. This should solve any timeout issues going forward! You can "emulate" this by using multi threading for now if you wish. Something like this: Are you able to locate where in your |
I am totally not able to locate that :D |
@tlnet1981 interesting! It's also ok if you're fine with how its working now. |
@robswc , sorry didnt understand you right - you mean the code of my "action" - sure no problem. I basically just pump it to a redis channel, and other stuff is picking it up from there: `class test(Action):
you mean the redis server is causing the delays? ...but the worker timeout or stuckness appears also during times when no webhook comes an, therefore no action is triggered. |
here you can see, no action triggered but reboots all the time (1 second timeout) ...pretty exactly every 1 minute 2022-10-13 02:06:33,869 [MainThread ] [INFO ] Registering action ---> test |
@robswc Is there an update on this issue? I saw an async commit but 1.0.2 did not solve the problem. Here is my log without any changes on my side:
|
Happens when /webhook request can't be processed in time. Can be from various causes. Investigating...
The text was updated successfully, but these errors were encountered: