23 Jan 2023 18:22:50.018212 <190>1 2023-01-23T23:22:49.795912+00:00 app web.1 - - Error while posting a comment: Server responded to GraphQL request with errors: Resource not accessible by integration
This is an authorization scope problem. Did it happen with an existing request or a new one? We might need to expand the permissions that coqbot asks for.
It was a transient error that occurred when coqbot tried to reply to my comment. When I tried the same thing again later, it worked fine.
OK, in this case, I guess this must have been a bug on GitHub's end.
Seeing it again at
01 Mar 2023 16:04:11.500212 <190>1 2023-03-02T00:04:11.094883+00:00 app web.1 - - Error while posting a comment: Server responded to GraphQL request with errors: Resource not accessible by integration
Do you know where it was supposed to post? If that's a standard repo (where it usually posts) or another one? If that's the former, then this is definitely on GitHub and we should report it to them. I wonder if there are any additional information we could extract, so that they can investigate the bug.
It's a standard repo, it was supposed to post to coq-community/run-coq-bug-minimizer. (Maybe we should have it log the info about the comment it was trying to post when it errors? Or does it already do this and I just didn't copy the relevant lines?)
Then it's normal, because coqbot is not installed on coq-community/run-coq-bug-minimizer. It is currently installed only on docker-coq and docker-base in this organization.
We can modify the installation so that it is also installed there. However, we will hit the issue that currently coqbot tries to sync any repo where it is installed to a GitLab counterpart. Ideally, we should make this feature optional, or even not activated by default (if no coqbot.toml configuration file, for instance). More realistically, we could create a run-coq-bug-minimizer GitLab mirror so that coqbot does not hit a wall when trying to sync this repo.
Last updated: May 28 2023 at 18:29 UTC