You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We try to update the address for non-CASE sessions (because the checks for "is this session that failed to deliver a message a CASE session?" got lost during the CASE refactors). This at best leads to spurious error logs and at worst leads to extra dns-sd traffic that actually makes the delivery problems worse.
Proposed Solution
Add back the "is this CASE?" checks.
The text was updated successfully, but these errors were encountered:
When the handling of "failed to send message, so update the IP for this peer"
moved out of DeviceCommissioner, we stopped checking whether the session is a
CASE session. Go back to checking that again.
Fixesproject-chip#22326
* Only do address updates for CASE delivery failures.
When the handling of "failed to send message, so update the IP for this peer"
moved out of DeviceCommissioner, we stopped checking whether the session is a
CASE session. Go back to checking that again.
Fixesproject-chip#22326
* Address review comment.
Problem
We try to update the address for non-CASE sessions (because the checks for "is this session that failed to deliver a message a CASE session?" got lost during the CASE refactors). This at best leads to spurious error logs and at worst leads to extra dns-sd traffic that actually makes the delivery problems worse.
Proposed Solution
Add back the "is this CASE?" checks.
The text was updated successfully, but these errors were encountered: