-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Comments
Any chance you've tested this with one display command or the other and gotten different results? Just trying to narrow down the culprits. |
I hadn't, but it reproduces for me with just the first line in the bunch:
Sample of Bunch - One Line.txt In case it might matter, |
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. |
Is there anything interesting about these log files? Are they set to
world read permissions (644)? Have you tested the same command with a
different text file at all? I just replicated your command with a simple
text file being written to at 5 second intervals and had no issues.
…-Brett
On 16 Aug 2022, at 17:12, Jamie Phelps wrote:
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](https://github.com/ttscoff/bunch/files/9354968/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.
--
Reply to this email directly or view it on GitHub:
#247 (comment)
You are receiving this because you commented.
Message ID: ***@***.***>
|
Permissions looked OK… I rotated log files and the new ones load fine, even with both
|
I never expected to deal with a 30MB text file, let alone 100+, but nothing about the setup should really break under those circumstances. Will look into it.
…-Brett
________________________________
From: Jamie Phelps ***@***.***>
Sent: Wednesday, August 17, 2022 2:44:29 PM
To: ttscoff/bunch ***@***.***>
Cc: Brett Terpstra ***@***.***>; Comment ***@***.***>
Subject: Re: [ttscoff/bunch] Bunch hanging on `(display)` command (Issue #247)
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
—
Reply to this email directly, view it on GitHub<#247 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAALVWODA5P62OT5TVUI4FDVZU6J3ANCNFSM56TBKRHA>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Bunch content
Debug logs
The text was updated successfully, but these errors were encountered: