Open martindekov opened 4 years ago
We didn't have this issue prior to merging the status change for the DCO and the change @Waterdrips made to use the new endpoint for installation tokens.
I would expect one of the above to be related to the regression, as Derek has never shown this error before - neither in local testing or deployed for users.
Can one of you raise a support issue with GitHub please?
Check rate limits as per description https://docs.github.com/en/rest/reference/rate-limit#understanding-your-rate-limit-status since the DCO feature increases the number of API calls.
You have 5000 (up from 50) per hour for properly authenticated requests, this appears to be a misconfiguration? Are there new limits on how the access tokens can be used?
You have 5000 (up from 50) per hour for properly authenticated requests, this appears to be a misconfiguration? Are there new limits on how the access tokens can be used?
I marked this ^ as not a problem, at least from my testing. We generate new token for every request which has those limits refreshed. I opened a ticket here: https://support.github.com/ticket/personal/0/796320
https://github.com/martindekov/push2/pull/48
Red is check_suite
which is not supported event.
Can't seem to replicate the issue now with alexellis/derek:0.10.0
image
Inconsistent error:
This error is here: https://github.com/alexellis/derek/blob/16d7143de95fbc1516be7377b7388995a78b19c0/handler/pullrequest_handler.go#L242
And the function is: https://github.com/alexellis/derek/blob/16d7143de95fbc1516be7377b7388995a78b19c0/handler/pullrequest_handler.go#L235
Things I went through while trying to make the error consistent and it didn't:
Expected Behaviour
Every request for the commits has the same behavior on error or success.
Current Behaviour
Requesting the commits in a PR is inconsistent and might fail.
Possible Solution
In this case we can re-try the request. Possibly if the problem is in the access token we can revisit how we request the token, or fix the error flow of the token.
Steps to Reproduce (for bugs)
Context
This can potentially lead to inconsistency when checking for DCO as if the error is present and derek will fail to list the commits and recognize if there is unsigned one.
Your Environment
or
docker version
(e.g. Docker 17.0.05 ): N/A