[squeak-dev] Bug in SqueakSource mailer service?

Thiede, Christoph Christoph.Thiede at student.hpi.uni-potsdam.de
Mon Oct 12 21:45:31 UTC 2020


Hi Dave,


a naive question: Why isn't SqueakSource running on an automatically updated Trunk image, maybe only pulling updates that were approved by a CI process? Wasn't it worth the effort? :-)


Best,

Christoph

________________________________
Von: Squeak-dev <squeak-dev-bounces at lists.squeakfoundation.org> im Auftrag von David T. Lewis <lewis at mail.msen.com>
Gesendet: Montag, 12. Oktober 2020 23:30:04
An: The general-purpose Squeak developers list
Betreff: Re: [squeak-dev] Bug in SqueakSource mailer service?

Hi Christoph,

On Mon, Oct 12, 2020 at 11:34:04AM +0000, Thiede, Christoph wrote:
> Hi all,
>
>
> that's funny. I uploaded EToys-ct.409, whiches removes some invalid encoding characters from a method comment, half an hour ago and it did not appear in the mailing list. However, Monticello-ct.731 which I uploaded some minutes later appeared on the list as usual. Do we have some bug in the mailer service code that stumbled upon the special characters in the method comment?
>
>
> Here is the (manually created) diff:
>
>
>   assureContentAreaStaysAt: aPoint
> -  "selbst-verst????????????????????????????ndlich"
>
> self currentWorld doOneCycleNow.
> self topLeft: ((self topLeft - contentArea topLeft ) + aPoint)
>

I do not know the answer to your question, but based on my experience
supporting the old squeaksource.com server (which has until recently
been running on an older image and squeaksource code base), I would
not be surprised to find bugs like this related to improper handling
of WideString in squeaksource.

In earlier years, squeaksource.com was being used heavily by students
for Pharo-based classroom assignments. User names that (quite properly)
used WideString for the user name would cause failures in the squeaksource
application, and I would have to "fix" these problems by converting
the usernames to plausible 8-bit strings in the squeaksource.com image.
These failures happened quite frequently for a number of years after
the Pharo community moved to smalltalkhub.com, because squeaksource.com
was still being used to support classroom projects.

On source.squeak.org we did not ever have these issues, possibly because
it was running on a newer Squeak image with better support for WideString,
or possibly simply because the active developers on source.squeak.org
have been in the habit of avoiding the use of international character
sets in their commits.

My guess is that you have uncovered a bug in SqueakSqueak that simply
has not been noticed until now.

Dave


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20201012/b3ed9964/attachment.html>


More information about the Squeak-dev mailing list