Hi Juergen,

On 02/05/2022 11:07, Juergen Gross wrote:
When firing special watches (e.g. "@releaseDomain"), they will be
regarded to be valid children of the "/" node. So a domain having
registered a watch for "/" and having the privilege to receive
the special watches will receive those special watch events for the
registered "/" watch.

Fix that by calling the related fire_watches() with the "exact"
parameter set to true, causing a mismatch for the "/" node.

Reported-by: Raphael Ning <[email protected]>
Signed-off-by: Juergen Gross <[email protected]>
Reviewed-by: Raphael Ning <[email protected]>

Reviewed-by: Julien Grall <[email protected]>

And commited it.

Cheers,

--
Julien Grall

Reply via email to