- Notifications
You must be signed in to change notification settings - Fork1k
fix: async fixtures in conftest.py#2068
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Explicitly make autouse fixtures async to avoid issues with newerversions of pytest, which made this a warning by default.
What's the error? |
Uh oh!
There was an error while loading.Please reload this page.
It comes from a new validation which I believe was added inpytest 8.4 here. I tripped over it when developing the AG-UI integration, as uv bumped all the dependencies and all the tests started failing. |
Use str for the type hint, avoiding the need for a comment or Literal.
You don't need to bump all dependencies when updating the lock file. Let me update pytest here. |
I've bumped |
Yer, I just tripped over it as I was bouncing between various configs and |
stevenh commentedJun 25, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
It's a bit heavy, but this should trigger a repoduction: uv add --dev -U pytest-cov I'd assumed it was pytest, as it was where the error was coming from, there might be another underlying cause. In case it helps:
|
@Viicos Would you like to check this PR? |
967b825
intopydantic:mainUh oh!
There was an error while loading.Please reload this page.
I can't really reproduce it... But since the pipeline is passing, let's go. |
Uh oh!
There was an error while loading.Please reload this page.
Explicitly make autouse fixtures async to avoid issues with newer versions of pytest, which made this a warning by default.
Fixes#2065