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
When writing a ConsoleTask in a plugin, Pants expects all output to be contained to the return value of console_output. It would be useful if Pants could support de-quieting this feature to allow for self.context.log.info and debug - debug for usage with -ldebug, and info logging in the event that you are using another external tool in your task that has its own logging mechanism and you want to naturally wrap that logging with a helpful explanation of what is happening
The text was updated successfully, but these errors were encountered:
CMLivingston
changed the title
Support context logger in ConsoleTasks
Support de-quieting the context logger in ConsoleTasks
Apr 17, 2019
One possible generalization of this is detailed in #7071 (comment), where in that case, ConsoleTask log output would normally default to not being printed, but if e.g. --my-console-task-workunit-output=+{'stderr': {'/dev/stderr': '__all__'}} was added to the command line, that would tell pants to print it to stderr instead of swallowing it (or something else, no clue how that interface should look right now).
When writing a
ConsoleTask
in a plugin, Pants expects all output to be contained to the return value ofconsole_output
. It would be useful if Pants could support de-quieting this feature to allow forself.context.log.info
anddebug
- debug for usage with-ldebug
, and info logging in the event that you are using another external tool in your task that has its own logging mechanism and you want to naturally wrap that logging with a helpful explanation of what is happeningThe text was updated successfully, but these errors were encountered: