Can't start a review from a comment due to GraphQL error

[yoavbls]

When starting a review from a comment:

A GraphQL error appears:

2024-11-09 22:52:00.572 [error] GitHubRepository+0> Error querying GraphQL API: GraphQL error: Fragment ReviewComment was used, but not defined. useAndDefineFragment
2024-11-09 22:52:00.572 [error] PullRequestModel> Failed to get pull request review comments: Error: GraphQL error: Fragment ReviewComment was used, but not defined

I thought it related to this: #6441 but it happens also in the pre-release version

• Extension version: v0.100.1
• VSCode Version: 1.95.2
• OS: macOS
• Repository Clone Configuration (single repository/fork of an upstream repository): Private repository
• Github Product (Github.com/Github Enterprise version x.x.x): Github.com

Steps to Reproduce:

1. Write a comment
2. Click on "Start Review"

[yoavbls]

Update: it also affects the load of existing comments.
Everything is fine in the version of November 5 so I think it is this change that moves the fragment out of reach of the query: 8434973

[valajczech]

Yup I have the same problem

[BenGale]

Same problem.

[christianvari]

Same issue

[DavidLangva]

same. I also can't leave one off comments

[michel-smarticket]

Same

[YashBhardwajAdpushup]

same

[koliyo]

Workaround, rollback to older version locally: Right click the extension in the marketplace tab, select "Install Specific Version", and pick v0.100.0.

[consdu]

thanks @koliyo

[jpomfret]

I have the same issue - confirmed the workaround works for me.

[ptraeg]

@koliyo Thanks - that fixed it for me as well.

[tristanbiesecker]

Same problem for me as well. Workaround fixed it.

[jacobharrison93]

Same problem for me as well

[MatthewKelseyRT]

Same for me, the workaround fixed it.

[JoeLyga]

Same problem. The workaround avoids the issue.

[jirihon]

Same problem for me.

[ian-blankinship-FHR]

Same problem for me.

[assafmo]

Rolling back to v0.100.0 fixed it, thanks @koliyo!

[Shamik-07]

Add me to this list as well

[dwillhelm]

Same

[Shamik-07]

Rolling back to v0.100.0 fixed it, thanks @koliyo!

This works for now

[pelord]

Rolling back to v0.100.0 fixed it.

[sg-tanner]

Rollback noted, just wanted to add that for weeks now I have had trouble with the extension in general loading the files changed when trying to expand the PR in the "Requests" pane. Wondering if this is related. Because I tried to skip the loading issue by right clicking the PR and selecting "Checkout pull request"

[baruchiro]

It's the same in review mode on the browser. Can revert to the previous version there

[gihankarunarathne]

Facing the same issue when trying to add a comment.

Need quick support!

[UrielZohar]

BE CAREFUL WITH DOWNGRADE THE EXTENTION VERSION YOU WILL LOSE THE COMMENTS YOU ALREDY WROTE

[BenGale]

When I was running into the issue it looked like those comments are gone anyway, they never get through to GitHub.

[pereyra-m]

Same here

[patricio-hondagneu-simplisafe]

Experiencing the same issue. Installing version v0.100.0 fixes it so it appears to be a regression.

[rubenarturopj]

Same issue

[ysuzuki19]

temporary solution

1. If you have failed comment locally, you should memo it.
2. Open Extensions (Ctrl+Shift+X)
3. Find GitHub Pull Requests
4. Open pull-down on Uninstall button
5. Select Install Specific Version...
6. Select 0.100.0
7. Client Restart Extensions

[Ardrete]

Same here, only rollbacking to version v0.98.0 worked for me, I am using github enterprise version 3.2.6

[joaomoreno]

Thanks @ysuzuki19 for providing steps for a workaround for the time being. We will release a fixed version early next week.

[arjentraas]

Rolling back to a previous version (100.0, or 98.0) doesn't work for me. Using VSCode in WSL.

[klausbadelt]

Downgrading is not an option in GitHub Codespaces - "Install Specific Version..." is disabled for this extension.

Revewing PRs in Codespaces is therefore 100% broken, with no workaround.

[klausbadelt]

Hi @alexr00 - since all PR reviews are broken in Codespaces, without any workaround (posted here), could this get a priority boost?

[bmlaw]

GitHub Education user: Now we are unable to leave feedback on any of our students' work, since the GitHub Education feedback mechanism is through a pull request. It's the middle of November. This is not a good time to not be able to leave feedback on any of our students' work.

[michaelk-redis]

Same issue for me. Roll back to 0.100.0 version helps.