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

Cannot access App Services in VS code (Internal Error) #2661

Closed
wittysuyu opened this issue Aug 22, 2024 · 9 comments · Fixed by #2662
Closed

Cannot access App Services in VS code (Internal Error) #2661

wittysuyu opened this issue Aug 22, 2024 · 9 comments · Fixed by #2662

Comments

@wittysuyu
Copy link

Issue

Not able to load azure resources in VS code using azure CLI... 

Operation 'Microsoft.Web/sites/read' failed as server encountered too many requests. Please try after '60' seconds. Tracking Id is '663dbaad-a145-4031-bf3e-04b2c45dba9c'.

Go to visual studio code
Sign into Azure
Visit the App Services under a specific subscription
Cannot load them

unable to load app services in sub 844f89f3-af43-43a6-9519-37b8e95ca138 only
image
the other subs are all good
image
tried to use command line to check directly and is able to reach the resources and deploy
image
from Azure portal, have the access to view the exact resource as well
image
only have issue list the resource in VS code portal
image
image

found a similar issue raised recently and is with logic app Azure/LogicAppsUX#4929, please help check and advise

@nturinski
Copy link
Member

Reopening until we confirm that the fix actually works and is released.

@nturinski
Copy link
Member

If you could help us test that our fix actually worked, please follow these steps:

  1. Download the zip file artifact from here: https://github.com/microsoft/vscode-azureappservice/actions/runs/10516435613/artifacts/1844660618
  2. Extract the .vsix file from the zip file
  3. In VS Code, hit F1 > Extensions: Install from VSIX
  4. Navigate to vscode-azureappservice.vsix
  5. Install and reload VS Code

If this resolves your issue, please let us know. It would help us greatly!

@wittysuyu
Copy link
Author

Thanks @nturinski for the suggestions. I will check with users having this issue and verify if it could work. Will post here once have any updates.

@nturinski
Copy link
Member

This fix is released. Please let me know if the users have had more success with the new release!

@wittysuyu
Copy link
Author

Hi @nturinski one of the users has confirmed the steps provided are okay to resolve the issue for now. Yet basically, we are wondering whether there is an official RCA for the incident please.

@nturinski
Copy link
Member

We don't have an official RCA or anywhere to to file it, but I can explain here.

The issue was caused by another extension loading all of the resources in parallel which caused the old caching logic to not work which resulted in many more requests to the Azure API than we had intended.

@wittysuyu
Copy link
Author

Thanks @nturinski for the explanation! Just per some further feedback from my customers that the issue has been resolved for him. However, some other colleagues are still encountering the same problem occasionally after following the steps outlined. Additionally, loading app names in VS Code is taking longer than expected.

If you have any suggestions or further steps to address these issues, could you please share them with us?

@nturinski
Copy link
Member

Hi @wittysuyu

Could you please share what versions of the Resources extension and the Azure App Service extension that they have installed?

@wittysuyu
Copy link
Author

Thanks @nturinski for the additional attention. As I have confirmed with my customer, since those who still getting the issue intermittently are not my direct cx, it is hard to check info with them. and since the issue is not so frequent, we agreed to put the issue on hold and will inform them to upgrade the extension to the latest just in case of next time they have similar issue. Thank you for your patience and explanation so far.

@microsoft microsoft locked and limited conversation to collaborators Oct 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants