cloudfoundry / cloudfoundry/stratos
Handle non-passthrough failures
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
- Metrics does not check response for errors, just dispatches success action regardless of content
- This was happening in the kube world too
- Need to check other effects to ensure we handle this
- Need to make calls that hit a single endpoint passthrough
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 metrics and kube effects that dispatch success actions without checking response errors, then inspect other effects for the same pattern. Done means non-passthrough failures are handled consistently and calls targeting a single endpoint use passthrough behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100