emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Ihor Radchenko <yantar92@posteo.net>
To: Stefan <org@stefan.failing.systems>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-element--cache: (org-agenda) Cached element is incorrect [9.6 (release_9.6-90-gf49ee9 @ /home/stefan/.emacs.d/contrib/org-mode/lisp/)]
Date: Thu, 15 Dec 2022 08:14:19 +0000	[thread overview]
Message-ID: <87359hw0bo.fsf@localhost> (raw)
In-Reply-To: <0818f914-1c9d-48d7-bb32-18909f9564a1@app.fastmail.com>

Stefan <org@stefan.failing.systems> writes:

> While trying to reproduce the "Org parser error" error issue (see other thread), I got multiple "Cached element is incorrect" warnings (backtrace excerpt below).
>
> Here is one that appeared when trying to loading the =t= agenda:

Thanks, but a small portion of the backtrace is not helpful here.
"Cached element is incorrect" appears to be related to some buffer edits
being missed by the cache, which can only be visible by looking at the
full history of registered cache edits.

There is a reason why this much backtrace is generated. The real problem
often appears long time before the actual issue is caught by
self-verification code.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
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>

next prev parent reply	other threads:[~2022-12-15  8:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14 21:24 [BUG] org-element--cache: (org-agenda) Cached element is incorrect [9.6 (release_9.6-90-gf49ee9 @ /home/stefan/.emacs.d/contrib/org-mode/lisp/)] Stefan
2022-12-15  8:14 ` Ihor Radchenko [this message]
2022-12-15 11:58   ` Stefan
2022-12-15 12:16     ` Ihor Radchenko
2022-12-15 18:05       ` Stefan
2022-12-15 18:42         ` Ihor Radchenko
2023-01-02  7:29           ` Ihor Radchenko

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.orgmode.org/

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

  git send-email \
    --in-reply-to=87359hw0bo.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=org@stefan.failing.systems \
    /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

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.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).