Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ref: remove try: around parse_percentage #87368

Merged
merged 1 commit into from
Mar 19, 2025

Conversation

asottile-sentry
Copy link
Member

given the parser input values it cannot fail

given the parser input values it cannot fail
@asottile-sentry asottile-sentry requested review from a team March 18, 2025 23:32
@asottile-sentry asottile-sentry requested a review from a team as a code owner March 18, 2025 23:32
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Mar 18, 2025
Copy link

codecov bot commented Mar 19, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #87368      +/-   ##
==========================================
+ Coverage   85.27%   85.34%   +0.07%     
==========================================
  Files        9864     9864              
  Lines      559031   559024       -7     
  Branches    22043    22043              
==========================================
+ Hits       476703   477115     +412     
+ Misses      81604    81185     -419     
  Partials      724      724              

@asottile-sentry asottile-sentry merged commit ead6308 into master Mar 19, 2025
49 checks passed
@asottile-sentry asottile-sentry deleted the asottile-parse-percentage-infallible branch March 19, 2025 16:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: Backend Automatically applied to PRs that change backend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants