You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Created new workspace from ready-to-go node stack. Workspace is created immediately:
2016-02-24 17:07:12,058[nio-8080-exec-9] [INFO ] [o.e.c.a.w.s.WorkspaceManager 140] - EVENT#workspace-created# WS#default# WS-ID#workspacef4refa2ij5yqofhw# USER#che#
Browser gives this error in the console: http://xxx.net:8080/api/ext/project/workspacef4refa2ij5yqofhw 503 (Service Unavailable)
This shows in a browser as:
HTTP Status 503 - Request can't be forwarded to machine. Dev machine of workspace workspacef4refa2ij5yqofhw is not running.
I would expect the workspace to start as part of the creation process, and/or the api call should be handled by the server or client gracefully rather than giving 503 error.
The text was updated successfully, but these errors were encountered:
ghost
added
the
kind/question
Questions that haven't been identified as being feature requests or bugs.
label
Feb 25, 2016
Actually, when you create a workspace, you do not automatically run it. You may create it but not run in fact.
As to this API call, I'll check with User Dashboard team.
ddementieva
added
kind/bug
Outline of a bug - must adhere to the bug report template.
and removed
kind/question
Questions that haven't been identified as being feature requests or bugs.
labels
Feb 26, 2016
Created new workspace from ready-to-go node stack. Workspace is created immediately:
2016-02-24 17:07:12,058[nio-8080-exec-9] [INFO ] [o.e.c.a.w.s.WorkspaceManager 140] - EVENT#workspace-created# WS#default# WS-ID#workspacef4refa2ij5yqofhw# USER#che#
Browser gives this error in the console:
http://xxx.net:8080/api/ext/project/workspacef4refa2ij5yqofhw 503 (Service Unavailable)
This shows in a browser as:
HTTP Status 503 - Request can't be forwarded to machine. Dev machine of workspace workspacef4refa2ij5yqofhw is not running.
I would expect the workspace to start as part of the creation process, and/or the api call should be handled by the server or client gracefully rather than giving 503 error.
The text was updated successfully, but these errors were encountered: