-
Notifications
You must be signed in to change notification settings - Fork 11
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: Log improvements and WORKER_MAX_SOCKET_TIMEOUT_SECONDS #749
Conversation
@taylordowns2000 The websocket timeout should be working on this branch Image should be built for 1.5.5 I don't have any automated or manual tests on the actual timeout. I know the value is being passed in to the Pheonix socket, I've just not verified it's working. It's a little tricky to setup a slow response in the mock - although it should be possible of course. If you can test manually on the image I'm happy to release. I'll probably spend an hour on it in the morning and see if I can crack it quickly. |
Oh bottoms, it's all failed :( Ok, I'll fix in the morning |
Ok, should be sorted now 👍 |
Test added so I'm happy that this is working as expected |
Adds WORKER_MAX_SOCKET_TIMEOUT_SECONDS variable to control socket timeouts.
A few other tiny logging tweaks here.