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

This fixes #1173 #1174

Merged
merged 1 commit into from
Nov 15, 2024
Merged

This fixes #1173 #1174

merged 1 commit into from
Nov 15, 2024

Conversation

Musa-Anwaar
Copy link
Contributor

This commit fixes an issue highlighed in #1173.

It occurs when you run a deployment from Azure AI Studio and choose the Web App, which links to this repo. The issue occurs when you try to run the app but it encounters an error and says "KeyError: 'PROVIDE_AUTOMATIC_OPTIONS'".

Copy link
Contributor

@sarah-widder sarah-widder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the fix!

@sarah-widder sarah-widder merged commit 3b22853 into microsoft:main Nov 15, 2024
8 of 9 checks passed
@cliexa
Copy link

cliexa commented Nov 15, 2024

I did the same on my local before this push, used to get this error, still getting it:
image

Previously built versions are working on our side. Even without this change. When I build now, I get the above issue. Do you have any idea how I can diagnose this further?

@borgerta
Copy link

borgerta commented Nov 18, 2024

Similar issues as @cliexa. Pushed to app service from local git to our deployment slot, still getting the PROVIDE_AUTOMATIC_OPTIONS error. I can build the app on my local machine without issues.

Production slot is still working

Edit/Update: Pinning quart to 0.19.9 did the trick (flask at 3.0.3)

@cliexa
Copy link

cliexa commented Nov 20, 2024

I can confirm that pinning quart to 0.19.9 fixes the string formatting error. Thank you @borgerta.

danniesim added a commit to danniesim/mecoai-chat that referenced this pull request Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants