Skip to content

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

Merged
merged 3 commits into from
Nov 10, 2021
Merged

Fix regression: #258

merged 3 commits into from
Nov 10, 2021

Conversation

asvetlov
Copy link
Member

  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

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
Copy link

codecov bot commented Nov 10, 2021

Codecov Report

Merging #258 (c842da2) into master (e704f94) will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff            @@
##            master      #258   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines          109       116    +7     
  Branches        16        18    +2     
=========================================
+ Hits           109       116    +7     
Flag Coverage Δ
unit 98.27% <100.00%> (+0.11%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
async_timeout/__init__.py 100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e704f94...c842da2. Read the comment docs.

@asvetlov
Copy link
Member Author

@achimnol does the PR fix your problem?

@achimnol
Copy link
Member

@achimnol does the PR fix your problem?

YES!!! My test cases came back normal as with both async-timeout v3 series and this PR. 🙏🏼

@asvetlov
Copy link
Member Author

Cool!
Going to publish a new release.

@asvetlov asvetlov merged commit a0e0e21 into master Nov 10, 2021
@asvetlov asvetlov deleted the fix-regression branch November 10, 2021 20:23
achimnol added a commit to lablup/backend.ai-common that referenced this pull request Nov 11, 2021
* aio-libs/async-timeout#258 fixes early-expring timeouts
  used within async generators, which was a regression
  in async-timeout 4.0.0.
achimnol added a commit to lablup/backend.ai-common that referenced this pull request Nov 11, 2021
* 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.
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants