Remove (potentially) recursive DEBUG statements #1823
Merged
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.
This is an alternative fix to #1241. This also addresses ros/rosconsole#30
When using a log level of
debug
, every logging statement will have console output:Warning: recursive print statement has occurred. Throwing out recursive print.
The logic introduced in #1241 uses
getCached
which will cause a second logging statement to occur recursively when log level is set to debug.Edit: This has been updated to remove the offending DEBUG statements so that it will work in all cases.