Checking for addon updates doesn't work anymore
Categories
(Thunderbird :: Untriaged, defect)
Tracking
(Not tracked)
People
(Reporter: juraj.masiar, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:95.0) Gecko/20100101 Firefox/95.0
Steps to reproduce:
This is a regression in the new 91.3.1 version which by the release notes brings:
After an update, Thunderbird will now check installed addons for updates
It will either not do it right or it will use cached response because the addons won't update. And visiting the addons manager and performing the check manually won't do anything either.
I've noticed the repeated manual checks were ignored even before and you would have restart Thunderbird to really re-check for addons updates, now restarting doesn't help anymore because Thunderbird will check when it starts (but obviously badly).
|
||
Updated•4 years ago
|
|
||
Comment 1•4 years ago
|
||
I cannot confirm this.
Can you give an STR starting with a fresh profile in 78?
|
Reporter | |
Comment 2•4 years ago
|
||
Forget it, waiting ~15 minutes helps. I'm not happy, but whatever, I can live with that. I'm sorry for the ping...
|
|
||
Comment 3•4 years ago
|
||
"Waiting 15 minutes" - what do you mean?
Are you releasing a new version of your own add-on and want to check if you receive it via updates? The entire ATN is sitting behind a loadbalancer / cache and that sometimes needs some time before changes are picked up. That has not changed.
|
|
Reporter | |
Comment 4•4 years ago
|
||
Yes, and yes I'm aware of the few seconds delay I have to wait after I get email confirmation about releasing new version.
I've waited, and my Nightly (Daily) successfully updated, so the update was live and working. But my 91.3.1 didn't find the update, so I've restarted it, which normally helps, but after restart the update is was still not found.
Thus my frustration not being able to update my addon which is obviously released and uneatable.
|
|
||
Comment 5•4 years ago
|
||
That is probably a loadbalancer effect, caches have a lifetime and the state of those lifetimes can be different for different endpoints. You do not get the same endpoint every time.
So yes, that is a caching issues, but there is no other way to handle millions of ATN requests. But I do not consider that an issue at all, once all endpoints have updated, all users get the new version and this issue ONLY exists right after a change on ATN.
If this really grinds your gears, you have to setup your own server for your add-ons and use the self-hosting approach.
|
|
Reporter | |
Comment 6•4 years ago
|
||
That makes sense.
On the other hand, the manual check should for sure check for updates no matter what.
That's why it's there, isn't it?
If I'm making an effort by going to the addons manager and clicking the check button, I expect it to check it and not to give me a stale result.
|
|
||
Updated•4 years ago
|
|
|
||
Comment 7•4 years ago
|
||
It does not matter if you use automatic or manual update checks, if the server / endpoint you are querying (which you do not have control over) still has not refreshed its cache, you get the old result. That is how caches work and there is no way to change it. We do not have an endpoint which can be used for production, which is bypassing cache, as that one would simply die under the load, which means you get no result at all.
Description
•