-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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.
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
Workspace undefined successfully created #500
Comments
Is this an appropriate use of issues in your github? Do you want me to keep raising issues for bugs I find? |
Yes, this is the right way to report issues. So, you have given your ws a name, but the UI message says otherwise? |
Yes exactly, it says 'undefined' where I would expect it to say the name of the workspace just created. |
What Che version do you use? |
Nightly 25.02.2016 |
Issue confirmed. The team is working on a fix. |
Fixed in master - 4.1.0-RC1-SNAPSHOT |
…checkers. Introduce wsagent ping success threshold Signed-off-by: Ilya Buziuk <ibuziuk@redhat.com>
…checkers. Introduce wsagent ping success threshold Signed-off-by: Ilya Buziuk <ibuziuk@redhat.com>
…checkers. Introduce wsagent ping success threshold Signed-off-by: Ilya Buziuk <ibuziuk@redhat.com>
…threshold' property for wsagent's server checker and liveness probe. Signed-off-by: Ilya Buziuk <ibuziuk@redhat.com>
…threshold' property for wsagent's server checker and liveness probe. Signed-off-by: Ilya Buziuk <ibuziuk@redhat.com>
…eshold' property for server checker and liveness probe configuration. Signed-off-by: Ilya Buziuk <ibuziuk@redhat.com>
…eshold' property for server checker and liveness probe configuration. Signed-off-by: Ilya Buziuk <ibuziuk@redhat.com>
…perty for server checker and liveness probe configuration. Signed-off-by: Ilya Buziuk <ibuziuk@redhat.com>
When creating a new workspace, a growl type message is shown in the ui saying 'Workspace undefined successfully created'. I assume this should say 'Workspace -name- successfully created'.
The text was updated successfully, but these errors were encountered: