-
Notifications
You must be signed in to change notification settings - Fork 691
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
uWSGI 2.0.25: TypeError: sequence item 14: expected str instance, NoneType found #2630
Comments
thanks for reporting. Could you please build it from git and help debugging the issue a bit? |
This line here fails because clfags contains a parameter that is no String, but None instead: I follwoed it back. Its pcre_cflags here that is None That parameter is populated here: And when I manually execute it I get:
So one can install pcre-dev:
It then failed with some classic missing headers, yet that could be fixed with:
So afterwards I could finally build uwsgi. The complete "solution" is:
That missing pcre-dev package was quite unpleasant to troubleshoot. A check if it exists and then throwing a meaningful error would be quite beneficial. :( |
Thanks! What values do you have in |
required_pcre is auto The call here to popuplate pcre_libs: https://github.com/unbit/uwsgi/blob/2.0.25/uwsgiconfig.py#L1088C33-L1088C53 is none, as the command isn't found:
|
The we are missing a guard around here https://github.com/unbit/uwsgi/blob/2.0.25/uwsgiconfig.py#L1104 |
I have faced the same issue, building inside docker, instead i downgraded to 2.0.24 |
I too had this issue, C_FLAGS were missing, broke our pipeline and we redeployed with 2.0.24 and problem was resolved. Built in docker via AWS CodeDeploy on AmazonLinux2023. |
Fixed by #2632 |
I can confirm that the new release (2.0.25.1) fixed it for me. Thanks alot! |
Hi,
I am running into an issue with the newest uwsgi (2.0.25). I am pinning things now to 2.0.24 so its not really a big deal for now, yet this of course prevents me from upgrading to newer patches which (especially for seucity updates) will be a problem for me :(
Steps to reproduce the issue
The full error output:
The text was updated successfully, but these errors were encountered: