-
Notifications
You must be signed in to change notification settings - Fork 400
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
ERROR: create_app: Exception in /api/conversation cannot access local variable ' answer' where it is not associated with a value #1302
Comments
Hello @yaowilli , Could you let us know about any other changes you made to the app settings before or after deployment? |
@Prasanjeet-Microsoft I made the following before : 1/ disabled all public all public access |
Hello @yaowilli , Did you change the GPT model or make any other configuration changes in the application? |
@Prasanjeet-Microsoft yes I changed the GPT to gpt-4o and embedding to text-embedding-ada-002 USE_KEY_VAULT set to true |
Hello @yaowilli , This is to inform you that text-embedding-ada-002 is the default value of Azure Open AI Embedding Model for this accelerator. However, we have tried to deploy this accelerator with gpt-4o model and have not been able to reproduce the issue so far. Could you please provide the value of the AZURE_AUTH_TYPE environment variable from the app settings? |
The issue is sporadic it occurs when you do not expect it |
Hello @yaowilli , Could you please investigate further using Application Insights to check for any exceptions or additional details? I believe there might be some relevant information that could help us diagnose the issue more precisely. Could you please follow the steps outlined below as an example. Go to Application Insights resource: In the Application Insights resource menu on the left, under Investigate, select the Failures option: Select the time range as Last 7 days or 30 days and click on Apply: Click on 500 response code: Click on suggested view details: Click on each exception and provide a screenshot for each one: |
ok will do I am out of office at moment |
getting the same error after switching from Azure OpenAI model gpt-4 to gpt-4o - error is intermitent:
|
@yaowilli We are already working on this, and the issue has been resolved. We will update you once it is published. |
Hello @yaowilli , We would like to inform you that the code fix has been published. You can now redeploy the accelerator and run your tests. Please inform us once you’ve completed the testing so we can close this GitHub issue. |
Hi @Prasanjeet-Microsoft is there a way I could obtain the code fixes via container deployment ? |
Hi @yaowilli, apologies for the delayed response. This accelerator already has container deployment in place, so there's no need to redeploy it. You can go ahead and run the test in your deployed accelerator. Thank you. |
Hi @yaowilli, just wanted to check if you’ve had a chance to run the tests on your deployed accelerator. Please update us on your progress when you can, so we can move forward and close this issue. Thank you! |
I am sorry it seems to be working now thanks I was waiting to perform more testing |
@yaowilli Thank you for your confirmation. If your issue has been resolved, can we go ahead and close this issue? |
Describe the bug
This issue is observed when simply chatting with the chat App
ERROR: create_app: Exception in /api/conversation cannot access local variable ' answer' where it is not associated with a value
UnboundLoca1Error: cannot access local variable 'answer' where it is not associated with a value
Expected behavior
I would expect a clear answer with no error
Debugging information
Steps to reproduce
Steps to reproduce the behavior:
Screenshots
Logs
ERROR: create_app: Exception in /api/conversation cannot access local variable ' answer' where it is not associated with a value
UnboundLoca1Error: cannot access local variable 'answer' where it is not associated with a value
Tasks
To be filled in by the engineer picking up the issue
The text was updated successfully, but these errors were encountered: