I'm really sorry Tim. You've stuck with it, it should treat you better. Later this year (est 4th quarter), it will.
It sounds like you went through the correct steps -- the only thing you didn't mention so I'm not sure is whether you're sure ALL four of the lists had a selection. I'm also not sure if you pressed Command+s on all the fields -- but perhaps that doesn't matter anymore since I think you may have fixed that before.
When you hit save, it should come back instantly -- if it timed out it means there was a problem integrating your Install script into the HTTP message request and theres probably a debugger on the server image. I just looked and only saw the old version of NuScratch (10/2018). I was able to Edit Release on that one to see the script. Is all you did was update the .mcz filename, and everything else was the same?
- Chris
On Fri, Apr 26, 2019 at 7:48 PM tim Rowledge tim@rowledge.org wrote:
Argh.
I just tried to update SM for the NuScratch package again. I had saved the new version to SqueakSource and released the version. I opened SM and selected the prior version, chose 'Create New Release'. Updated the install code. Added a commit comment. Set my password. Set the version name. Click on Save'. Wait... timeout!
It failed during the SMReleaseBrowser>savePackageRelease: method, trying to do `smClient save: release`. The actual timeout came as a result of the attempt to read the response, which was reported as 'HTTP/1.1 302 Moved Temporarily
Server: nginx/1.14.2
Date: Sat, 27 Apr 2019 00:31:21 GMT
Content-Type: text/html
Content-Length: 53
Connection: keep-alive
URI: /account
Location: /account
Set-Cookie: SessionID=B2C7C610EB4946C2; path=/
X-Clacks-Overhead: GNU Terry Pratchett
Temporarily moved to: <A HREF="/account">/account</A> {followed by junk}
Seems different to the last problem I had.
tim
tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Success always occurs in private, and failure in full view.