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

UD and workspace-loader should subscribe to output on a specific endpoint provided by Workspace API #11526

Closed
garagatyi opened this issue Oct 8, 2018 · 2 comments
Closed

UD and workspace-loader should subscribe to output on a specific endpoint provided by Workspace API #11526

garagatyi opened this issue Oct 8, 2018 · 2 comments
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@garagatyi
Copy link

Description

Workspace API provides a specific endpoint for clients.
For the time being, we have it equal to the main Che master websocket endpoint, but it is possible to move it to another service.
Unfortunately, clients do not use endpoints from Workspace API response and construct endpoint URL themselves. Apart from that, clients do not respect that it is needed to subscribe to statuses and output on different endpoints and that URL is returned on workspace start call and might not be static and available whenever a client wants.

Reproduction Steps

OS and version:

Diagnostics:
@garagatyi garagatyi added kind/task Internal things, technical debt, and to-do tasks to be performed. team/ide2 labels Oct 8, 2018
@garagatyi
Copy link
Author

See #11459 (comment)

@evidolob evidolob mentioned this issue Nov 1, 2018
Closed
26 tasks
@ashumilova ashumilova mentioned this issue Nov 8, 2018
Closed
23 tasks
@ashumilova ashumilova mentioned this issue Nov 27, 2018
Closed
43 tasks
@evidolob evidolob mentioned this issue Dec 19, 2018
Closed
34 tasks
@evidolob evidolob mentioned this issue Jan 9, 2019
Closed
40 tasks
@evidolob evidolob mentioned this issue Jan 30, 2019
Closed
43 tasks
@evidolob evidolob mentioned this issue Feb 20, 2019
Closed
40 tasks
@ashumilova ashumilova mentioned this issue Mar 12, 2019
Closed
36 tasks
@evidolob evidolob mentioned this issue Apr 3, 2019
Closed
50 tasks
@ashumilova ashumilova mentioned this issue Apr 23, 2019
Closed
25 tasks
@evidolob evidolob mentioned this issue May 6, 2019
Closed
26 tasks
@che-bot
Copy link
Contributor

che-bot commented Sep 17, 2019

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 17, 2019
@che-bot che-bot closed this as completed Sep 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ashumilova @garagatyi @che-bot