Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot specify log level via the CLI #288

Open
piraka9011 opened this issue Feb 7, 2020 · 1 comment
Open

Cannot specify log level via the CLI #288

piraka9011 opened this issue Feb 7, 2020 · 1 comment
Labels
bug Something isn't working

Comments

@piraka9011
Copy link
Contributor

There is currently no mechanism to specify the log level ros2bag via the CLI.

I have attempted to configure the level using __log_level:=debug and --log-level flags, however they both are assumed to be topics by Python's argparser.

This may require specifying the log level in ros2bag and propogating it accordingly to rosbag2_transport where we could then use rcutils_logging_set_logger_level() with the transport_node.

@piraka9011 piraka9011 added the enhancement New feature or request label Feb 7, 2020
@emersonknapp emersonknapp added bug Something isn't working and removed enhancement New feature or request labels Feb 10, 2020
@emersonknapp
Copy link
Collaborator

Now that the Recorder and Player are Nodes, we should be pretty close to being able to configure the log level via parameters to those nodes. Though, the workflow is not quite connected yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants