cloudfoundry / cloudfoundry/stratos
App Summary Poll continues after failure
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
- After manual requests to start/stop/restage an app we poll for certain app states
- If the original request failed we're forever waiting for an un-achievable state
- seen when attempting to restage an app following a failed deploy of cf-quick-app (deploy failed due to routes quota exceeded, routes quota was then updated and restage attempted)
Contributor guide
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
Start by tracing the app summary polling triggered after manual start, stop, or restage requests, then reproduce the failed-deploy and restage scenario described in the issue. Done means polling stops or handles the failed original request instead of waiting indefinitely for an unachievable app state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100