Skip to content

Add support for logging to a file #458

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

Closed
DartBot opened this issue Jun 5, 2015 · 1 comment
Closed

Add support for logging to a file #458

DartBot opened this issue Jun 5, 2015 · 1 comment
Assignees
Labels
closed-not-planned Closed as we don't intend to take action on the reported issue type-enhancement A request for a change that isn't a bug

Comments

@DartBot
Copy link

DartBot commented Jun 5, 2015

<img src="https://avatars.githubusercontent.com/u/46275?v=3" align="left" width="96" height="96"hspace="10"> Issue by munificent
Originally opened as dart-lang/sdk#8686


Pub has detailed logging now, but its options for outputting the logs are limited. For the pub tests, we often want to specifically capture both stdout and stderr and it's tricky if the logs are in either of those.

It would be ideal if pub could be directed to log to a separate file (or pipe?). Then the pub tests could capture that separately and keep stdout/stderr clean.

@DartBot
Copy link
Author

DartBot commented Jun 5, 2015

<img src="https://avatars.githubusercontent.com/u/46275?v=3" align="left" width="48" height="48"hspace="10"> Comment by munificent


The OS already supports piping, so we've decided to just rely on that. The pub tests separate out stdout and stderr.


Added NotPlanned label.

@DartBot DartBot added type-enhancement A request for a change that isn't a bug closed-not-planned Closed as we don't intend to take action on the reported issue Priority-Medium labels Jun 5, 2015
@DartBot DartBot closed this as completed Jun 5, 2015
sigurdm pushed a commit to sigurdm/pub that referenced this issue Nov 15, 2019
* update options

* whitespace

* test fix

* 0.1.29 updates

* back to 0.12.8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-not-planned Closed as we don't intend to take action on the reported issue type-enhancement A request for a change that isn't a bug
Projects
None yet
Development

No branches or pull requests

2 participants