unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Camden Narzt via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 61668@debbugs.gnu.org
Subject: bug#61668: Bug in flymake-proc with fix
Date: Tue, 21 Feb 2023 09:15:01 -0700	[thread overview]
Message-ID: <049BD343-8598-44EE-B510-64199BC594F9@me.com> (raw)
In-Reply-To: <CALDnm524oaGuEvo4HnaMyx7B-2BOiD+prkhx9oN9JXu8yXDC8Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 131 bytes --]

Hi João,

Yeah I don’t use flymake-proc directly, I think lsp-mode is using it or something. Anyway I’ve attached a patch.

[-- Attachment #2: flymake-proc.patch --]
[-- Type: application/octet-stream, Size: 579 bytes --]

--- flymake-proc.el.old	2023-02-21 09:12:10
+++ flymake-proc.el.new	2023-02-21 09:11:43
@@ -904,7 +904,7 @@
 (defun flymake-proc--delete-temp-directory (dir-name)
   "Attempt to delete temp dir DIR-NAME, do not fail on error."
   (let* ((temp-dir    temporary-file-directory)
-         (suffix      (substring dir-name (1+ (length (directory-file-name temp-dir))))))
+         (suffix      (substring dir-name (1+ (length (file-truename (expand-file-name (directory-file-name temp-dir))))))))
 
     (while (> (length suffix) 0)
       (setq suffix (directory-file-name suffix))

[-- Attachment #3: Type: text/plain, Size: 3331 bytes --]



Cheers,

Camden


> On Feb 21, 2023, at 5:42 AM, João Távora <joaotavora@gmail.com> wrote:
> 
> Hi Camden,
> 
> Flymake-proc is a deprecated part of Flymake.  I haven't used or tested
> it in a long time (there were never automated tests for it).  When I
> redesigned Flymake years ago, in which flymake-proc became another
> backend, I tested some basic use cases, but I didn't change the
> underlying code, including the directory calculating parts and helpers.
> 
> In other words, this is not "my code" and I never understood it.
> 
> So if you think the change makes sense, go for it i.e. provide a patch
> that we can push. I think there are very few users of this backend
> anyway.
> 
> João
> 
> On Tue, Feb 21, 2023 at 12:35 PM Eli Zaretskii <eliz@gnu.org> wrote:
>> 
>> Adding João.
>> 
>>> Date: Mon, 20 Feb 2023 11:23:02 -0700
>>> From:  Camden Narzt via "Bug reports for GNU Emacs,
>>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>> 
>>> I’m sorry if this is not the correct place to report a flymake-proc bug, but since flymake is included in the emacs git repo I figured it might be ok.
>>> 
>>> I’m currently seeing incorrect behaviour from the `flymake-proc--delete-temp-directory` function. The path is parsed and then reassembled incorrectly as the following backtrace extract demonstrates:
>>> 
>>> flymake-proc--safe-delete-directory("/private/var/folders/p7/03_g5t611499lmjqhwc5tljr0000gn/T/000gn/T/Users/camdennarzt/Developer/Java/getargv.java/src/main/java/cam/narzt/getargv")
>>> flymake-proc--delete-temp-directory("/private/var/folders/p7/03_g5t611499lmjqhwc5tljr0000gn/T/Users/camdennarzt/Developer/Java/getargv.java/src/main/java/cam/narzt/getargv/“)
>>> 
>>> As you can see the `000gn/T/` segment of the path gets duplicated when `flymake-proc--safe-delete-directory` gets called.
>>> 
>>> This is because in `flymake-proc--delete-temp-directory` when the `suffix` variable is declared it is assumed that `(directory-file-name temporary-file-directory)` is a prefix of the `dir-name` argument, however `(directory-file-name temporary-file-directory)` doesn’t seem to resolve symlinks in the path whereas `dir-name` seems to have symlinks already resolved, so they don’t necessarily match. On my system the difference is:
>>> 
>>> (directory-file-name temporary-file-directory) → "/var/folders/p7/03_g5t611499lmjqhwc5tljr0000gn/T”
>>> dir-name → "/private/var/folders/p7/03_g5t611499lmjqhwc5tljr0000gn/T/Users/camdennarzt/Developer/Java/getargv.java/src/main/java/cam/narzt/getargv/“
>>> 
>>> Note the "/private” prefix on the `dir-name` path. That difference in length causes the suffix to be incorrectly determined and then causes a bunch of errors while any subsequent function call tries to work with a path with the `000gn/T/` segment duplicated which obviously doesn’t exist in the fs.
>>> 
>>> Changing the suffix variable to be computed as follows fixes the bug:
>>> 
>>> (substring dir-name (1+ (length (file-truename (expand-file-name (directory-file-name temp-dir))))))
>>> 
>>> 
>>> If this can be fixed that’s great, if there’s somewhere else I should report this I’d love to know.
>>> 
>>> Cheers,
>>> 
>>> Camden Narzt
>>> 
>>> 
>>> 
> 
> 
> 
> -- 
> João Távora


  reply	other threads:[~2023-02-21 16:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20 18:23 bug#61668: Bug in flymake-proc with fix Camden Narzt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-21 12:35 ` Eli Zaretskii
2023-02-21 12:42   ` João Távora
2023-02-21 16:15     ` Camden Narzt via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-10-08 16:35       ` Stefan Kangas
2023-10-08 19:54         ` Camden Narzt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-09  7:45 ` Stefan Kangas
     [not found]   ` <31C926E5-AA1F-403A-A4DB-9F0B448323DC@me.com>
2023-10-09 14:35     ` Stefan Kangas

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=049BD343-8598-44EE-B510-64199BC594F9@me.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=61668@debbugs.gnu.org \
    --cc=c.narzt@me.com \
    --cc=eliz@gnu.org \
    --cc=joaotavora@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).