[ADAPTERS] Use logger.warning() instead of logger.warn()#13
Merged
Conversation
saikishor
approved these changes
Jun 17, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Replace deprecated
logger.warn()calls withlogger.warning().On newer ROS 2 distributions (Lyrical/Rolling),
rclpyno longer provides theLogger.warnalias, which results in anAttributeErrorwhen those code paths are executed. This can cause the node to crash in warning scenarios such as rejected goals or lifecycle publisher disconnects.This change replaces all usages of
.warn()with.warning(), which is supported on both Jazzy and Lyrical.Is this user-facing behavior change?
No
Did you use Generative AI?
No
Additional Information
Tested on: