[squeak-dev] trunk update stream appears to have become inaccessible

Thiede, Christoph Christoph.Thiede at student.hpi.uni-potsdam.de
Tue Dec 27 20:22:17 UTC 2022


>From the perspective of someone who has only gotten to know SqueakSource from the client side: The possibility to enumerate *all* trunk versions is important for me in several situations. It would be quite a shame if one could no longer access the full ancestry of a version or browse an ancient version of any package through the UI. The release notes generator in the ReleaseBuilder could also be affected, I think.


With a view to modern REST and GraphQL APIs, would it be possible to add support for some parameters to the requests in question to enable pagination or filter the retrieved information vertically (i.e., leave out some metadata)?


Best,

Christoph

________________________________
Von: Chris Muller <ma.chris.m at gmail.com>
Gesendet: Dienstag, 27. Dezember 2022 21:03:58
An: Thiede, Christoph
Cc: The general-purpose Squeak developers list; box-admins at lists.squeakfoundation.org
Betreff: Re: [squeak-dev] trunk update stream appears to have become inaccessible


> So, I changed the production server code to only return the last 1000 of those 14000, it's "working" again.

Just in case this wasn't obvious, updating your image still doesn't work because many versions are missing. Round-robin or some date-based heuristic would surely be a better (yet more complex) workaround. :-)

Yup.  And, it would alleviate our property of unsustainability.  I'm curious about the proxy configuration, but this has me wanting to come up with something in the app code in any case.  We're just sending that ever-growing list over the wire hundreds, possibly thousands of times, every day.  I like your idea of having age be a factor.

The impact of such a change would occur in the Repository browser.  There would be fewer Versions in the right-hand pane for each package.  However, I think it would be able to use the ancestry to diff anything older than what the Repository browser showed, so it may not be a big deal..  Does anyone see any holes in this idea?

 - Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20221227/0a7a8716/attachment.html>


More information about the Squeak-dev mailing list