-
Notifications
You must be signed in to change notification settings - Fork 211
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
Inconsistent - Token required because branch is protected #1580
Comments
Workaround is to close the PR and make a new one e.g. opensearch-project/opensearch-migrations#1019 |
I'm getting this quite a lot suddenly on https://github.com/google/osv-scanner - this only started happening in the last couple of weeks and afaik there have not been any changes to the branch protection rules (@another-rex could you confirm this?) Some action examples: |
@thomasrockhu can you please look into this one? 🙏 |
@thomasrockhu-codecov seems to be a better handle to ping :) |
@greg0ire @AndreKurait noting that I see this. Am asking the team what the expected behavior is but from what I can tell, we have always had protected branches require a token. @AndreKurait have you seen this come up again or was it that one time? |
@G-Rath please let me know if there was a change in branch protection rules |
@thomasrockhu-codecov I don't know as I'm not the owner of the repository, but I've not seen this failure for a few weeks so I assume it's just been fixed 🤷 |
@thomasrockhu-codecov I no longer see the _error message on my repository, but I still have an issue: the upload is never processed. I will file a separate bug report. |
Here it is: #1633 |
Going to close this one out for now, @greg0ire I'll take a look at that issue |
@thomasrockhu-codecov I just hit this again, can we reopen this? I only ever get it after pushing multiple commits after creating a PR. It appears to be a bug in detecting the fork
|
It's inconsistent because another action on the same commit passed
|
@AndreKurait got it, taking a look |
Leaving a tasklist of some issues/PRs that will mitigate/fix the issue
|
@bobleesj @AndreKurait we pushed a different change from the tasklist above that I think will solve a race condition we were having. Can you see if this issue is still happening? |
@thomasrockhu-codecov Thanks! Yup will do. |
@AndreKurait everything ok? I got a message in my email and just wanted to double-check |
We had some failures tonight with a new error message.
Made some PRs which passed, and some failed. I have a suspicion there's some throttling limits involved, so i set up some actions to retry 20 times, and observed this error message occur consistently. I looked into our use of tokens, and saw we were triggering our action on |
found it |
@AndreKurait we pushed a fix for this earlier today, can you try again? |
@thomasrockhu-codecov just wanted to share we've had no issues so far, around 3-4 PRs across 2-3 repos since then. |
This comment has been minimized.
This comment has been minimized.
This is still broken for me
Full output
|
@KATT do you mind trying on |
We use I can't test it without creating a new github user etc, so I'll see whenever a new PR drops in next, I force-merged the aforementioned one |
@KATT just wanted to ping back here and see if there's anything I can help with. |
@AndreKurait just wanted to check back and see if this was working for you |
I'm seeing resolution and working tokenless uploads on 5.0.5 Working Logs
And 5.0.6 Failed Logs
|
@AndreKurait on it, thanks |
@AndreKurait can you try |
@thomasrockhu-codecov v5.0.7 is working reliably. This has been a rough few months for us using codecov, do we have any tests added to ensure this continues to work as expected? |
@AndreKurait I'm so sorry that your experience has been pretty rough, that's obviously not our intention. We have built out some tests regarding the v5 release internally and I'll be building out some more infrastructure that is exposed to open source. There are definitely some cases we missed that we shouldn't have, and that's my fault. I am hoping that the silver lining for the issues in this release have been the attention and speed of fixes to the problems. If you have any suggestions on what else we can be doing better, please let me know. Given that I believe everyone in this thread has had their issues resolved, I'm closing this issue. |
On a public repo, i'm getting inconsistent results with codecov-v4
e.g. opensearch-project/opensearch-migrations#1016
First Run - Successful
Subsequent Run - Failure
The text was updated successfully, but these errors were encountered: