[GUI Plugin] Kobo Utilities

[JSWolf]

Originally Posted by ownedbycats

Edit line 26 of _init_.py if you want the notification go away.

But the problem is that if you use a version number too high, you won't get notified for a new version and if you use the same number that's being used for the new version, you again won't be notified

It would be best if @Majutsushi released 2.17.2 as 2.18.01. And then we can update to it and no longer be notified of a new version that we don't want.

What's your opinion? Would you prefer a working version or the new features? My opinion is a working version.

[Lys]

My opinion is: the newer features, since this version works correctly for me
Others will be of the opinion they want the previous ones since that works correctly for them and they have no use of the newer features.


But in the end, let Majutsushi work in peace (or help them to correct the error if you are able to ), and in the meanwhile update or revert to the version you like the most, I honestly don't see the major issue here

[ownedbycats]

Originally Posted by JSWolf

But the problem is that if you use a version number too high, you won't get notified for a new version and if you use the same number that's being used for the new version, you again won't be notified.

So use number equal to current version. Duh.

[JSWolf]

Originally Posted by Lys

My opinion is: the newer features, since this version works correctly for me
Others will be of the opinion they want the previous ones since that works correctly for them and they have no use of the newer features.


But in the end, let Majutsushi work in peace (or help them to correct the error if you are able to ), and in the meanwhile update or revert to the version you like the most, I honestly don't see the major issue here

It's better to have a version that works then a version that's buggy.. There could be a lot of people that use Kobo Utilities that do not come here. So all they know is that it's broken if they try to compress the database if they use that feature.

[Lys]

Originally Posted by JSWolf

It's better to have a version that works then a version that's buggy. My question is, since database compression is not working, is anything else not working?

You can check yourself if something else is not working, and then report.

And FOR ME it's better to have a version that works for what I like than having a version that works for something I have no use for.

But I know what is true for me may not be true for everybody, so just go back to whatever version works for you.

[chaley]

Folks, remember that @Majutsushi is volunteering to do this work, starting from a complex code base that no one fully understands. Give him crap, as many seem to be doing, and he could walk away. I know I would.

[JSWolf]

Originally Posted by Lys

You can...

You should edit your post as I've edited it and your reply no longer fits.

[JSWolf]

Originally Posted by chaley

Folks, remember that @Majutsushi is volunteering to do this work, starting from a complex code base that no one fully understands. Give him crap, as many seem to be doing, and he could walk away. I know I would.

Thanks for that reminder.

[decoylad]

Originally Posted by Majutsushi

I can't reproduce the syncing issue, and so far only one person seems to be affected. It's working fine in all my tests, and syncing of existing columns shouldn't have been affected by my changes anyway. So I need some more details to be able to investigate this. I can reproduce the database compression issue, so I'll have a look at that, but it's a rather niche feature. So for now I think it makes more sense to leave the current version and not take away the new features for people that it works fine for.


I have created tickets for the current issues/tasks here for easier tracking:
https://github.com/majutsushi/kobo-utilities/issues

Ok if I specifcally select the Kobo device it is working for me now for Kobo Libra color, I haven't tried with my libra 2.
I haven't attempted the device database compression that seems to be popping up.

@Majutsushi sorry if I havne't been responsive but if there is something specificalyl you want/need me to test I can.

[DNSB]

Personally I will keep the time reading stats and give up the database compression. With my Kobo connected to the computer, I can use several SQLite utilities to compress the database. Given the time it took for someone to notice that the database compression option did not work, it seems fairly obvious that database compression is not on most peoples' top 10 list.

I do agree with @lys and @chaley. Enough of the whinging and give @Majutsushi time to look at the issue. Real life is likely to reduce the amount of time available.

[Majutsushi]

I just created a new release that fixes the compression issue. The previous code was doing something that only accidentally worked and so a cleanup that should have been a no-op had unintended consequences. I think I fixed all the places where that could have caused issues.

[Majutsushi]

Originally Posted by decoylad

Ok if I specifcally select the Kobo device it is working for me now for Kobo Libra color, I haven't tried with my libra 2.
I haven't attempted the device database compression that seems to be popping up.

Glad you found a way to make it work. Are you saying that when you select "Any device" for a profile it doesn't work? That's odd, I've only ever used that setting and it works fine for me.


If you're seeing a difference in behaviour between 2.17.2 and 2.18.0 then the thing that would help the most is if you could create a debug log with both the old and the new version the way it is described at the bottom of the help file (click "Help" in the top right of the config dialog). Ideally when only syncing one or two books so that the log doesn't become too long. I know that's a bit onerous but it's the best way to see what differences there might be.

[theducks]

DB Compression , maybe if you added and removed hundreds of books in a week or month. It is all about CHURN.

The (books) data is just normally marked inactive when you remove a book. After time, these dead records do impact the processing. but for the average reader , (OK, we don't have too many of those here at MR ), you could probably go a year before the DB bloat would affect MODERN devices.
Just think of all the Retail stores with seasonal product churn. They don't Vacuum regularly (if at all).

[Terisa de morgan]

Originally Posted by theducks

DB Compression , maybe if you added and removed hundreds of books in a week or month. It is all about CHURN.

The (books) data is just normally marked inactive when you remove a book. After time, these dead records do impact the processing. but for the average reader , (OK, we don't have too many of those here at MR ), you could probably go a year before the DB bloat would affect MODERN devices.
Just think of all the Retail stores with seasonal product churn. They don't Vacuum regularly (if at all).

Well, sure... but in the same way I've always switched off my computer work, I like to do a weekly clean of my database I've never said I'm an average reader, however

[Phil_C]

Originally Posted by Majutsushi

I just created a new release that fixes the compression issue. The previous code was doing something that only accidentally worked and so a cleanup that should have been a no-op had unintended consequences. I think I fixed all the places where that could have caused issues.

Compression is now working here. Much appreciated.