microsoft / microsoft/vscode-azurecontainerapps
Fail to execute Container App actions after being idle for over 30 minutes
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 42
- Forks
- 21
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 2
Description
OS: Win 11
Build Version: 20251017.1
Repro Steps:
- Expand one Container App.
- Leave it idle for more than 30 minutes without performing any actions.
- Execute one action such as "Disable Ingress for Container App".
- Check whether succeeds to execute the action.
Expect:
Succeed to execute the action without any error,
Actual:
Fail to execute "Disable Ingress for Container App" action.
More Info:
This issue does not reproduce after refreshing Azure view or reloading VS Code.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure in the VS Code Azure Container Apps view by leaving an expanded Container App idle for over 30 minutes, then executing “Disable Ingress for Container App.” Compare this with the behavior after refreshing the Azure view or reloading VS Code; done means the action succeeds without requiring either workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript, vscode
- Domain
- cloud, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100