microsoft
PR Functionality Unresponsive
I am not sure what changes were recently made to this software but it is not working more often than not for the past month or so.
Looking through the logs it appears there is some kind of timeout involved, as well as the following errors. Otherwise I dont see any possible errors in the logs.
2025-09-29 22:13:59.744 [error] [GitHubRepository+2] Unable to fetch PR: Error: GraphQL error: Could not resolve to a PullRequest with the number of XXX.
2025-09-29 22:13:59.744 [info] [FolderRepositoryManager+2] Found GitHub pr repo for pr #XXX: no
2025-09-29 22:13:59.761 [error] [GitHubRepository+3] Error querying GraphQL API (PullRequest): GraphQL error: Could not resolve to a PullRequest with the number of XXX..
2025-09-29 22:13:59.761 [error] [GitHubRepository+3] Unable to fetch PR: Error: GraphQL error: Could not resolve to a PullRequest with the number of XXX.
To resolve timeout/ connectivity issues it appears that turning off my VPN and restarting VS Code seems to help but I'm at a loss as to why this tool isn't reliable.
I love it when its working!
I'm unfamiliar with the inner workings of this extension or electron but I think maybe a conceptual way to fix it would be to store PR's local first so you could still format them, but offer some kind of a connectivity icon or warning in the case of the above problem (if that really is the issue)
@alexr00 this isn't a connectivity issue, my network connection works just fine. This is an issue with your application!!!!!!
@alexr00 We don't handle loss of connectivity well at all.
Is it expected that after a network failure, the PR will be unable to refresh comments even after pressing the refresh button (for the extension) or the refresh command in the context menu (for one PR)? I'm seeing the GHPR extension be unable to refresh so am investigating why that may be happening.
Is there a way to delete the GHPR extension's cache so that it's forced to refresh from server?
The only way to fully recover from loss of connectivity is the reload the extension. Not a good solution, I know.