Closed brabalan closed 9 years ago
I use org-id-get-create everywhere, to make sure nothing like that happens, but looking at the org-id code, I don't think there's actually anything that could create a new ID for an entry that already has one. So that's very weird.
I'm in the midst of refactoring and cleaning up all this code, to make it easier to work with. Bear with me for a few days, and hopefully I'll have a cleaner field from which to fix these things.
I think I figured this out -- I was calling org-id-get-create with the force argument, I have no idea why. This should be fixed, but leave it open for a while and see if you get any more similar errors.
Will do.
If you haven't seen this again recently, I'll go ahead and close this...
I haven't seen it indeed, thanks.
I tried to run
gnorb-gnus-outgoing-do-todo
right after sending a message and I got a backtrace:What is surprising is that the searched ID existed before (the message I'm replying to is part of a thread where there is a todo with a
GNORB_MSG_ID
containing a message of the thread; if I go in my org buffer to that task andundo
, then I see the ID as searched; when Iredo
a new ID replaces it). Is it possible that IDs are generated even when they already exist, leading to such an inconsistency?