-
Notifications
You must be signed in to change notification settings - Fork 59
Fix regression: #258
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Fix regression: #258
Conversation
asvetlov
commented
Nov 10, 2021
- Don't raise TimeoutError from timeout object that doesn't enter into async context manager
- Use call_soon() for raising TimeoutError if deadline is reached on entering into async context manager
1. Don't raise TimeoutError from timeout object that doesn't enter into async context manager 2. Use call_soon() for raising TimeoutError if deadline is reached on entering into async context manager
Codecov Report
@@ Coverage Diff @@
## master #258 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 1 1
Lines 109 116 +7
Branches 16 18 +2
=========================================
+ Hits 109 116 +7
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
@achimnol does the PR fix your problem? |
YES!!! My test cases came back normal as with both async-timeout v3 series and this PR. 🙏🏼 |
Cool! |
* aio-libs/async-timeout#258 fixes early-expring timeouts used within async generators, which was a regression in async-timeout 4.0.0.
* fix: Update async-timeout API usage * test: Update async-timeout API usage * test: Fix docker-compose container naming to be compatible with docker-compose 2.0 and 2.1 * fix: Catch TimeoutError in addition to asyncio.TimeoutError - aioredis v2 often wraps asyncio.TimeoutError with TimeoutError * test: Distinguish PING/PONG msgs for readiness checks * setup: Upgrade async-timeout to a compatible version (4.0.1) - aio-libs/async-timeout#258 fixes early-expring timeouts used within async generators, which was a regression in async-timeout 4.0.0.