Temporarily suppress napari warnings

[lochhh]

100s of warnings (UserWarning #573 and FutureWarning #593) were introduced in PR #476 and these obfuscate pytest's warnings summary, making it difficult to see if new changes are potentially introducing issues.

This PR filters out the aforementioned warnings.

Checklist:

• The code has been tested locally
• Tests have been added to cover all new functionality
• The documentation has been updated to reflect any changes
• The code has been formatted with pre-commit

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (4c31b3f) to head (a17feae).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #592   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           31        31           
  Lines         1615      1615           
=========================================
  Hits          1615      1615           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[sfmig]

Heya, thanks for raising this.

Apologies, I missed fixing one of the two FutureWarnings in PR #476 - I have tackled that now in PR #594, which should make that filter warning unnecessary. With that fix we bring the warnings down to 36.

I agree that warnings clutter the CI logs and make it difficult to parse the information (we are also currently getting about ~100 lines of warnings re license syntax just at the beginning of running tox, see PR #549). But I am confused, these particular warnings you mention seem to be well contained in a reasonably sized summary section right (~16 lines)? Or are you referring to something else?

Re the Previous color_by key warning, I actually would like to keep an eye on it. It is coming from napari and I would like to see if an update fixes it, so I think keeping the warning visible would be helpful for that. But let me know thoughts.

[lochhh]

Thanks @sfmig this is great! I can remove the FutureWarning filter in this PR, but I don't mean to close #573 with this PR; it's just to make the warnings summary easier to read when running pytest locally. This filter will of course be removed when we've tackled #573.

[sfmig]

Ok sounds good, thanks for clarifying!
Yeah, I think just tracking the problem with issue #573 should be enough.

Will approve now 🚀

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud