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.

Sign up for GitHub

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

Jump to bottom

Regression: Don't print progress in a non-TTY context #11195

Closed
mgol opened this issue Jun 11, 2018 · 1 comment · Fixed by #11805
Closed

Regression: Don't print progress in a non-TTY context #11195

mgol opened this issue Jun 11, 2018 · 1 comment · Fixed by #11805
Labels
area: devkit/build-angular freq1: low Only reported by a handful of users who observe it rarely P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful severity5: regression type: bug/fix

Comments

@mgol
Copy link
Member

mgol commented Jun 11, 2018

Bug Report or Feature Request (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request

Area

- [x] devkit
- [ ] schematics

Versions

$ node --version
v8.11.2
$ yarn --version
1.7.0

macOS High Sierra 10.13.5 (17F77)

Repro steps

See #8148.

The log given by the failure

See #8148.

Desired functionality

See #8148.

Mention any other details that might be useful

This is a regression as it worked fine in CLI 1.7.4 and no longer does in 6.0.8.
@mgol mgol mentioned this issue Jun 11, 2018
Closed
@filipesilva filipesilva added freq1: low Only reported by a handful of users who observe it rarely severity5: regression area: devkit/build-angular type: bug/fix labels Jun 11, 2018
@hansl hansl added the P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful label Jul 30, 2018
filipesilva added a commit to filipesilva/angular-cli that referenced this issue Aug 7, 2018
@filipesilva
fix(@angular-devkit/build-angular): use process TTY as progress default
30670d0 
Fix angular#11195
@filipesilva filipesilva mentioned this issue Aug 7, 2018
Merged
filipesilva added a commit that referenced this issue Aug 7, 2018
@filipesilva
fix(@angular-devkit/build-angular): use process TTY as progress default
8fd1040 
Fix #11195
alexeagle pushed a commit that referenced this issue Aug 9, 2018
@filipesilva @alexeagle
fix(@angular-devkit/build-angular): use process TTY as progress default
6b0e14f 
Fix #11195
filipesilva added a commit that referenced this issue Aug 16, 2018
@filipesilva
fix(@angular-devkit/build-angular): use process TTY as progress default
d1387b6 
Fix #11195
This was referenced Sep 22, 2018
Closed
Closed
Closed
Closed
Closed
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area: devkit/build-angular freq1: low Only reported by a handful of users who observe it rarely P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful severity5: regression type: bug/fix
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(@angular-devkit/build-angular): use process TTY as progress default filipesilva/angular-cli
3 participants
@hansl @mgol @filipesilva