Update poetry lockfile #403
Merged
Conversation
This file contains 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
|
I'm going to merge this PR to unblock #402 (should be a pretty uncontroversial change). I'm happy to handle any follow-up comments folks have. FWIW I'd be happy to just remove all the exception handling here and let response.raise_for_status()raise directly, but wanted to keep this PR as minimal as possible. |
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.
Over in #402 I'm seeing some test failures from updating the poetry lock file that I'm confused about. I'm wondering if those failures are due to the changes in that PR or not (they don't seem related).
This PR runs
poetry lockon the currentmainbranch to see if CI is happy with that. That should tell us whether the failures in #402 are related to the changes there or not.