cloudfoundry / cloudfoundry/stratos

Error status not cleared when disconnecting an endpoint

Open
#2,974 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
267
Forks
137
Avg merge
5h 14m
Merged PRs (30d)
77

Description

If you have an endpoint which causes the "We've been having trouble..." message to appear, then disconnecting it does not remove the warning message.

... neither does connecting it again

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the warning with an endpoint that causes the “We've been having trouble...” message, then disconnect and reconnect that endpoint while tracing the UI error state. Done means the warning is cleared after disconnecting and remains cleared when the endpoint is connected again.

Written by the indexing model from the issue text.

Assessment

Tech stack
angular, typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.