* [ISSUE] `neovim` package is built with debug information logging
@ 2023-02-01 6:31 Elvyria
2023-02-01 8:43 ` [ISSUE] [CLOSED] " sgn
0 siblings, 1 reply; 2+ messages in thread
From: Elvyria @ 2023-02-01 6:31 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 902 bytes --]
New issue by Elvyria on void-packages repository
https://github.com/void-linux/void-packages/issues/42010
Description:
### Is this a new report?
Yes
### System Info
Void 6.1.8_1
### Package(s) Affected
neovim-0.8.2_2
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
Release build of `neovim`, on launch, creates log file of a size 0, assuming nothing is actually worth logging.
### Actual behaviour
`Neovim` is logging full debug info to `$XDG_STATE_HOME/nvim/log` or `$NVIM_LOG_FILE`
Accidentally stumbled upon a 5gb log file, that contains nothing, but garbage.
This commit is to blame befd5f42c7da43c0874b618cd4de16f4db7fac05. Assuming that it's already at 5gb after 3 weeks, this can get nasty.
### Steps to reproduce
1. Open `nvim`
2. `du "$XDG_STATE_HOME/nvim/log"` or `du "$NVIM_LOG_FILE"`
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [ISSUE] [CLOSED] `neovim` package is built with debug information logging
2023-02-01 6:31 [ISSUE] `neovim` package is built with debug information logging Elvyria
@ 2023-02-01 8:43 ` sgn
0 siblings, 0 replies; 2+ messages in thread
From: sgn @ 2023-02-01 8:43 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
Closed issue by Elvyria on void-packages repository
https://github.com/void-linux/void-packages/issues/42010
Description:
### Is this a new report?
Yes
### System Info
Void 6.1.8_1
### Package(s) Affected
neovim-0.8.2_2
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
Release build of `neovim`, on launch, creates log file of a size 0, assuming nothing is actually worth logging.
### Actual behaviour
`Neovim` is logging full debug info to `$XDG_STATE_HOME/nvim/log` or `$NVIM_LOG_FILE`
Accidentally stumbled upon a 5gb log file, that contains nothing, but garbage.
This commit is to blame befd5f42c7da43c0874b618cd4de16f4db7fac05. Assuming that it's already at 5gb after 3 weeks, this can get nasty.
### Steps to reproduce
1. Open `nvim`
2. `du "$XDG_STATE_HOME/nvim/log"` or `du "$NVIM_LOG_FILE"`
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-02-01 8:43 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-01 6:31 [ISSUE] `neovim` package is built with debug information logging Elvyria
2023-02-01 8:43 ` [ISSUE] [CLOSED] " sgn
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).