Calibre corrupts last modified date when using the server
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
calibre |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I have a fairly specific bug, that is not completely consistent, and only occurs in certain circumstances.
When starting the server from the main calibre UI, when requesting a book using calibredb including the last_modified field, it returns an error.
Traceback (most recent call last):
File "runpy.py", line 196, in _run_module_as_main
File "runpy.py", line 86, in _run_code
File "site.py", line 83, in <module>
File "site.py", line 78, in main
File "site.py", line 50, in run_entry_point
File "calibre\
File "calibre\
File "calibre\
File "calibre\
File "calibre\
File "calibre\
File "calibre\
File "msgpack/
File "calibre\
File "calibre\
File "calibre\
TypeError: timezone() argument 1 must be datetime.timedelta, not int
If I close calibre, and start the server with the command
calibre-server --disable-
and then rerun the same calibredb command, it does not occur.
This only occurs when requesting the last_modified date, and only when starting the server through the main calibre program.
This means that scripts are unable to find the searched book.
calibre version - 6.24.0
operating system - Windows 11 22H2
What is the calibredb command you are using?