euri10
euri10
yep, pytest-asyncio might add another layer of complexity but this fails without regardless so the issue lies elsewhere, now adding some goold old-style prints to this: ``` from collections.abc import...
> sync test function with an async @pytest.fixture(autouse=True) pytest-trio raises an error pytest-anyio ignores the fixture https://github.com/agronholm/anyio/issues/789 great summary @jakkdl , long story short I introduced pytest-random-order to a pretty...
any idea how to cover this ? I dont understand why it pops now though
alright maybe we nee don top of this a version of LifespanHandler that "skips" the portal in case of the AsyncClient ?
im kinda bocked on 2 failing tests during the lifespan shutdown though the new tests work fine, but I dont see a clear reason, any idea ?
closing, this was fixed by https://github.com/litestar-org/litestar/pull/4291
2 ways to solve this: 1. either with the current examples we put a note (this wont work with swagger login which expects url-encoded form with username / password) 2....
I think I addressed all the deprecation warning but the github review system makes it not that easy to know for sure. I still have a mypy issue I dont...
not tested but that's on top of my head how I'd do it ``` @asynccontextmanager async def lifespan(app: Litestar): cp = next((p for p in app.plugins.init if isinstance(p, ChannelsPlugin)), None)...
Transferring this to this repo where it seems more correct ot make mention of that pattern