Fix XCom.get_one exactly one exception text #30183
Merged
Conversation
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
vemikhaylov
force-pushed
the
fix-xcom-get-one-exactly-one-exc
branch
from
fa8a9e2 to
b504586
Compare
vemikhaylov
force-pushed
the
fix-xcom-get-one-exactly-one-exc
branch
from
b504586 to
1ce894c
Compare
uranusjr
approved these changes
Mar 21, 2023
potiuk
approved these changes
Mar 21, 2023
pierrejeambrun
pushed a commit
that referenced
this pull request
Mar 23, 2023
(cherry picked from commit 18b91ca)
pierrejeambrun
pushed a commit
that referenced
this pull request
Mar 24, 2023
(cherry picked from commit 18b91ca)
28 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
In
BaseXCom.get_onewe got rid of theti_keyparameter passing and, hence, checking in d08284e, but didn't tune the exception message, what I'm doing here.