Coveralls is in Read Only mode while we work on updating the system. Sorry for the inconvenience.
VIGILANCE! Check this page any time you notice a problem with coveralls
422 Errors for users of coveralls-python with Github Actions
Incident
Report for Coveralls
Resolved
This incident has been resolved.
Update
We are getting reports that the issue is resolved for several users using coveralls-python with Github Actions for CI.
We'd like to hear from you if this is not the case for your workflows: support@coveralls.io
We'll monitor for another 1-2 hrs before we mark this incident resolved.
We'd like to hear from you if this is not the case for your workflows: support@coveralls.io
We'll monitor for another 1-2 hrs before we mark this incident resolved.
Monitoring
We have implemented a fix for this issue and are monitoring the results. If you are still experiencing this issue, please let us know at support@coveralls.io.
Investigating
We are investigating and trying to resolve an incident that seems related to a previous incident, now resolve, here:
https://status.coveralls.io/incidents/pgcdqr7r4lgj
We believe that some recently deployed changes, which appeared to affect customers using the Coverage Reporter and Github Action for several hours on Fri, Apr 28, seems to still be affecting customers using the coveralls-python integration with Github Actions.
This issue, submitted by user andy-meier, provides both a description, and a workaround that solved his issue:
https://github.com/lemurheavy/coveralls-public/issues/1710
We are hoping to identify a root cause of the issues he describes, to prevent other users from having to go to the same lengths.
We will be posting updates here, and in that issue.
https://status.coveralls.io/incidents/pgcdqr7r4lgj
We believe that some recently deployed changes, which appeared to affect customers using the Coverage Reporter and Github Action for several hours on Fri, Apr 28, seems to still be affecting customers using the coveralls-python integration with Github Actions.
This issue, submitted by user andy-meier, provides both a description, and a workaround that solved his issue:
https://github.com/lemurheavy/coveralls-public/issues/1710
We are hoping to identify a root cause of the issues he describes, to prevent other users from having to go to the same lengths.
We will be posting updates here, and in that issue.
This incident affected: Coveralls.io API.