-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Crash when piping output from node/nodemon web server #3892
Comments
Does
Are there any error messages? |
No.
No. So, at a loss what to do to debug. I could run the GitHub version again if there's a way to enable logging somewhere. |
Can you provide minimal steps to reproduce the problem from my side? I don't have your project with index.ts so there's no way I can further look into the problem. Also, please don't assume that I know anything about the thing called "ts-node". |
Ah, sorry, I was hoping to look for a way to get debug logs so I can gather more information first. Thanks for helping to look into this. I was wrong, it wasn't
I made a repo to reproduce the issue for me — https://github.com/hboon/nodemon-fzf/. It's really just running A. Run this:
I'm hoping to use |
Thanks for the repro. I can reproduce the problem, and it definitely looks like Workaround 1. Prevent nodemon from reading user inputBy redirecting node_modules/nodemon/bin/nodemon.js index.js < /dev/null | fzf --ansi --tail 10000 --tac The problem is Workaround 2. Make fzf start the processfzf --ansi --tail 10000 --tac --bind 'start:reload:node_modules/nodemon/bin/nodemon.js index.js' fzf starts nodemon process when it starts, and can terminate it when it exits. (Works better with 5b52833) |
Both workarounds work for me. I'll use (2). Doesn't seem like 5b52833 is needed yet. But all good. Thanks again! |
Checklist
man fzf
)Output of
fzf --version
0.53.0 (brew)
OS
Shell
Problem / Steps to reproduce
I can reproduce with the latest on github too. fish and bash.
If I do:
I noticed that filtering by typing seems to be extremely slow, given the number of lines (and compared to running
fzf
with other cases on the same machine in the same shell).I'm not sure what's going on, but is there a way to enable some logs so I can gather more information?
The text was updated successfully, but these errors were encountered: