Reduce helix.log max size #10377
Answered
by
kirawi
bhansconnect
asked this question in
General
Reduce helix.log max size
#10377
-
SummaryHelix looks like it never trims it log files. As such, on 1 machine I had over an 100GB log file. On my other machine here, I have a 22GB log file. Maybe I missed a config option to deal with this. That said, even if I did, there should be a better default. Reproduction StepsUse helix with various lsps. It will log issues. Logs never get cleared and add up to gigabytes of data. I expected this to happen: Instead, this happened: Helix logThis is a small snippet from my linux box. Mostly rust analyzer issues it seems. ~/.cache/helix/helix.logOn my macos box it is a similar story. Tons of messages from clangd and tablegen. PlatformLinux and Macos Terminal Emulatorkitty 0.33.1 Installation Methodbrew and source Helix Versionhelix 24.3 (2cadec0) |
Beta Was this translation helpful? Give feedback.
Answered by
kirawi
Apr 13, 2024
Replies: 1 comment 8 replies
-
|
I'm pretty sure this is not something the maintainers want and it's been rejected in the past. Not much is logged by default at this point so usually it never goes over a couple of megabytes (IIRC). The issue in this case seems to be that you enabled logging on |
Beta Was this translation helpful? Give feedback.
8 replies
-
|
See #735 and #1135 for the previous issues regarding that. I can see how it can be useful but that sounds like something you could achieve yourself with a script (which is what I think the maintainers stance was because it's somewhat of a niche request). Alternatively, you can redirect stderr to |
Beta Was this translation helpful? Give feedback.
-
|
A few questions:
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Ah, actually there is a way to disable it. You can specify the log path |
Beta Was this translation helpful? Give feedback.
Answer selected by
bhansconnect
-
Ah. Probably something that other editors just ignore. Not sure how feasable/valuable fixing is in many cases. For the projects I work with, the lsp works fine, so I never would have know it spits out tons of errors without the helix logs.
Intriguing. Makes sense in terms of complexity. As for the first in years, that is honestly kinda surprising to me. On one hand, I wouldn't be surprised if many users have 1+ GB files and just never notice. On the other hand, for the most part, my config isn't particularly special (especially given I have seen tons of logs from multiple different lsps), so surprised that more users don't fall into the same bucket as me.
Thanks. Might make that my default alias. Or might figure out a simple regular script to properly truncate the log. Still think it would be really nice to have some sort of solution built into the config.toml though. I think any of the following directly in the config.toml would be nice:
|
Beta Was this translation helpful? Give feedback.
-
|
It's possible people encountered the aforementioned issues and decided not to bring it up again, or just deleted the log file and moved on with their day 🤷 I just haven't personally seen it in a while. Regarding the config option, I think one of the reasons it's not being done is because the logger is global and it's hard to pass user input to it: Lines 8 to 34 in 081f7d0 We'll probably need to address that someday as part of #149 |
Beta Was this translation helpful? Give feedback.
-
|
Hi, just to add to that, since you mentioned people not bringing it up much, I just encountered this issue for the first time today: I have the latest version of helix Today my machine was out of memory and after investigating I found out the helix log grew to almost 500GB, at which point helix could no longer write to the file. (Helix did not crash though) |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ah, actually there is a way to disable it. You can specify the log path
hx --logfile /dev/null#3807