Skip to content

fix: correctly override question type flag for requests #1558

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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

agners
Copy link
Collaborator

@agners agners commented Apr 2, 2025

Currently even when setting the explicit question type flag, the implementation ignores it for subsequent queries. This commit ensures that all queries respect the explicit question type flag.

Currently even when setting the explicit question type flag, the
implementation ignores it for subsequent queries. This commit ensures
that all queries respect the explicit question type flag.
Copy link

codecov bot commented Apr 2, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.79%. Comparing base (b757ddf) to head (4d5dfa4).
Report is 2 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1558   +/-   ##
=======================================
  Coverage   99.79%   99.79%           
=======================================
  Files          33       33           
  Lines        3393     3393           
  Branches      463      463           
=======================================
  Hits         3386     3386           
  Misses          5        5           
  Partials        2        2           

☔ 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.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@agners
Copy link
Collaborator Author

agners commented Apr 2, 2025

Maybe the current behavior is intended, but I don't think so, at least it isn't mentioned when the logic to ask for a unicast on the first request got first implemented: #852.

Copy link

codspeed-hq bot commented Apr 2, 2025

CodSpeed Performance Report

Merging #1558 will not alter performance

Comparing agners:fix-explicit-question-type-flag (4d5dfa4) with master (b757ddf)

Summary

✅ 6 untouched benchmarks

Add unit test to validate that the explicit question type flag is set
correctly in outgoing requests.
@agners agners force-pushed the fix-explicit-question-type-flag branch from b419f32 to 4d5dfa4 Compare April 2, 2025 14:56
@bdraco
Copy link
Member

bdraco commented Apr 2, 2025

Thanks @agners

@bdraco bdraco merged commit bd643a2 into python-zeroconf:master Apr 2, 2025
33 of 34 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants