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

Terminal is being exploded with repeated log outputs #1200

Open
J4v4Scr1pt opened this issue Sep 19, 2022 · 11 comments
Open

Terminal is being exploded with repeated log outputs #1200

J4v4Scr1pt opened this issue Sep 19, 2022 · 11 comments

Comments

@J4v4Scr1pt
Copy link

J4v4Scr1pt commented Sep 19, 2022

@akamfoad Describes and show this issue really good below. But there is more to it. When it gets repeated like shown below TaskManager show there is a lot of node.js instances spun up slowing down the computer. It affects the computer so much that it actully makes js-tests (jest) to timeout.

This issue really needs to be addressed otherwise I think this will affect usage. My colleagues are already using the --no-verify flag when commiting.

Please let me know if there is anything I can provide to ease the finding of a solution!

OS: Windows
Shell: git bash
Git version: 2.37.3
packagemanager: npm

Hi, I have a similar issue but in my case the terminal is being exploded with repeated log output.

OS: Windows
Shell: PowerShell 7.2.6
Git Version: 2.37.1.windows.1

running

yarn lint-staged

Through git hooks (added with husky):

PowerShell.2022-09-06.16-37-59.mp4

Directly running the command:

PowerShell.2022-09-06.16-39-07.mp4

Originally posted by @akamfoad in #968 (comment)

@raulmarindev
Copy link

I have the exact same issue, does anyone have an idea of what the cause could be?

@J4v4Scr1pt
Copy link
Author

I have the exact same issue, does anyone have an idea of what the cause could be?

Unfortunately not it seems😑...

@gillesdalle
Copy link

+1
I've the same problem.

@tompretty
Copy link

I'm having the exact same issue too

@IlyaZaprutski
Copy link

+1

@gillesdalle
Copy link

Duplicate bug : lint-staged/lint-staged#1164
Found a soluition in #968 (comment)
Add
exec >/dev/tty 2>&1
before your command lines in pre-commit file.

@J4v4Scr1pt
Copy link
Author

J4v4Scr1pt commented Oct 11, 2022

Duplicate bug : okonet/lint-staged#1164 Found a soluition in #968 (comment) Add exec >/dev/tty 2>&1 before your command lines in pre-commit file.

Interesting, will test! Thx m8!

Edit:
This does solve the issue. Thanks man for finding this! 🐱‍💻

EditTwo:
Well it solved it for me but my colleagues got error instead and we had to remove it... back to square one.

dudwns0921 referenced this issue in function-implementation-only/Frontend Dec 2, 2022
@typicode
Copy link
Owner

typicode commented Dec 5, 2022

@J4v4Scr1pt
Copy link
Author

Have you tried https://typicode.github.io/husky/#/?id=yarn-on-windows ?

I have not, but I am using npm. Thx for the advice tough. Hopefully it can help anyone using yarn. 🤞

@vatsalpatel68
Copy link

Add exec >/dev/tty 2>&1 this command. And update the git version using this command ( git update-git-for-windows ).

@so1ve
Copy link

so1ve commented Mar 24, 2023

I think the git built-in shell is not being recognized a tty...

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

8 participants