-
Notifications
You must be signed in to change notification settings - Fork 3
Enable wsgi streaming conformance tests with pyvoy #51
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
Conversation
Signed-off-by: Anuraag Agrawal <[email protected]>
c047329 to
d5b0571
Compare
Signed-off-by: Anuraag Agrawal <[email protected]>
Signed-off-by: Anuraag Agrawal <[email protected]>
9c04be0 to
356f7a8
Compare
Signed-off-by: Anuraag Agrawal <[email protected]>
| port_future: asyncio.Future[int], | ||
| ): | ||
| args = ["--bind=127.0.0.1:0", "--threads=40", "--reuse-port"] | ||
| args = [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since updating conformance to have connection reuse, gunicorn would have some flakes. A bit disappointed since the vanguard has been so robust otherwise, but doing some research it seems a lot of settings assume nginx in front of gunicorn.
Through some random selection I got these settings to pass CI 3 times, but if anyone happens to know gunicorn better happy to hear any thoughts.
| "pytest-cov==7.0.0", | ||
| "pytest-timeout==2.4.0", | ||
| "pyvoy==0.1.1; sys_platform != 'win32'", | ||
| "pyvoy==0.1.2; sys_platform != 'win32'", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed an issue that could sporadically hang with WSGI
And tweaks gunicorn