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.

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

Che ignores user response when asks whether it should restore workspace or not #1849

Closed
vkuznyetsov opened this issue Jul 19, 2016 · 10 comments
Assignees
Milestone

Comments

@vkuznyetsov
Copy link

When there is workspace snapshot and user opens IDE it asks whether workspace should be restored or not. If user press cancel IDE does not send request to restore but default restoring behavior restores WS anyway.

Reproduction Steps:

  1. Start workspace
  2. Create a snapshot
  3. Stop workspace
  4. Refresh window
  5. Click 'no' in Workspase recovering popup.

Expected behavior:

Correct behavior should be either Che doesn't ask user about restoring or send request with flag that forbids restoring enabled by default.

Observed behavior:

Default restoring behavior restores WS

@vkuznyetsov vkuznyetsov added kind/bug Outline of a bug - must adhere to the bug report template. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. sprint/next team/enterprise labels Jul 19, 2016
@vkuznyetsov
Copy link
Author

@vinokurig vinokurig added status/in-progress This issue has been taken by an engineer and is under active development. and removed status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. labels Jul 19, 2016
@vinokurig
Copy link
Contributor

vinokurig commented Jul 20, 2016

@slemeur Please chose the behavior in this case:

  1. Since we have snapshot auto-restore we can remove asking user to restore from snapshot. But auto-restore can be disabled and user can not enable it by himself. So if user will have snapshot and the auto-restore will be disabled user will not be able to restore ws from snapshot.
  2. Also we can modify the start ws API request with flag that forbids restoring, if it is enabled by default.

@slemeur
Copy link
Contributor

slemeur commented Jul 20, 2016

System define default behaviors - but the user must keep the control on what will happen. So, do not remove this ability for the user, but modify the API to take into account the choice made by the user.

In the future, we'll have this wizard to restart a workspace from the IDE:
restart

The checkbox, will be checked/unchecked by default depending on first:
1- Default system behavior
2- Workspace's configuration for this option

@TylerJewell
Copy link

-1 on this behavior. It is not a suitable Ux.

@vinokurig
Copy link
Contributor

@TylerJewell What should we do in this case?

@TylerJewell
Copy link

My -1 is to Stevan's wizard behavior not this issue.

@garagatyi
Copy link

@slemeur @TylerJewell Can you elaborate on which UX is OK. We prefer having spec on what should be done before we will change API.

@garagatyi
Copy link

Right now we considering API changes that will allow IDE to either:

  • start workspace with restore
  • start workspace without restore (no matter if auto-restore is enabled)
  • start workspace and rely on auto-restore behavior

Please describe how workspace dialog should work. Then we will be able to implement needed changes.

@slemeur
Copy link
Contributor

slemeur commented Jul 21, 2016

The API description you are providing is the good one.

@TylerJewell : your feedback is about the UI, not about the ability for the user to choose if he wants to restart the workspace from snapshot, right?

@TylerJewell
Copy link

You should start on the API.

My issue is with the IDE ui and dialog box which needs to change. I do not think we will have a Ux design quickly so just do the API change now.

@vinokurig vinokurig added kind/bug Outline of a bug - must adhere to the bug report template. status/in-progress This issue has been taken by an engineer and is under active development. sprint/current team/enterprise and removed kind/bug Outline of a bug - must adhere to the bug report template. sprint/current status/in-progress This issue has been taken by an engineer and is under active development. team/enterprise labels Jul 26, 2016
@vinokurig vinokurig removed status/in-progress This issue has been taken by an engineer and is under active development. team/enterprise labels Jul 26, 2016
@vinokurig vinokurig added this to the 4.6.0 milestone Jul 28, 2016
@bmicklea bmicklea mentioned this issue Jul 28, 2016
64 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants