Org-mode mailing list
 help / color / Atom feed
From: Justin Vallon <>
Subject: Re: infinite recursion org-update-id-locations / org-entry-properties / org-entry-blocked-p / org-edna / org-id-find / org-id-update-locations
Date: Fri, 31 Jul 2020 14:31:04 -0400
Message-ID: <> (raw)
In-Reply-To: <>

I just tried using straight for org, and master (a1e5bee5c) has a
rewritten org-update-id-locations that uses regexps to find the IDs.  It
appears to have fixed the problem (for cases that I tried).


On 7/30/20 4:21 PM, Justin Vallon wrote:
> I copy by org files between 2 machines.  Thus, my .org-id-locations file
> gets stale when I archive on one machine, then sync the org files.
> I also use org-edna.
> Sometimes, org-agenda will go into an infinite loop (recursion depth,
> etc) when scanning.
> I believe what is happening is:
> - org-agenda / org-edna builds the agenda, and hits a "missing" id(X)
> - org-update-id-locations starts scanning files/nodes to refresh
> - org-cached-entry-get tries to get all properties
> - org-entry-blocked-p is called
> - org-edna then tries to parse the BLOCKER property
> - the property mentions "id(Y)", which has not been found (yet)
> - cache miss, rescan files
> The X and Y could be different, but once id(Y) is missing and the
> cache-miss happens during id-scanning, it will repeat.
> I suppose it also might be sensitive to the order of files in the list,
> since scanning the archive first would scan the older IDs, then the
> active file would reference those older IDs.  However, I would imagine
> there would be trouble if an "earlier" node in the active file
> referenced an ID that appeared "later" in the file, since the file is
> being scanned in-order.
> I haven't tried this, but the simplest case to reproduce might be to
> delete the .org-id-locations file, then feed it:
> * Second
>   BLOCKER: id(first)
> * First
>   ID: first
> I can try to build a (simple) reproducible test case if this is unclear.
> My work-around is to disable org-edna, run org-id-update-id-locations,
> then reenable org-edna.


      reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-30 20:21 Justin Vallon
2020-07-31 18:31 ` Justin Vallon [this message]

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:

  List information:

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

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Org-mode mailing list

Archives are clonable:
	git clone --mirror list/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 list list/ \
	public-inbox-index list

Example config snippet for mirrors

Newsgroups are available over NNTP:

AGPL code for this site: git clone