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
Is it part of the specification that the client does not stop the discovery process until the discovery timeout is passed, even when an agent was already discovered?
For example, when the 'attempts' parameter is 1000(times) and the 'period' parameter is 1000(ms),
the client will try to discover an agent for 1000 seconds. Even when an agent is discovered, uxr_discovery_agents() does not return until 1000 seconds have passed.
In version 1.0.2, when an agent is discovered and a callback function returns true, variable 'consumed' changes to true. And the client stops the discovery process.
Is it part of the specification that the client does not stop the discovery process until the discovery timeout is passed, even when an agent was already discovered?
For example, when the 'attempts' parameter is 1000(times) and the 'period' parameter is 1000(ms),
the client will try to discover an agent for 1000 seconds. Even when an agent is discovered, uxr_discovery_agents() does not return until 1000 seconds have passed.
In version 1.0.2, when an agent is discovered and a callback function returns true, variable 'consumed' changes to true. And the client stops the discovery process.
Micro-XRCE-DDS-Client/src/c/profile/discovery/discovery.c
Lines 69 to 73 in 1a113ee
But since version 1.1.0, the client does not stop the discovery process until the discovery timeout is passed. Variable 'consumed' was deleted!
Micro-XRCE-DDS-Client/src/c/profile/discovery/discovery.c
Lines 78 to 82 in abcef44
Is this going to be fixed?
The text was updated successfully, but these errors were encountered: