emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Stefan <org@stefan.failing.systems>
To: 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 12:58:36 +0100	[thread overview]
Message-ID: <52739b43-b836-44db-a250-7323ff8d294c@app.fastmail.com> (raw)
In-Reply-To: <87359hw0bo.fsf@localhost>

Hello,

sorry, I was not aware of that. I am sending the full backtrace unredacted to you directly. 

The respective org files are in a git repo, and there I don't see any edits in the files since starting emacs (also not after manually saving all org buffers).

Let me know if you need anything else.

Best,
 Stefan


On Thu, Dec 15, 2022, at 09:14, Ihor Radchenko wrote:
> 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.


  reply	other threads:[~2022-12-15 11:59 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
2022-12-15 11:58   ` Stefan [this message]
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=52739b43-b836-44db-a250-7323ff8d294c@app.fastmail.com \
    --to=org@stefan.failing.systems \
    --cc=emacs-orgmode@gnu.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.
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).