66/113 tests failing — jose and asyncio infrastructure issues #26
Labels
No labels
blocked:gate-fetch
blocked:gate-fetch
blocked:gate-implement
blocked:gate-plan
blocked:needs-attention
blocked:needs-decision
blocked:needs-human
blocked:no-procedure
blocked:preflight
bug
feature-request
in-progress
lint-cleanup
needs-decompose
needs-triage
ops-task
quickfix
security/medium
triage-approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Mark/msp_c2#26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Bug
Running
pytestresults in 66 failed, 35 passed, 12 errors. The test suite is majority-broken.Root causes identified
jose module resolution — Many tests fail with
jose.exceptions.JWSErroror similar JWT-related errors. Thepython-jose[cryptography]==3.3.0dependency doesn't always resolve correctly depending on the Python environment. Tests fail with JWT encoding/decoding errors.Async test infrastructure — Some async tests fail with
anyiostream errors (MemoryObjectReceiveStreamclosure), suggesting the async test fixtures aren't properly managing database sessions. SQLAlchemy connections are being closed before the test completes.Pydantic namespace warning —
Field "model_number" has conflict with protected namespace "model_"— this affects the Pydantic model configuration.Test breakdown
Severity
RED Critical — Majority of test suite is broken. Core JWT authentication flow cannot be verified.
Fixed in commit. Closing.