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

Support de-quieting the context logger in ConsoleTasks #7585

Closed
CMLivingston opened this issue Apr 17, 2019 · 3 comments
Closed

Support de-quieting the context logger in ConsoleTasks #7585

CMLivingston opened this issue Apr 17, 2019 · 3 comments

Comments

@CMLivingston
Copy link
Contributor

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

@CMLivingston CMLivingston changed the title Support context logger in ConsoleTasks Support de-quieting the context logger in ConsoleTasks Apr 17, 2019
@cosmicexplorer
Copy link
Contributor

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).

@stuhood
Copy link
Sponsor Member

stuhood commented Apr 17, 2019

Relates to #6880 as well.

@Eric-Arellano
Copy link
Contributor

ConsoleTasks were removed in Pants 2.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants