question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

The reset limit backoff code may not be timezone aware

See original GitHub issue

First of all a great useful action… been using it for multiple projects. For the first time I tried using it on a self hostet runner and faced this rare issue hence reporting. This is also the first time that I have faced the rate limiting response form GHA and I get a feeling that the code for retry backoff reset may not be timezone aware… see the attached log. Note the very last line shows that that next attempt will happen 5Hr 30 mins and 59 seconds later. though the authors intention is to try 1 minute later

Since this self hosted runner is running in India time which 5.5 hrs ahead of UTC… it is clearly a bug that instead of retrying after 1 minute it is adding the time zone offset as well.

  2022-02-24 21:15:38 +0530 - publish -  INFO - created check https://github.com/Apra-Labs/ApraPipes/runs/5321272796
  2022-02-24 21:15:38 +0530 - publish-unit-test-results - WARNING - Request GET /search/issues?q=type%3Apr+repo%3A%22Apra-Labs%2FApraPipes%22+e10e0c3b16257b9be2a05ed3df65554798615562&per_page=100 failed: Forbidden
  2022-02-24 21:15:38 +0530 - publish - WARNING - Request GET /search/issues?q=type%3Apr+repo%3A%22Apra-Labs%2FApraPipes%22+e10e0c3b16257b9be2a05ed3df65554798615562&per_page=100 failed with 403: Forbidden
  2022-02-24 21:15:38 +0530 - publish-unit-test-results -  INFO - There is no Retry-After given in the response header
  2022-02-24 21:15:38 +0530 - publish-unit-test-results -  INFO - Response body indicates retry-able error: you have exceeded a secondary rate limit. please wait a few minutes before you try again.
  2022-02-24 21:15:38 +0530 - publish-unit-test-results -  INFO - Reset occurs in 5:30:59.330597 (2022-02-24 21:16:38), setting next backoff to 19859.330597s

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:10 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
EnricoMicommented, Feb 24, 2022

Can you please test the fix?

uses: EnricoMi/publish-unit-test-result-action/composite@branch-fix-reset-timestamp-utc
1reaction
EnricoMicommented, Feb 24, 2022

Thanks for reporting, this is valuable. I will look into this.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Reset timezone aware timestamp momentjs - Stack Overflow
I am using momentjs for doing my date operations and want to code a scenario where if timestamp is given, and timezone name...
Read more >
Using Coinmarketcap API with Python - gists · GitHub
Implement a "Retry with exponential backoff" coding pattern for your REST API call logic. This means if your HTTP request happens to get...
Read more >
JobInfo.Builder - Android Developers
Set deadline which is the maximum scheduling latency. ... This is because back-off typically does not make sense for these types of jobs....
Read more >
Configuration | Apache Flink
You can configure checkpointing directly in code within your Flink job or application. Putting these values here in the configuration defines them as...
Read more >
Workflows | Temporal Documentation
This guide provides a comprehensive overview of Temporal Workflows.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found