Change liveliness tokens logs from warn to debug level #22
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@Yadunund could you please review this ? |
Yadunund
approved these changes
Sep 23, 2024
imstevenpmwork
pushed a commit
that referenced
this pull request
Sep 23, 2024
YuanYuYuan
added a commit
that referenced
this pull request
Dec 6, 2024
* chore: configure the compiliation * chore: complete the 1st version * fix: memory leak * fix: z_error_t -> z_result_t * Fix `scouting/*/autoconnect/*` per eclipse-zenoh/zenoh@b31a410 (#3) * chore: checkout the local zenoh-c * chore: polish z_open * feat: `z_bytes_serialize_from_slice` without copy * Initialize `query_` member of `ZenohQuery` * refactor: use `z_owned_slice_t` instead * chore: adapt the latest change of zenoh-c dev/1.0.0 * chore: use `strncmp` to avoid copying * refactor: use `z_view_keyexpr_t` to avoid copying * chore: adapt the new changes from zenoh-c and fix the bug in liveliness * fix: segmentation fault due to the unallocated query memory * fix: workaround the ZID parsing issue * fix Zenoh Config read\check * adopt to recent zenoh-c API changes * fix: adapt the latest change of batching config * build: deprecate the zenohc_debug and include the zenohc dependency in the zenoh_c_vendor * Use main branch for upgrading to Zenoh 1.0 * Increase the delay in scouting (#16) * ci: fix the argument order in the style CI * refactor: use `z_id_to_string` * build: enable the unstable feature flag * build: bump up the zenoh-c commit * build: update zenoh-c version * fix: set the max size of initial query queue to `SIZE_MAX - 1` * fix: iterator memory leak * feat: update to zenoh-c 1.0.0.8 changes * chore(style): address `ament_cpplint` and `ament_uncrustiy` * fix: initiate zenoh logger * chore: apply the suggestions * chore: add the comments for the zenoh logger * fix: store and destroy the subscriber properly * chore: improve the null pointer check: NULL => nullptr * Change liveliness tokens logs from warn to debug level (#22) * fix: properly clone the pointer of query and reply to resolve the segfault in test_service__rmw_zenoh_cpp * chore: update to zenoh-c 1.0.0.9 (#23) * Thread-safe access to graph cache (ros2#258) * refactor(api): align with latest serialization changes * chore(deps): bump up zenoh-c to 1.0.0.10 * chore(api): align with latest serialization changes * fix: correct the sub_ke and selector_ke in the querying_subscriber * fix: thread-safe publisher * Enable history option for liveliness subscriber. (#27) * refactor!: adopt the TLS config renaming * refactor: allow Zenoh session to close without dropping * fix: address the failure in rclcpp/test_wait_for_message of declaring a subscriber after the RMW has been shut down * test: close but not drop the session * fix: correct the merge * chore: Explicit false in adminspace config * fix: enable admin space in rmw router and ros nodes * Bump zenoh-c version. * Use the latest zenoh-c which fix some nav2 issues. (#31) * Update config files according to Zenoh 1.0.0 DEFAULT_CONFIG.json5 (#33) * chore(zenoh_c_vendor): bumb up zenoh-c version * refactor: remove the free_attachment * Fix unset request header writer GUID in `rmw_take_response` * fix: keyexpr is missing in the service * Avoid touching Zenoh Session while exiting. * Register function right after opening Zenoh Session. * chore(deps): bump up zenoh-c to 1.0.1 * fix: use TRUE value to configure the feature flag * fix: correct typo `attachement` to `attachment` * refactor: remove the warning of subscriber reliability QoS * Fix `z_view_string_t` to `std::string` conversion * refactor: zc_liveliness_* -> z_liveliness_* and bump up zenoh-c version * refactor: reorder the cancel functions * chore: reorder some lines of code * refactor: add `session_is_valid` check * fixup! refactor: reorder the cancel functions * fixup! refactor: zc_liveliness_* -> z_liveliness_* and bump up zenoh-c version Signed-off-by: Luca Cominardi <[email protected]> Signed-off-by: ChenYing Kuo <[email protected]> Signed-off-by: Gabriele Baldoni <[email protected]> Signed-off-by: Yadunund <[email protected]> Co-authored-by: Mahmoud Mazouz <[email protected]> Co-authored-by: yellowhatter <[email protected]> Co-authored-by: Steven Palma <[email protected]> Co-authored-by: Julien Enoch <[email protected]> Co-authored-by: Chris Lalancette <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As agreed here change the log levels of warnings about "out-of-order" unregistration of liveliness tokens from
warntodebug.The reason is that in case a remote Node is disconnected or if it shuts down abruptly (calling
rmw_shutdownand thus closing the Zenoh session before deleting its pubs/subs/services) Zenoh will locally deliver the events of liveliness tokens unregistrations in an arbitrary order. Thus it's likely that the unregistration of Node will be notified before the unregistration of its pubs/subs/services.