build(deps-dev): bump pytest-asyncio from 0.21.2 to 0.23.7 in /server

Bumps pytest-asyncio from 0.21.2 to 0.23.7.

Release notes

Sourced from pytest-asyncio's releases.

pytest-asyncio 0.23.7

0.23.7 (2024-05-19)

Silence deprecation warnings about unclosed event loops that occurred with certain CPython patch releases #817

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). 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.

pytest-asyncio 0.23.6

0.23.6 (2024-03-19)

Fix compatibility with pytest 8.2 #800

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). 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.

pytest-asyncio 0.23.5.post1

0.23.5 (2024-02-09)

Declare compatibility with pytest 8 #737

Fix typing errors with recent versions of mypy #769

Prevent DeprecationWarning about internal use of asyncio.get_event_loop() from affecting test cases #757

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). 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.

pytest-asyncio 0.23.5

0.23.5 (2024-02-09)

Declare compatibility with pytest 8 #737

Fix typing errors with recent versions of mypy #769

Prevent DeprecationWarning about internal use of asyncio.get_event_loop() from affecting test cases #757

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). 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.

pytest-asyncio 0.23.5a0

0.23.5 (UNRELEASED)

Declare compatibility with pytest 8 #737

Fix typing errors with recent versions of mypy #769

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). 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.

pytest-asyncio 0.23.4

0.23.4 (2024-01-28)

pytest-asyncio no longer imports additional, unrelated packages during test collection #729

Addresses further issues that caused an internal pytest error during test collection

Declares incompatibility with pytest 8 #737

... (truncated)

Commits

eb63d5a docs: Prepared for release of v0.23.7.
da04a7a Build(deps): Bump exceptiongroup in /dependencies/default
00c667a Build(deps): Bump pytest from 8.1.1 to 8.2.0 in /dependencies/default
3bd9cd8 [docs] Add changelog entry.
15544f0 Revert GitHub Actions and Tox changes.
6316b28 Deduplicate simplefilter snippet.
3ffdfc5 asyncio.run(port_afinalizer())
0107fd7 Remove extra space.
3bf700a Fix GH Action mapping.
d15dc31 Fix 3109/3108 typo.
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Skipped Deployments

@dependabot ignore this minor version

pytest-asyncio has changed how they manage the event loop since 0.23.x, which makes it difficult to upgrade.

OK, I won't notify you about version 0.23.x again, unless you re-open this PR.

📦 Next.js Bundle Analysis for web

This analysis was generated by the Next.js Bundle Analysis action. 🤖

🎉 Global Bundle Size Decreased

Page	Size (compressed)
`global`	`226.42 KB` (-1 B)

Details

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!

Thirty-three Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load	% of Budget (`350 KB`)
`/maintainer/page`	`449.48 KB`	675.9 KB	193.11% (+/- <0.01%)
`/backoffice/layout`	`456.67 KB`	683.09 KB	195.17% (🟢 -0.01%)
`/docs/api/[...endpoint]/page`	`420.81 KB`	647.23 KB	184.92% (+/- <0.01%)
`/maintainer/[organization]/(topbar)/layout`	`456.67 KB`	683.09 KB	195.17% (🟢 -0.01%)
`/maintainer/[organization]/(topbar)/donations/overview/page`	`573.87 KB`	800.29 KB	228.66% (🟢 -0.01%)
`/maintainer/[organization]/(topbar)/funding/page`	`477.78 KB`	704.2 KB	201.20% (+/- <0.01%)
`/maintainer/[organization]/(topbar)/issues/badge/page`	`468.86 KB`	695.28 KB	198.65% (+/- <0.01%)
`/maintainer/[organization]/(topbar)/issues/overview/page`	`485.03 KB`	711.46 KB	203.27% (+/- <0.01%)
`/maintainer/[organization]/(topbar)/members/page`	`446.81 KB`	673.23 KB	192.35% (+/- <0.01%)
`/maintainer/[organization]/(topbar)/overview/page`	`473.39 KB`	699.81 KB	199.95% (🟢 -0.01%)
`/maintainer/[organization]/(topbar)/posts/analytics/page`	`566.97 KB`	793.4 KB	226.68% (+/- <0.01%)
`/maintainer/[organization]/(topbar)/posts/page`	`557.53 KB`	783.95 KB	223.99% (🟢 -0.01%)
`/maintainer/[organization]/(topbar)/products/benefits/page`	`538.75 KB`	765.17 KB	218.62% (🟢 -0.01%)
`/maintainer/[organization]/(topbar)/products/overview/page`	`476.24 KB`	702.66 KB	200.76% (+/- <0.01%)
`/maintainer/[organization]/(topbar)/sales/orders/page`	`479.21 KB`	705.63 KB	201.61% (🟢 -0.01%)
`/maintainer/[organization]/(topbar)/sales/overview/page`	`570.46 KB`	796.88 KB	227.68% (+/- <0.01%)
`/maintainer/[organization]/(topbar)/sales/subscriptions/page`	`492.08 KB`	718.5 KB	205.29% (🟢 -0.01%)
`/maintainer/[organization]/(topbar)/settings/page`	`462.34 KB`	688.76 KB	196.79% (🟢 -0.01%)
`/maintainer/[organization]/(topbar)/settings/webhooks/endpoints/[id]/page`	`488.73 KB`	715.15 KB	204.33% (🟢 -0.01%)
`/maintainer/[organization]/(white)/posts/[post]/page`	`554.49 KB`	780.91 KB	223.12% (🟢 -0.01%)
`/maintainer/[organization]/(white)/layout`	`441.33 KB`	667.75 KB	190.79% (🟢 -0.01%)
`/maintainer/[organization]/(white)/posts/new/page`	`552.12 KB`	778.54 KB	222.44% (+/- <0.01%)
`/maintainer/[organization]/products/[id]/page`	`528.15 KB`	754.57 KB	215.59% (+/- <0.01%)
`/maintainer/[organization]/products/layout`	`441.33 KB`	667.75 KB	190.78% (+/- <0.01%)
`/maintainer/[organization]/products/new/page`	`527.84 KB`	754.26 KB	215.50% (+/- <0.01%)
`/maintainer/[organization]/promote/page`	`463.31 KB`	689.73 KB	197.07% (🟢 -0.01%)
`/maintainer/[organization]/promote/layout`	`441.33 KB`	667.75 KB	190.79% (🟢 -0.01%)
`/docs/(mdx)/layout`	`393.06 KB`	619.48 KB	177.00% (🟢 -0.01%)
`/docs/api/(mdx)/layout`	`393.05 KB`	619.47 KB	176.99% (+/- <0.01%)
`/docs/contribute/layout`	`393.06 KB`	619.48 KB	177.00% (🟢 -0.01%)
`/docs/support/layout`	`393.06 KB`	619.48 KB	177.00% (🟢 -0.01%)
`/maintainer/[organization]/(topbar)/finance/layout`	`441.32 KB`	667.74 KB	190.78% (+/- <0.01%)
`/maintainer/[organization]/(topbar)/finance/issue-funding/layout`	`441.32 KB`	667.74 KB	190.78% (+/- <0.01%)

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.

polarsource / polar