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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Copy Permalink fails frequently, seemingly on the first copy of the day #5185
Comments
I see this frequently; I had thought it was a me problem 馃槄 . |
@meganrogge I added more logging. Can you set the default log level of GitHub Pull Request to "debug" and then share logs the next time you see this? |
Closing, @Tyriar and @meganrogge if you see it please share logs! |
This still happens constantly for me, looking at the logs it looks like the issue might be me expecting it to happen immediately but it's taking over 3 seconds:
Can we make it near instant? I'm not sure why it takes so long to get the commit hash, the extension should already know what it is? |
We are currently making 2 git calls to get the commit hash. I can reduce it to 1, but we still need the one to tell if the file is actually under source control. Let's see if that helps. |
* Speed up copy permalink Fixes #5185 * Fix test
@alexr00 could we do that eagerly in the background when the repo commit changes locally as that shouldn't happen often? |
@Tyriar it's per file, so we would have to eagerly make the call every time you change files. |
Typical repro (I haven't nailed it down entirely):
GitHub Issues: Copy GitHub Permalink
, 馃悰 fails sometimesI have been hitting this for literally years and it's one of my biggest papercuts, but since it's such a pain to reproduce I never end up following it up after mentioning it. Since it's so annoying I think it's worth spending a couple of hours in a debug session together, restarting my computer if that's what it takes.
Trace logs:
GitHub Pull Request:
Git:
The text was updated successfully, but these errors were encountered: