Coveralls incident
Some customers with active subscriptions receiving 402 ("repo paused") notice
Coveralls experienced a notice incident on February 19, 2024 affecting Coveralls.io API, lasting 14m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Feb 19, 2024, 06:09 PM UTC
The issue has been identified and a fix is being implemented.
- identified Feb 19, 2024, 06:28 PM UTC
If you were affected by this issue, the issue should be resolved in the next 15 minutes for you. Please check the status of your next CI build. You may wish re-run your previously failing CI build in order to send your coverage report(s) to Coveralls. Note: FAIL ON ERROR option: If you want to ensure that this type of error, or any other, will not break your CI pipelines, please set your integration's "FAIL ON ERROR" input option to `false`. How to Enable the "FAIL ON ERROR" input option: Coveralls GitHub Action users (`fail-on-error`): https://github.com/marketplace/actions/coveralls-github-action#:~:text=fail%2Don%2Derror,to%20any%20errors. Coveralls Orb for CircleCI users (`fail_on_error`): https://circleci.com/developer/orbs/orb/coveralls/coveralls#:~:text=boolean-,fail_on_error,-Whether%20to%20fail Coveralls Universal Coverage Reporter (`--no-fail`): https://github.com/coverallsapp/coverage-reporter#:~:text=For%20more%20options%20see
- monitoring Feb 19, 2024, 06:37 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 19, 2024, 06:43 PM UTC
This incident has been resolved. No repos for any active subscriptions should be returning the `402 repo paused` error from the Coveralls API. If you are experiencing this error, please get in touch with us at [email protected] and we'll sort you out asap. Thanks for your patience, everyone!