all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: chad <yandros@gmail.com>
To: Thomas Klausner <wiz@gatalith.at>
Cc: emacs-devel@gnu.org
Subject: Re: broken (or missing) packages after 'error in process sentinel: async-handle-result: End of file during parsing'
Date: Tue, 7 Mar 2023 15:57:24 -0500	[thread overview]
Message-ID: <CAO2hHWaVsOtmPWSVHMJ78uBjhAjnc15UDAb_=opMXVwNGYm=AA@mail.gmail.com> (raw)
In-Reply-To: <ZAcBrJNWHA1eishx@yt.nih.at>

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

This used to happen to me pretty often when I would update emacs, relaunch
it, and then immediately update packages. What I saw was that async native
compile would schedule/start a file, package.el would update that elpa
package with new code, and then async-jit-native-compile would try to
compile the since-replaced file.
It went away when I started giving the new emacs a little time to catch up
before running package-list-packages; I would sometimes manually work
around the problem with package-recompile-all.

I started a bug report and then stopped, because it was very closely tied
to the developer-centric behavior -- I didn't see it if I let the new emacs
"settle" for a few minutes of normal use.

Hope that helps,
~Chad

[-- Attachment #2: Type: text/html, Size: 852 bytes --]

  parent reply	other threads:[~2023-03-07 20:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07  9:19 broken (or missing) packages after 'error in process sentinel: async-handle-result: End of file during parsing' Thomas Klausner
2023-03-07 13:06 ` Eli Zaretskii
2023-03-07 13:22   ` Thomas Klausner
2023-03-07 20:57 ` chad [this message]
2023-03-08  5:18   ` Michelangelo Rodriguez
2023-03-09 10:27   ` Thomas Klausner
2023-03-09 12:46     ` Thierry Volpiatto

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='CAO2hHWaVsOtmPWSVHMJ78uBjhAjnc15UDAb_=opMXVwNGYm=AA@mail.gmail.com' \
    --to=yandros@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=wiz@gatalith.at \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.