codecov[bot]
commented
6 months ago Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Comparison is base (
98028fa) 100.00% compared to head (de5b129) 100.00%.
Additional details and impacted files
```diff @@ Coverage Diff @@ ## master #217 +/- ## ========================================= Coverage 100.00% 100.00% ========================================= Files 8 8 Lines 401 401 Branches 76 76 ========================================= Hits 401 401 ```:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
This PR contains the following updates:
==0.23.2->==0.23.3Release Notes
pytest-dev/pytest-asyncio (pytest-asyncio)
### [`v0.23.3`](https://togithub.com/pytest-dev/pytest-asyncio/releases/tag/v0.23.3): pytest-asyncio 0.23.3 [Compare Source](https://togithub.com/pytest-dev/pytest-asyncio/compare/v0.23.2...v0.23.3) ### 0.23.3 (2024-01-01) - Fixes a bug that caused event loops to be closed prematurely when using async generator fixtures with class scope or wider in a function-scoped test [#706](https://togithub.com/pytest-dev/pytest-asyncio/issues/706) - Fixes various bugs that caused an internal pytest error during test collection [#711](https://togithub.com/pytest-dev/pytest-asyncio/issues/711) [#713](https://togithub.com/pytest-dev/pytest-asyncio/issues/713) [#719](https://togithub.com/pytest-dev/pytest-asyncio/issues/719) #### Known issues As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see [#706](https://togithub.com/pytest-dev/pytest-asyncio/issues/706)). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.