jstasiak / python-zeroconf

92%

master: 94%

LAST BUILD ON BRANCH pr-239-cleanup

branch: pr-239-cleanup

CHANGE BRANCH

x

Reset

• pr-239-cleanup
• 0.15.1
• 0.16
• 0.17.1
• 0.17.2
• 0.17.3
• 0.17.4
• 0.17.5
• 0.17.6
• 0.18.0
• 0.19.0
• 0.19.1
• 0.20.0
• 0.21.0
• 0.21.1
• 0.21.2
• 0.21.3
• 0.22.0
• 0.23.0
• 0.24.0
• 0.24.5
• 0.25.0
• 0.25.1
• 0.26.0
• 0.26.1
• 0.26.2
• 0.26.3
• 0.27.0
• 0.27.1
• 0.28.0
• 0.28.1
• 0.28.2
• 0.28.3
• 0.28.4
• 0.28.5
• 0.28.6
• 0.28.7
• 0.28.8
• allow-underscore-in-service-names
• asd
• coverage
• dev
• dev2
• develop
• documentation
• explicit-mock-import
• fix-importerror-description
• fix-linting
• fix-unique-regression
• gh9
• improve-documentation
• improve-logging
• int-equality
• js
• macos-ci
• make-mypy-happy
• master
• merge-strict-and-allow_underscores
• more-logging
• more-type-hints
• multiple-interfaces
• no-more-if_nameindex
• old-kernels
• python3.8
• rebase-175
• rebase-188
• remove-deprecated-stuff
• remove-python2-stuff
• remove-typing-dependency
• restore-missing-import
• service-info-construct-with-parsed-addresses
• simplify-dnshinfo
• switch-to-pytest
• test
• test-with-python39
• test2
• warn-on-no-update-service

Build # 644

Build Type

push

travis-ci

Committed by jstasiak

Commit Message

Call UpdateService on SRV & A/AAAA updates as well as TXT (#239)

Fix https://github.com/jstasiak/python-zeroconf/issues/235

Contains:

* Add lock around handlers list
* Reverse DNSCache order to ensure newest records take precedence

  When there are multiple records in the cache, the behaviour was
  inconsistent. Whilst the DNSCache.get() method returned the newest,
  any function which iterated over the entire cache suffered from
  a last write winds issue. This change makes this behaviour consistent
  and allows the removal of an (incorrect) wait from one of the unit tests.

Run Details

516 of 623 branches covered (82.83%)

86 of 86 new or added lines in 2 files covered. (100.0%)

2118 of 2290 relevant lines covered (92.49%)

5.55 hits per line