View Single Post
Old 04-25-2022, 05:38 PM   #7049
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,509
Karma: 8065348
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by JimmXinu View Post
I'm not able to duplicate.

That's the code that calls into calibre to marked updated books with db.set_marked_ids(marked_ids).

Considering the Calibre marking code just got a significant update, I suspect it's either a problem with that, or with how FFF calls it.

How many downloads/updates were you doing at the time?
Looking at the code and the trace it appears that FFF is calling set_marked_ids() with a dict that contains None values, as in {1234:None}. It is likely that this was converted to {1234:True} before the changes, while now for a key:value pair the value is preserved. The dict passed to set_marked_ids() should contain only books that are to be marked using a text string or the value "true" (not a boolean True) if a general (non-text) mark is desired. Books that are to be unmarked should be left out of the dict.
chaley is offline   Reply With Quote