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

"Discard modified line" does not complete without switching focus on app #690

Closed
1 task done
Mikifarber1 opened this issue Apr 4, 2022 · 6 comments
Closed
1 task done
Labels
bug retest-requested Issue needs to be verified against latest version of app

Comments

@Mikifarber1
Copy link

Search existing issues

  • I have searched the issue tracker and confirmed that I was unable to find existing issues for the problem I am experiencing.

The problem

upon pressing the discard modify line for a certain line. the popup menu isn't reacting and I had to close the app and reopen it.
the operation occurred - meaning that the line was discarded.. but I had to close and open the app

+extra feature request: only when I'm pressing the line number I can perform the "discard modify line" and honestly I didn't know that you had this option.. can you change it that when I'm pressing the mouse right-click anywhere on the line then in the popup menu (copy/expand the whole file) you will add the discard button?

Release version

2.9.9

Operating system

linux

Steps to reproduce the behavior

No response

Log files

No response

Screenshots

No response

Additional context

No response

@shiftkey
Copy link
Owner

shiftkey commented Apr 4, 2022

@Mikifarber1 thanks for the report.

If you look at the logs you should see some messages like this:

2022-04-04T13:49:08.079Z - info: [ui] Executing discardChangesFromSelection: git apply --unidiff-zero --whitespace=nowarn - (took 17.471s)

Note that took value at the end there. On my machine it took over 17s, which isn't great for what's not a complex repoistory. Can you confirm you're also seeing a high number when you do this?

@shiftkey
Copy link
Owner

shiftkey commented Apr 4, 2022

+extra feature request: only when I'm pressing the line number I can perform the "discard modify line" and honestly I didn't know that you had this option.. can you change it that when I'm pressing the mouse right-click anywhere on the line then in the popup menu (copy/expand the whole file) you will add the discard button?

Please submit this to the upstream project as feedback: https://github.com/desktop/desktop

@shiftkey shiftkey added the bug label Apr 4, 2022
@shiftkey shiftkey changed the title discard modified line is stuck discard modified line does not complete without switching focus on app Apr 4, 2022
@shiftkey shiftkey changed the title discard modified line does not complete without switching focus on app "Discard modified line" does not complete without switching focus on app Apr 4, 2022
@Mikifarber1
Copy link
Author

@Mikifarber1 thanks for the report.

If you look at the logs you should see some messages like this:

2022-04-04T13:49:08.079Z - info: [ui] Executing discardChangesFromSelection: git apply --unidiff-zero --whitespace=nowarn - (took 17.471s)

Note that took value at the end there. On my machine it took over 17s, which isn't great for what's not a complex repoistory. Can you confirm you're also seeing a high number when you do this?

when I waited long enough I was able to press another button in the pop up window and to continue to work..

@Mikifarber1
Copy link
Author

+extra feature request: only when I'm pressing the line number I can perform the "discard modify line" and honestly I didn't know that you had this option.. can you change it that when I'm pressing the mouse right-click anywhere on the line then in the popup menu (copy/expand the whole file) you will add the discard button?

Please submit this to the upstream project as feedback: https://github.com/desktop/desktop

Done, desktop#14279

@shiftkey
Copy link
Owner

shiftkey commented Apr 4, 2022

Based on the symptoms I've published a new release 2.9.12-linux4 which has a different version of the Git package that I've been carrying around since the app was running on Electron 11 (and Node v12) that I think are now regressed because we're on Electron 17 (and Node v16) and no longer necessary.

So I've undone that change and I see this operation complete immediately when running locally, without needing to interact with the app again. Let me know if that works for your situation also.

@shiftkey shiftkey added the retest-requested Issue needs to be verified against latest version of app label Apr 8, 2022
@shiftkey
Copy link
Owner

Closing this out as I believe this has been resolved by the latest release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug retest-requested Issue needs to be verified against latest version of app
Projects
None yet
Development

No branches or pull requests

2 participants