Fix error variable not being reset when failure in a coroutine call in flags2_asyncio.py#35
Merged
ramalho merged 1 commit intofluentpython:masterfrom May 19, 2025
Merged
Conversation
Fix `error` variable not being reset when a successful coroutine call
charlielito
changed the title
error variable not being reset when a successful coroutine call in flags2_asyncio.pyerror variable not being reset when with a failure in a coroutine call in flags2_asyncio.py
charlielito
changed the title
error variable not being reset when with a failure in a coroutine call in flags2_asyncio.pyerror variable not being reset when failure in a coroutine call in flags2_asyncio.py
Member
|
Thanks for this contribution, @charlielito ! |
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
2 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 the
asyncioexample inflags2_asyncio.pythere is a bug when a call to a coroutine in the loop fails and the next one has success, theerrorvariable doesn't get reset and it still thinks it got an error, and updates thecounter[status]with the wrong value