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.

Sign up for GitHub

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

Jump to bottom

Websocket connection fails on workspace #3109

Closed
ashumilova opened this issue Nov 17, 2016 · 1 comment
Closed

Websocket connection fails on workspace #3109

ashumilova opened this issue Nov 17, 2016 · 1 comment
Assignees
@ashumilova
Labels
kind/bug Outline of a bug - must adhere to the bug report template.
Milestone
5.0.0

Comments

@ashumilova
Copy link
Contributor

ashumilova commented Nov 17, 2016 •
edited
Loading

In some cases the workspace+project creation flow fails due to websocket connection errors. The project creation step is not reached in this case, though we have running workspace.

image

Additional information:

  • Problem started happening recently, didn't happen in an older version of Che: [No]
  • Problem can be reliably reproduced, doesn't happen randomly: [No]
@ashumilova ashumilova added sprint/next status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. team/plugin labels Nov 17, 2016
@ashumilova ashumilova self-assigned this Nov 17, 2016
@ashumilova ashumilova added sprint/current status/in-progress This issue has been taken by an engineer and is under active development. and removed sprint/next status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. labels Dec 6, 2016
@riuvshin riuvshin added this to the 5.0.0-M8 milestone Dec 6, 2016
@riuvshin riuvshin added kind/bug Outline of a bug - must adhere to the bug report template. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. labels Dec 6, 2016
@bmicklea bmicklea modified the milestones: 5.0.0-M9, 5.0.0-M8 Dec 6, 2016
@bmicklea bmicklea removed the severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. label Dec 6, 2016
@ashumilova ashumilova mentioned this issue Dec 16, 2016
Merged
@ashumilova ashumilova added status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. and removed status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach status/in-progress This issue has been taken by an engineer and is under active development. status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. labels Dec 16, 2016
@ashumilova
Copy link
Contributor Author

Added handlers for closed connection - to inform user.
Also need to clean-up the browser cache.

@bmicklea bmicklea mentioned this issue Jan 13, 2017
Closed
70 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ashumilova ashumilova

Labels
kind/bug Outline of a bug - must adhere to the bug report template.
Projects
None yet
Milestone
5.0.0
Development

No branches or pull requests
3 participants
@ashumilova @riuvshin @bmicklea