Bug: test_default_no_warns failed in CI

[sobolevn]

Description

Link: https://github.com/litestar-org/litestar/actions/runs/11371187529/job/31632686132

================================== FAILURES ===================================
____________________________ test_default_no_warns ____________________________
[gw1] win32 -- Python 3.12.7 D:\a\litestar\litestar\.venv\Scripts\python.exe

    def test_default_no_warns() -> None:
        with catch_warnings(record=True) as warnings:
            simplefilter("always")
            import litestar.handlers.http_handlers.decorators
    
            reload(litestar.handlers.http_handlers.decorators)
>           assert len(warnings) == 0
E           assert 2 == 0
E            +  where 2 = len([<warnings.WarningMessage object at 0x000002E038316450>, <warnings.WarningMessage object at 0x000002E038316480>])

tests\unit\test_handlers\test_http_handlers\test_deprecation.py:25: AssertionError
============================== warnings summary ===============================
tests/unit/test_concurrency.py::test_sync_to_thread_trio
  D:\a\litestar\litestar\.venv\Lib\site-packages\trio\_core\_wakeup_socketpair.py:59: RuntimeWarning: It looks like Trio's signal handling code might have collided with another library you're using. If you're running Trio in guest mode, then this might mean you should set host_uses_signal_set_wakeup_fd=True. Otherwise, file a bug on Trio and we'll help you figure out what's going on.
    warnings.warn(

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=========================== short test summary info ===========================
FAILED tests/unit/test_handlers/test_http_handlers/test_deprecation.py::test_default_no_warns - assert 2 == 0
 +  where 2 = len([<warnings.WarningMessage object at 0x000002E038316450>, <warnings.WarningMessage object at 0x000002E038316480>])
= 1 failed, 5277 passed, 168 skipped, 7 xfailed, 5 xpassed, 1 warning in 77.81s (0:01:17) =

URL to code causing the issue

No response

MCVE

No response

Steps to reproduce

No response

Screenshots

No response

Logs

No response

Litestar Version

main

Platform

• Linux
• Mac
• Windows
• Other (Please specify in the description above)

---

Note

While we are open for sponsoring on GitHub Sponsors and
OpenCollective, we also utilize Polar.sh to engage in pledge-based sponsorship.

Check out all issues funded or available for funding on our Polar.sh dashboard

• If you would like to see an issue prioritized, make a pledge towards it!
• We receive the pledge once the issue is completed & verified
• This, along with engagement in the community, helps us know which features are a priority to our users.