fix(codecov): add retry logic to codecov collection

[ReenigneArcher]

Description

Another attempt to fix codecov failures.

Screenshot

Issues Fixed or Closed

• Fixes codecov regularly fails to update #64

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (4)

src/updater.py:48

• [nitpick] The variable name 'max_tries' is not very descriptive. Consider renaming it to 'max_retries' for better clarity.

max_tries = 5

src/updater.py:49

• [nitpick] The variable name 'count' is not very descriptive. Consider renaming it to 'retry_count' for better clarity.

count = 0

src/updater.py:61

• The error message raised when 'data' is not available is not very descriptive. Consider including more context in the error message.

raise requests.exceptions.HTTPError(f'Error: {response.text}')

src/updater.py:52

• Ensure that the retry logic and exponential backoff are covered by tests.

while count < max_tries:

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud