From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] `neovim` package is built with debug information logging
Date: Wed, 01 Feb 2023 09:43:15 +0100 [thread overview]
Message-ID: <20230201084315._13ZO7XD9gbqr9aNVSzw9fBrmC4JYqTxWcqxoNqTpCw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42010@inbox.vuxu.org>
[-- 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"`
prev parent reply other threads:[~2023-02-01 8:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 6:31 [ISSUE] " Elvyria
2023-02-01 8:43 ` sgn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230201084315._13ZO7XD9gbqr9aNVSzw9fBrmC4JYqTxWcqxoNqTpCw@z \
--to=sgn@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).