-
Notifications
You must be signed in to change notification settings - Fork 6
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
[Bug] Webhooks fail to start under gunicorn 20.0.0 #85
Comments
Huh. See benoitc/gunicorn#2159. Apparently app factories are just broken in that release. |
Well that'll explain it. Wonder if it's intentional. |
Looks to be a consequence of moving to using importlib as using |
The Gunicorn and Flask devs are now chatting on that issue, and various users are weighing in with their perspectives. Sounds like they're leaning toward restoring the functionality but with a better implementation. The reason I used the app factory pattern here has been mentioned by others in that discussion: running the tests loads all modules to find tests. When I tried a global variable |
I think the use of the factory pattern is appropriate here and it is configured as per the flask documentation. We can either keep it pinned to 19.9.x until they decide how they're going to sort this going forward. All the right people are talking about it, so it's no real biggie and we're not chomping to use anything in 20.x.x to my knowledge. Alternatively, we're not passing anything to the create app, so we could alter the launch slightly as per this comment. Personally I think pinning the version is appropriate in the interim. |
Gunicorn 20.0.3 is out, and it works as far as I can tell. |
Awesome. We can unpin it at some point 🙂 |
Background
After releasing the latest batch of changes the webhooks failed to start. Not being part of the python code, rather gunicorn it didn't send the logs to discord.
Worked around it by locking below 20.0.0 for now.
Problem
The text was updated successfully, but these errors were encountered: