Fix parse invalid interval string - #860
Merged
ashb merged 2 commits intoJul 16, 2025
Merged
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
Copy link
Copy Markdown
CodSpeed Performance ReportMerging #860 will not alter performanceComparing rchindris:master (c44ffb0) with master (b84b976) Summary✅ 1 untouched benchmarks |
Sorry, something went wrong.
Copy link
Copy Markdown
Collaborator
|
Please rebase your changes with master to fix the failing pipeline |
Sorry, something went wrong.
ashb
approved these changes
Jul 16, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The function _parse_iso8601_interval raises IndexError when either the first or the last part of the interval is not specified. This fix checks if the interval parts are empty strings and raises ParserError if so.
Pull Request Check List