Stanford CS342 - Building for Digital Health
[Technical Questions] Failing PR Tests in Stanford Spezi Contact #153
-
In what area do you have a technical challenge?Other (non-StanfordBDHG-related) area Description[2025-03-07T03:16:24.311Z] ['error'] There was an error running the uploader: Error uploading to https://codecov.io: Error: There was an error fetching the storage URL during POST: 429 - {"message":"Rate limit reached. Please upload with the Codecov repository upload token to resolve issue. Expected time to availability: 2713s."} ReproductionForked Spezi Contact and pushed small bug fix / documentation update (worked on open issue). Then created a Pull Request to main Spezi Contact branch to update it. See here: StanfordSpezi/SpeziContact#33. Expected behaviorTest should've ran / passed. Additional contextNo response Code of Conduct
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Great question. This is unfortunately a know issue in @codecov; uploads from forks don't seem to work as they don't have access to the token. We have tried to update to later version of their tool but there were some challenges with the code coverage report upload from Xcode. For now, we can ignore the codecov upload error in the PR. |
Beta Was this translation helpful? Give feedback.
Great question. This is unfortunately a know issue in @codecov; uploads from forks don't seem to work as they don't have access to the token. We have tried to update to later version of their tool but there were some challenges with the code coverage report upload from Xcode. For now, we can ignore the codecov upload error in the PR.