Configure pytest to ignore known DeprecationWarnings

[kurtmckee]

Older starlette and pydantic syntax is currently supported, so these warnings are known and expected.

There are still two ResourceWarnings from anyio left to address. These are thrown due to unclosed MemoryObjectReceiveStream objects.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (5f93626) to head (1bd6cde).
Report is 4 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #233   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           58        58           
  Lines         4732      4732           
  Branches       324       324           
=========================================
  Hits          4732      4732           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[zmievsa]

What would we need to resolve the resource warnings from anyio?

[kurtmckee]

When I set PYTHONTRACEMALLOC, I found that the resources were opened -- but unclosed -- within starlette itself.

I found several open issues in the starlette repo that suggested this was indeed caused by starlette (not by cadwyn's own usage) so I think we're in the clear to simply ignore those ResourceWarnings.

I'll try to find a definitive starlette issue to link to and update this PR to ignore those warnings, together with a comment pointing to the definitive issue...and then lock in the pytest configuration to error on warnings moving forward.

[zmievsa]

Understood. Thanks!