Skip to content
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

Latest version of Werkzeug does not support Flask 2.0.2 #8

Open
ljarman84 opened this issue Nov 23, 2023 · 4 comments
Open

Latest version of Werkzeug does not support Flask 2.0.2 #8

ljarman84 opened this issue Nov 23, 2023 · 4 comments
Labels
bug Something isn't working

Comments

@ljarman84
Copy link

Adding Werkzeug==2.2.2 to requirements.txt fixes the issue

@ljarman84 ljarman84 added the bug Something isn't working label Nov 23, 2023
@Flawke
Copy link

Flawke commented Feb 7, 2024

I set it to Werkzeug>=2.3.8,<3.0.0

@RobbeVandenDaele
Copy link

Can confirm that the fix recommended by @ljarman84 works. Opened a pull-request: #9

@andyfaulds
Copy link

Hi, had this same issue and managed to resolve with updating requirements.txt to

requests==2.27.1
Flask==2.0.2
Werkzeug>=2.3.8,<3.0.0
gunicorn[gevent]
gevent

@JamieICG
Copy link

JamieICG commented Sep 18, 2024

We had the same issue and updated our requirements.txt file to the following and it started building the app correctly:

requests==2.27.1
Flask==2.2.2
Werkzeug==2.2.2
gunicorn[gevent]
gevent

I should also point out that the WORKSPACE__ID and SHARED_KEY (called out on other issues/PRs) need to be present in your environmental variables or it still wont work. These are the Workspace ID and Secret for your Log Analytics workspace. Palo Alto could do with reviewing some of the recommendations/bugs here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants