Install button no longer gets the latest version of the script

in Userscripts.org discussion
Subscribe to Install button no longer gets the latest version of the script 17 posts, 7 voices



Vess Scriptwright
FirefoxWindows

While downloading a few scripts that have been updated recently, I suddenly noticed the the Install button no longer serves the latest (updated) version of the script! This really sucks!

I had to go to the source code page, inspect the previous versions, and download from the Install link of the topmost one.

Fix, please. It's probably again some screw-up with the clouded hosting... I wish we could go back to the sunny days...

 
Harm_ru Scriptwright
ChromeWindows

I have the same problem.

 
Marti Scriptwright
FirefoxX11

Vess wrote:
Install button no longer serves the latest
Please give a sample script homepage. Did a few random tests and I'm getting the most current versions.

 
Harm_ru Scriptwright
ChromeWindows

It seems to be ok now.

 
Jesse Andrews Admin
ChromeMacintosh

Yesterday just scaled the service from 1 app server to many to deal with the 5X traffic peaks (up to 1000 requests per second).

It could be caching issues. Checking it out

 
Vess Scriptwright
FirefoxWindows

Yes, it works now.

 
Jesse Andrews Admin
ChromeMacintosh

what was the script id? I didn't change anything yet - so I'm afraid it might be broken still on a single box out of the cluster.

 
Zyphir Scriptwright
FirefoxWindows

Hello,

Indeed, I still have the problem on this script http://userscripts.org/scripts/show/93313 (which is a beta version of http://userscripts.org/scripts/show/92414 that works well).

 
Marti Scriptwright
FirefoxX11

Zyphir wrote:
Indeed, I still have the problem on this script http://userscripts.org/scripts/show/93313
Thanks for the script homepage link... confirmed.

Source Code page says here, right now:

...
// @version         3.1.0.0c
...

and GM bypassed says:

...
// @version         3.1.0.0b
...

Page refresh on user.js URI now says 3.1.0.0c within a few minutes.

Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 (64bit edition)

 
Jesse Andrews Admin
ChromeMacintosh

Updated the caching code... There were a few gotchas in a multi-node deployment

 
Zyphir Scriptwright
FirefoxWindows

It works fine now. Thanks!

 
Marti Scriptwright
FirefoxX11

Still getting this issue on this versus that. It's been about 16 hours since author updated and about 2 days since I last visited that page I think.


Rechecked 2011 08 07 Appears resolved

 
Marti Scriptwright
FirefoxX11

Another in this versus that.


Rechecked on 2011 08 22
Still hasn't been resynced :S


Rechecked on 2011 10 09
Still hasn't been resynced :S

 
SparkysBigPa... User
ChromeWindows

The same happens to me!

 
Marti Scriptwright
FirefoxX11

@Jesse Andrews,
This happened again just a few moments ago with my script here. Seems to be serving the current one now though.


And here... this one fixed as of 2011 11 11 01:02 (OOOOH! it's 11/11/11 ;)
And here :(


This is entirely unpredictable... various times I get the latest version others I get a version before. This includes @require, etc. values that point to USO. Kicked my entire network just to be sure it's not here.


I also noticed when browsing https://userscript.org/ the Install button on script homepages isn't secure here.


amazonaws.com CDN is leaking in secure browsing mode on userscripts.org (e.g. pulls unsecure image)
https://greasefire.userscripts.org/ isn't denoted as a valid SSL certificate for userscripts.org and SSL connections are also having old versions served too starting today (Friday).


This topic is probably related too.

 
Marti Scriptwright
FirefoxX11

For those interested I've added a "white text on black background" install button notification to uso - installWith(assuming you can get 0.18.1+ served on installation) to detect this USO issue a portion of the time when this is happening. It is still intermittent... some visits to my scripts (and everyone elses) are okay and then I return later and they are black (e.g. not being served the most current user.js) I've lost count at how many times this has happened during testing phase of detection. *sigh*

 
sizzlemctwizzle Scriptwright
FirefoxWindows

I just experienced this today when I updated one of my scripts. The updated version isn't being served.

Edit: Nevermind, it works now. Just took a little while to update.