Skip to content

Add a hook for handling background rate limit errors #2294

Add a hook for handling background rate limit errors

Add a hook for handling background rate limit errors #2294

Triggered via pull request December 21, 2025 01:39
Status Cancelled
Total duration 1m 11s
Artifacts

ci.yml

on: pull_request
Matrix: test
Lint Commit Messages
17s
Lint Commit Messages
lint
17s
lint
Build Package
8s
Build Package
Test Semantic Release
49s
Test Semantic Release
release
0s
release
Fit to window
Zoom out
Zoom in

Annotations

6 errors
Lint Commit Messages
You have commit messages with errors ⧗ input: Add a hook for handling background rate limit errors When a rate limit error is received the background loop will jump to the maximum backoff (now 6 hours) and will also invoke a callback so that the caller can decide to re-authenticate or stop harder. The new backoff follows this trajectory, where the change in behavior is introduced after 15 attempts: - attempt 1: wait 10 seconds - attempt 5: waits 50 seconds - attempt 7: waits 2 minutes - attempt 10: waits 6 minutes - attempt 15: waits 32 minutes - attempt 17: waits 2 hours - attempt 20: waits 6 hours ✖ subject may not be empty [subject-empty] ✖ type may not be empty [type-empty] ✖ found 2 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint
test (3.11)
Canceling since a higher priority waiting request for mqtt-unauthorized exists
test (3.11)
The operation was canceled.
test (3.14)
Canceling since a higher priority waiting request for mqtt-unauthorized exists
test (3.14)
The operation was canceled.
CI
Canceling since a higher priority waiting request for mqtt-unauthorized exists