You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 24, 2019. It is now read-only.
I'll describe the problems we ran into this morning on a project; not sure about the best way to resolve them.
A read-only user was added to a private repo, which prevented the webhook from updating the GitHub status about the coverage. Here is the error message:
Unable to set pending status to vokal/project-api/54825ba as username, user's oauth token may have expired, not have push access for the repo, or the sha may not exist: {"message":"Not Found","documentation_url":"https://developer.github.com/v3"}
That read-only user was then removed from the repo, but since I believe the user's auth token was cached, CVR could no longer access new commits to properly add updated coverage reports:
The commit 54825ba does not exist
But we verified that was the correct commit.
The text was updated successfully, but these errors were encountered:
Note this appears to have happened for a user that had push rights which were revoked. That doesn't make the issue less valid, cvr should be able to recover better on those types of permission failures.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'll describe the problems we ran into this morning on a project; not sure about the best way to resolve them.
A read-only user was added to a private repo, which prevented the webhook from updating the GitHub status about the coverage. Here is the error message:
That read-only user was then removed from the repo, but since I believe the user's auth token was cached, CVR could no longer access new commits to properly add updated coverage reports:
But we verified that was the correct commit.
The text was updated successfully, but these errors were encountered: