MobileRead Forums - View Single Post - content server caching delivery - not delivering latest edit- fresh evidnce

stumped · 01-29-2019, 07:58 AM

a few weeks ago I asserted this ws happening, and got shot down by Kovid who says dotes not happen - cannot happen
at tat time I was unsure whether to blame content server, calibre companion or my device, but here is fresh evidence that it is Content server which is caching
sequence
1. added a book to calibre - delivered it via content server and calibre companion to tablet 1.
2. then noticied that font size needed tweatking on one place, so I fixed that with the editor, then decided I y should not bother correcting it on tablet 1, but instead, I would send the revised version to tablet 2. So, picked up tablet 2 which was on overnight charge connected that to content server and got the book, only to find that I had been served the previous version with the wrong font size. THAT CANNOT BE BLAMED ON DEVICE OR ON CC APP as the tablet 2 target device was OFF until AFTER i fixed up the book and only then asked for it from the content server. the book had never been on that device before.

4. rechecking the book in calibre confirms that it HAS been edited, and the font size fixed.

so the content server had served up a cached version to tablet 2

now how do I convince Kovid to at least take a look at that & check it out ?

for the record I am running calibre v.3.3.7 in windows 10 latest 1809 update. PC is using wired ethernet to my LAN

Steps to reproduce the bug
1 request a book from content server & get it onto a reader
ANY EBUB WILL DO
2 then edit that book. Make some obvious easy to find alteration
3, then delete it from target device and request it again ( without shutting s down calibre. )the unedited version will be re-delivered
now shut down and restart calibre, delete the book from device and request it a 3rd time. the CS will now deliver the latest version

PS I know from previous testing that I can clear this "non existent" cache by shutting down calibre and restarting it. BUT I am seeking some acknowledgement and confirmation that the existing content server behavior is bugged and cannot be blamed on windows or, android, or Calibre

01-29-2019, 07:58 AM	#1
stumped Wizard Posts: 3,305 Karma: 10259306 Join Date: May 2016 Device: kobo forma, Kobo Libra, Huawei media Tab, fire HD10, PW3 HDX8.9,	content server caching delivery - not delivering latest edit- fresh evidnce a few weeks ago I asserted this ws happening, and got shot down by Kovid who says dotes not happen - cannot happen at tat time I was unsure whether to blame content server, calibre companion or my device, but here is fresh evidence that it is Content server which is caching sequence 1. added a book to calibre - delivered it via content server and calibre companion to tablet 1. 2. then noticied that font size needed tweatking on one place, so I fixed that with the editor, then decided I y should not bother correcting it on tablet 1, but instead, I would send the revised version to tablet 2. So, picked up tablet 2 which was on overnight charge connected that to content server and got the book, only to find that I had been served the previous version with the wrong font size. THAT CANNOT BE BLAMED ON DEVICE OR ON CC APP as the tablet 2 target device was OFF until AFTER i fixed up the book and only then asked for it from the content server. the book had never been on that device before. 4. rechecking the book in calibre confirms that it HAS been edited, and the font size fixed. so the content server had served up a cached version to tablet 2 now how do I convince Kovid to at least take a look at that & check it out ? for the record I am running calibre v.3.3.7 in windows 10 latest 1809 update. PC is using wired ethernet to my LAN Steps to reproduce the bug 1 request a book from content server & get it onto a reader ANY EBUB WILL DO 2 then edit that book. Make some obvious easy to find alteration 3, then delete it from target device and request it again ( without shutting s down calibre. )the unedited version will be re-delivered now shut down and restart calibre, delete the book from device and request it a 3rd time. the CS will now deliver the latest version PS I know from previous testing that I can clear this "non existent" cache by shutting down calibre and restarting it. BUT I am seeking some acknowledgement and confirmation that the existing content server behavior is bugged and cannot be blamed on windows or, android, or Calibre Last edited by stumped; 01-29-2019 at 08:01 AM.