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

"unable to restore" prompt appears when restore takes time to complete #7652

Closed
shiftkey opened this issue May 30, 2019 · 4 comments · Fixed by #7757
Closed

"unable to restore" prompt appears when restore takes time to complete #7652

shiftkey opened this issue May 30, 2019 · 4 comments · Fixed by #7757
Labels
bug Confirmed bugs or reports that are very likely to be bugs priority-2 Bug that affects more than a few users in a meaningful way but doesn't prevent core functions
Projects

Comments

@shiftkey
Copy link
Member

Description

The warning we have setup to originally indicate that a stash cannot be restored also appears as part of the normal restore flow:

Version

  • GitHub Desktop: 1.7.1-beta1
  • Operating system: Windows 10

Steps to Reproduce

  1. Setup a stash to restore (I've been able to see this with as few as 3 files, but 20+ is a good number)
  2. Restore the stash

Expected Behavior

Some indicator of progress while restoring the stash would be nice, but other than that the experience is fine.

Actual Behavior

Midway through the restore process the alert about "Unable to restore stash..." appears and then disappears:

restore-warning-appears-during-restore

This is confusing in a couple of ways:

  • the ⚠️ indicator suggests something hazardous
  • how it appears and disappears while I'm waiting makes me a bit nervous
@billygriffin
Copy link
Contributor

Oof, yes. I don't like this at all - that's a rough experience. It's not blocking the workflow but does create unnecessary confusion and uncertainty. Just getting back into this, but this feels like a priority 2 bug and pretty high priority on the things to fix for stashing.

@billygriffin billygriffin added bug Confirmed bugs or reports that are very likely to be bugs priority-2 Bug that affects more than a few users in a meaningful way but doesn't prevent core functions labels May 31, 2019
@tierninho
Copy link
Contributor

Good catch 👍 Confirming I can repro with one stash on Mac.

@shiftkey shiftkey self-assigned this Jun 6, 2019
@shiftkey
Copy link
Member Author

shiftkey commented Jun 6, 2019

The fix I had in mind for this overlaps with what's currently happening in #7683, so I'm gonna pause that and keep an eye on that PR.

@shiftkey shiftkey removed their assignment Jun 6, 2019
@iAmWillShepherd
Copy link
Contributor

Oof, yes. I don't like this at all - that's a rough experience. It's not blocking the workflow but does create unnecessary confusion and uncertainty. Just getting back into this, but this feels like a priority 2 bug and pretty high priority on the things to fix for stashing.

I've added this to the stashing priority list for discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bugs or reports that are very likely to be bugs priority-2 Bug that affects more than a few users in a meaningful way but doesn't prevent core functions
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

4 participants