[squeak-dev] Server timeouts and 504 return codes

David T. Lewis lewis at mail.msen.com
Tue Jan 29 02:41:01 UTC 2019


On Mon, Jan 28, 2019 at 06:02:05PM -0600, Chris Muller wrote:
> >
> > > I guess I don't know what you mean -- I see only one Chronology-ul.21
> > > in the ancestry currently anyway..
> >
> > Never said it was in the ancestry. In the Trunk there is:
> >
> > Name: Chronology-Core-ul.21
> > Author: dtl
> > Time: 4 January 2019, 1:17:39.848442 pm
> > UUID: 5d9b02fa-8e37-4678-adda-f302163732a1
> >
> > In the Treated Inbox there is:
> >
> > Name: Chronology-Core-ul.21
> > Author: ul
> > Time: 26 December 2018, 1:48:40.220196 am
> > UUID: 2e6f6ce2-d0ec-41a0-b27c-88c642e5afc9
> 
> Okay.  Are you the author of both?  This is something you yourself
> need to guard against doing, but as it's in Treated anyway, I don't
> really see any pertinent impact in the case of Chronology-Core-ul.21.
>

This is because of the the following commit that I made to trunk:

  Name: Chronology-Core-ul.21
  Author: dtl
  Time: 4 January 2019, 1:17:39.848442 pm
  UUID: 5d9b02fa-8e37-4678-adda-f302163732a1
  Ancestors: Chronology-Core-dtl.20
  
  From Chronology-Core-ul.21 from inbox, and resaved to ensure that
  version history exactly matches that of trunk. Updated by dtl and
  saved with original author initials.

This was a case in which I intentionally re-wrote the version
history in in order to make the trunk update stream appear to be
clean even though it actually contained a merge of a long series
of changes that had been developed and maintained elsewhere
(http://www.squeaksource.com/UTCDateAndTime).

Regardless of whether you think that "cleaning" the version history
is a good thing to do, there is no way that a local package-cache
based on file names can be expected to figure out the resulting
confusion.

Dave 


More information about the Squeak-dev mailing list