R3ap3r/Aurora-Core
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Pin pytest-asyncio below 1.0
CI / lint (push) Canceled after 0s
Details
CI / typecheck (push) Canceled after 0s
Details
CI / unit-tests (push) Canceled after 0s
Details
CI / integration-tests (push) Canceled after 0s
Details
CI / container-build (push) Canceled after 0s
Details
CI / dependency-audit (push) Canceled after 0s
Details

Browse Source 
1.x changed session-scoped async fixture/event-loop behavior across test
modules, breaking the single-shared-engine assumption tests/conftest.py's
engine fixture and the asyncio_default_*_loop_scope settings depend on.
Surfaced as sporadic "relation ... does not exist" failures in specific
integration test files when run alongside the full suite, despite those
same files passing cleanly when run standalone -- confirmed via a real
Postgres run on production hardware while verifying the watch-provider
dedup fix.

Co-Authored-By: Claude Sonnet 5 <[email protected]>
This commit is contained in:
NixReaper
2026-09-12 04:46:08 -05:00
co-authored by Claude Sonnet 5
parent 0ab31a314c
commit 0be052bc1f
1 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
pyproject.toml
+7 -1
View File
@@ -33,7 +33,13 @@ dependencies = [
[project.optional-dependencies] [project.optional-dependencies]
dev = [ dev = [
"pytest>=8.3.0", "pytest>=8.3.0",
"pytest-asyncio>=0.24.0", # <1.0: 1.x changed session-scoped async fixture/event-loop behavior
# across test modules, breaking the single-shared-engine assumption
# tests/conftest.py:engine and the asyncio_default_*_loop_scope
# settings below depend on (surfaced as sporadic "relation ... does
# not exist" failures in specific test files when run alongside others,
# despite passing standalone).
"pytest-asyncio>=0.24.0,<1.0.0",
"pytest-cov>=5.0.0", "pytest-cov>=5.0.0",
"ruff>=0.6.9", "ruff>=0.6.9",
"mypy>=1.11.2", "mypy>=1.11.2",