Not getting plugin update notifications?

[ownedbycats]

Has anybody else been having trouble with this? I see the plugins have been updated in the forum and on the plugins page but the plugin updates don't show up on my plugin update box even after restarting. So I have to manually download and install them. The two I had to get manually were GetFileName and Kobo Utilities.

I went into Windows firewall but Calibre was already on the list of allowed applications.

I'm hoping this is just one of those gremlins that'll disappear a few minutes after I post this but any suggestions?

[Uncle Robin]

I got notice in Calibre of the Kobo utilities update within 2 hours of davidfor's posting about it here, and the update process worked as usual.

[ownedbycats]

Thanks. Wonder if it's just my internet being cranky again.

[BetterRed]

It can take up to an hour for an updated plugin to show in calibre notify area.

The Plugin Updater process that copies them from here to Kovid's server runs every hour on the half hour.

BR

[theducks]

You can always do Preferences:Get Plugins: <switch to Update available>
NB just tested on 5.01 and it works

[ownedbycats]

I just got an update notification for Goodreads metadata. It seems to be working again.

[enuddleyarbl]

I'm currently having the same problem with the KoboTouchExtended plugin:

https://www.mobileread.com/forums/sh...d.php?t=211135

About two weeks ago, there was an update to 3.5.1 (from 3.4.4, which is what I have) which my system never picked up. Yesterday, an update to 3.5.2 was posted and it's still not showing in Calibre. I've filtered my Plugins by All, Installed, and Update Available with the same result. Interestingly, Calibre notified me of today's Kobo Utilities update to v 2.14.1.

[ownedbycats]

I have the same!

The plugin page still shows as 3.44. I wonder if somehow the update is not reaching the scraper that feeds the update page.

[jgoguen]

A while back there was a problem caused by the version in the plugin being indirect (the tuple is defined in a common file and referenced in each plugin) but that got fixed and davidfor didn't think there were recent changes in that area. Hopefully Kovid sees this and can track down what's going on.

[chaley]

Originally Posted by jgoguen

A while back there was a problem caused by the version in the plugin being indirect (the tuple is defined in a common file and referenced in each plugin) but that got fixed and davidfor didn't think there were recent changes in that area. Hopefully Kovid sees this and can track down what's going on.

The plugin updater processes Abstract Syntax Trees to find the information. ASTs don't compile the source, so the eventual value isn't visible.

You could test if this is the problem by changing the plugin zip to put the text of the version number in plugin.../device/driver.py instead of the reference.

[DNSB]

I was noticing that the two plugins (KTE and Kepub Output) that I am aware of having issues have a url in the version spoiler after the last version that shows as available.

Version 3.5.2 - 2021-07-17
Fix issue with exceptions being thrown in subprocesses
Version 3.5.1 - 2021-07-04
No longer compatible with Python 2
Use a process pool to avoid starting too many threads on massive books (https://github.com/jgoguen/calibre-k...ver/issues/135)
Version 3.4.4 - 2021-01-11
Hopefully fix random disappearing spaces between some words
Version 3.4.3 - 2021-01-05
Fix for non-English locales on Windows failing to load or install the plugin

[davidfor]

Originally Posted by chaley

The plugin updater processes Abstract Syntax Trees to find the information. ASTs don't compile the source, so the eventual value isn't visible.

You could test if this is the problem by changing the plugin zip to put the text of the version number in plugin.../device/driver.py instead of the reference.

I tried to run the plugin_updater locally, but, I am using Windows and there was enough code in it that is non-Windows (os.rename fails if the destination exists), that I ran out of patience fiddling to fix that.

Looking at the history of it, the last change was in November. Which is before the last version of the plugin that is showing on the updater. And I don't see any difference in how the plugin is defining the version. So, I don't see why there is a difference. Unless the version of the plugin updater on the server is not the same as the version on Github.

[kovidgoyal]

It's because those plugins are using type annotations. plugins_mirror.py currently runs under python2 because there are still a lot of plugins that dont even parse under python3.

Either remove the type annotations or use the commnet based syntax for them that is compatible with python2

[kovidgoyal]

And I updated plugins_mirror.py to only use python2 when a plugin fails to parse with python3. And now you can easily test your plugin with it using

calibre-debug plugins_mirror.py plugin.zip

[chaley]

For completeness: using the new version of plugin_mirrors.py on windows I get:

{"name": "KoboTouchExtended", 
"description": "ePub features.", 
"supported_platforms": ["windows", "osx", "linux"], 
"version": [3, 5, 2], 
"author": "Joel Goguen", 
"minimum_calibre_version": [5, 0, 0]}

As far as I can tell this is correct. The new version also appears in the plugin updates dialog.

Clearly I was wrong about the indirection.