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

Bunch hanging on (display) command #247

Open
jxpx777 opened this issue Aug 15, 2022 · 7 comments
Open

Bunch hanging on (display) command #247

jxpx777 opened this issue Aug 15, 2022 · 7 comments
Labels
bug Something isn't working

Comments

@jxpx777
Copy link

jxpx777 commented Aug 15, 2022

Bunch content

(display ~/code/railsapp/log/development.log left,top 350x50%)
(display ~/code/railsapp/log/test.log left,bottom 350x50%)
Debug logs
2022-08-15 11:10:37: ⚪[Repro] Open >>>>>>>>>>>>>>>>>>>>>
2022-08-15 11:10:37: ⚪[Repro] Processing command "display /Users/jp/code/railsapp/log/develo…"
2022-08-15 11:10:37: 🔘Generating status menu
2022-08-15 11:10:37: ⚪[Repro] Processing command "display /Users/jp/code/railsapp/log/test.l…"
@jxpx777
Copy link
Author

jxpx777 commented Aug 15, 2022

process-sample.txt

@ttscoff
Copy link
Owner

ttscoff commented Aug 15, 2022

Any chance you've tested this with one display command or the other and gotten different results? Just trying to narrow down the culprits.

@jxpx777
Copy link
Author

jxpx777 commented Aug 16, 2022

I hadn't, but it reproduces for me with just the first line in the bunch:

(display ~/code/railsapp/log/development.log left,top 350x50%)

Sample of Bunch - One Line.txt

In case it might matter, ~/code/railsapp… is a redacted path; the real path is ~/code/clientname/clientproject/log/development.log. The bits I redacted are all lowercase ascii letters, but I thought it worth mentioning just in case something weird might be going on even with that simple of a change.

@jxpx777
Copy link
Author

jxpx777 commented Aug 16, 2022

Just tried with the second line alone in its own bunch and it also reproduces, so hopefully that helps. I will also add that when I copied the redacted path and forgot to change it (lulz), there was no hang, presumably because the failure to locate the file short circuited the whole operation.

@ttscoff
Copy link
Owner

ttscoff commented Aug 17, 2022 via email

@jxpx777
Copy link
Author

jxpx777 commented Aug 17, 2022

Permissions looked OK… I rotated log files and the new ones load fine, even with both (display) commands in one bunch, so maybe just an overall size problem? I honestly didn't realize these log files were this big… might be something worth addressing!

$ ls -lh
total 512008
-rw-r--r--  1 jp  staff     0B Jul  5 14:35 bullet.log
-rw-r--r--@ 1 jp  staff    38M Aug 17 12:02 development.1.log
-rw-r--r--  1 jp  staff   7.3K Aug 17 12:40 development.log
-rw-r--r--  1 jp  staff   196M Aug 17 08:44 test.1.log
-rw-r--r--  1 jp  staff    91K Aug 17 12:40 test.log
-rw-r--r--  1 jp  staff     0B Aug 17 12:40 vcr.log

@ttscoff
Copy link
Owner

ttscoff commented Aug 17, 2022 via email

@ttscoff ttscoff added the bug Something isn't working label Sep 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants