all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 75209@debbugs.gnu.org, njackson@posteo.net
Subject: bug#75209: 30.0.93; Emacs reader failed to read data in "/home/nlj/.cache/org-persist/gc-lock.eld"
Date: Wed, 01 Jan 2025 09:42:28 +0000	[thread overview]
Message-ID: <87ldvug9a3.fsf@localhost> (raw)
In-Reply-To: <86v7uzljc5.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> Another possible scenario is two Org instances writing to the same file
>> at the same time.
>> If it is what is happening in your case, your problem may be similar to 
>> https://list.orgmode.org/orgmode/CAMJKaZxA_VmLdFP_u1rNiF2s0X2kVivjT31jEM_r3BYCHri1PQ@mail.gmail.com/
>
> Can't Org prevent more than one session writing to this file?  We have
> file locks which can be used here, I think.

That's exactly the idea I am trying in the linked thread to address the
issue.

It is not the biggest problem there though. The problem is when there is
a race between Emacs processes writing to the same file one after
another (without any locking). Contents of the file may then become
unexpected compared to other Emacs session.

-- 
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>





  reply	other threads:[~2025-01-01  9:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-30 18:48 bug#75209: 30.0.93; Emacs reader failed to read data in "/home/nlj/.cache/org-persist/gc-lock.eld" N. Jackson
2024-12-30 19:31 ` Eli Zaretskii
     [not found]   ` <87zfkddk1l.fsf@Phoenix>
2024-12-30 20:01     ` Eli Zaretskii
2025-01-01 17:41       ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-01 18:52         ` Eli Zaretskii
2025-01-01 21:09           ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-31 17:42   ` Ihor Radchenko
     [not found]     ` <87frm3elkr.fsf@Phoenix>
2024-12-31 19:02       ` Ihor Radchenko
2024-12-31 19:54         ` Eli Zaretskii
2025-01-01  9:42           ` Ihor Radchenko [this message]
2025-01-01 12:14             ` Eli Zaretskii
2025-01-02 17:28               ` Ihor Radchenko
2025-01-02 18:48                 ` Eli Zaretskii
2025-01-05 10:03                   ` Ihor Radchenko
2025-01-05 11:15                     ` Eli Zaretskii
2025-01-05 13:18                       ` Ihor Radchenko
2025-01-01 15:54         ` N. Jackson
2025-01-02 13:34 ` N. Jackson
2025-01-05 14:18   ` N. Jackson
2025-01-05 17:21     ` Eli Zaretskii
2025-01-06  0:58       ` N. Jackson
2025-01-06 13:49         ` Eli Zaretskii

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=87ldvug9a3.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=75209@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=njackson@posteo.net \
    /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.