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

Request review always* fails #76440

Closed
Brambor opened this issue Sep 14, 2024 · 5 comments · Fixed by #78256
Closed

Request review always* fails #76440

Brambor opened this issue Sep 14, 2024 · 5 comments · Fixed by #78256
Labels
Code: Tests Measurement, self-control, statistics, balancing. (S2 - Confirmed) Bug that's been confirmed to exist

Comments

@Brambor
Copy link
Contributor

Brambor commented Sep 14, 2024

Describe the bug

Request review either concludes that nobody is to be pinged and then successfully ends. Or it finds somebody to ping and then fails instead of requesting the review.

image

from:

Attach save file

N/A

Steps to reproduce

I am not sure. Make a PR with changes to a file somebody is subscribed to? Make it Qrox to be sure it fails.

Expected behavior

I would either disable the test or fix it. Currently, it gives no value. It never requests a review which is the whole point.

Screenshots

No response

Versions and configuration

N/A

Additional context

Search "request review" on Discord for more insight.

@Brambor Brambor added the (S1 - Need confirmation) Report waiting on confirmation of reproducibility label Sep 14, 2024
@GuardianDll GuardianDll added (S2 - Confirmed) Bug that's been confirmed to exist Code: Tests Measurement, self-control, statistics, balancing. and removed (S1 - Need confirmation) Report waiting on confirmation of reproducibility labels Sep 15, 2024
@Brambor
Copy link
Contributor Author

Brambor commented Sep 22, 2024

@RenechCDDA
Copy link
Member

Because Korggent has push permissions and it never triggered iscollaborator(), I'm pretty sure.

https://github.com/Qrox/auto-request-review/blob/481e6cd2f5d57b6e914d81ca731211384a76798f/src/github.js#L114-L118

My best guess is that either the octokit module is no longer supported (doesn't seem to be the case) or there has been some unknown permissions requirement increase. Taking a look at the actions log it looks like the failures started on June 8th... I was kind of hoping to use the logged failures to figure out what happened but uh, this PR couldn't have caused it. Checked github's blog, nothing terribly suspicious around that date.

@RenechCDDA
Copy link
Member

@Qrox Any chance you could lend us your wisdom?

Harakka seemed to think it was an API change and also identified that function so that's what I'm going with 🤷

image

@Qrox
Copy link
Contributor

Qrox commented Oct 18, 2024

If it is failing inside is_collaborator and throwing an error, then my best guess is that the returned error status when a user is not a collaborator is somehow not 404, which will trigger this line. When the user is a collaborator, the returned status is 204 so it succeeds. I haven't tested though.

@Procyonae
Copy link
Contributor

Procyonae commented Nov 26, 2024

Qrox/auto-request-review#1 should hopefully fix it (we'll need to update https://github.com/CleverRaven/Cataclysm-DDA/blob/master/.github/workflows/request-review.yml#L23 to the new commit)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Code: Tests Measurement, self-control, statistics, balancing. (S2 - Confirmed) Bug that's been confirmed to exist
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants