Seaside loading broken in Pharo 7

> Gesendet: Dienstag, 13. März 2018 um 21:26 Uhr
> Von: "Cyril Ferlicot" <[hidden email]>
> An: "Pharo Development List" <[hidden email]>
> Betreff: Re: [Pharo-dev] Seaside loading broken in Pharo 7
>  
> On mar. 13 mars 2018 at 21:11, Torsten Bergmann <[hidden email]> wrote:
> Hi Pharo-dev (CC Seaside-dev)
>
> the Seaside PR on discussions for Pharo 7 supprt on
>
> https://github.com/SeasideSt/Seaside/pull/979
>
> says one should use
>
> Metacello new
>  baseline:'Seaside3';
>  repository: 'github://SeasideSt/Seaside:master/repository';
>  load.
>
> to load Seaside in Pharo 7 (which was from around 7th of February)
>
> I today tried with latest 70694 fresh Pharo image but after a while I get many
> walkback debuggers with #setToEnd, isReadOnly and #closed not implemented
> on ZnCharacterReadWriteStream
>
> while it is loading "Zinc-Character-Encoding-Core-SvenVanCaekenberghe.56"
>
> If I remember correctly I was able to load it in P7 two weeks ago - so something
> broke it meanwhile.
>
> Any ideas?
>  
> Hi! This is because of a really recent change and Sven is working on it.
>  
>
>
> Bye
> T.
>  
> --
> Cyril Ferlicot
> https://ferlicot.fr
>
> http://www.synectique.eu
> 2 rue Jacques Prévert 01,
> 59650 Villeneuve d'ascq France

> On 21 Mar 2018, at 20:41, Torsten Bergmann <[hidden email]> wrote:
>
>> Normally loading #bleedingEdge of Zn, but I have to see if the very, very latest changes are in.
>>
>> You need Zinc-Character-Encoding-Core-SvenVanCaekenberghe.58 or newer.
>
> Already trapped in Git/Monticello problems:
>
> 1. In latest Pharo 7 Build 70715 I open Monticello browser and then I add
>
>    MCHttpRepository
> location: 'http://mc.stfx.eu/ZincHTTPComponents'
> user: ''
> password: ''
>
>   Now try to browse the contents of the repo I already get a DNU because
>   IceProxyMCVersionInfo returns nil when asked for a #versionNumber leading
>   to other trouble.
>
>
> 2. Now I try to load what you suggested with a script:
>
>      Gofer it
>          url: 'http://mc.stfx.eu/ZincHTTPComponents';
>          package: 'Zinc-Character-Encoding-Core-SvenVanCaekenberghe.58';
>         load
>
>   which fails as this version of the package is not there
>
>   Currently http://mc.stfx.eu/ZincHTTPComponents only goes up to
>
>   Zinc-Character-Encoding-Core-SvenVanCaekenberghe.39
>
> and the 39 up to 58 are missing.
>
> So where is Zinc-Character-Encoding-Core-SvenVanCaekenberghe.58 or newer versions hosted???
>
> Thanks
> T.
>
>
>

> Sven wrote:
> >You must be looking somewhere else,
> >http://mc.stfx.eu/ZincHTTPComponents/
> >find 'Character-Encoding-Core', they are all there.
>
>
>
> Hmmm ... mysterious ... I checked two times yesterday using a web browser after the
> loading trouble in Pharo and it was not there.
>
>
> Works now using:
>
>
> Gofer it
>           url: 'http://mc.stfx.eu/ZincHTTPComponents';
>            package: 'Zinc-Character-Encoding-Core';
>           load.
>
> Metacello new
>   baseline:'Seaside3';
>    repository: 'github://SeasideSt/Seaside:master/repository';
>    load.
>
>
> Thanks
> T.
>
>

> Gesendet: Donnerstag, 22. März 2018 um 23:07 Uhr
> Von: "Torsten Bergmann" <[hidden email]>
> An: [hidden email], [hidden email]
> Betreff: Re: [Pharo-dev] Seaside loading broken in Pharo 7
>
> Seaside is working ... but it is not possible to develop as by patching Zinc
> the Iceberg tool in P7 is broken then and one can not commit anymore.
>
> So be warned when you follow and use the script below.
>
> :(
>
>
>
>
> > Sven wrote:
> > >You must be looking somewhere else,
> > >http://mc.stfx.eu/ZincHTTPComponents/
> > >find 'Character-Encoding-Core', they are all there.
> >
> >
> >
> > Hmmm ... mysterious ... I checked two times yesterday using a web browser after the
> > loading trouble in Pharo and it was not there.
> >
> >
> > Works now using:
> >
> >
> > Gofer it
> >           url: 'http://mc.stfx.eu/ZincHTTPComponents';
> >            package: 'Zinc-Character-Encoding-Core';
> >           load.
> >
> > Metacello new
> >   baseline:'Seaside3';
> >    repository: 'github://SeasideSt/Seaside:master/repository';
> >    load.
> >
> >
> > Thanks
> > T.
> >
> >

> Gesendet: Freitag, 18. Mai 2018 um 15:24 Uhr
> Von: "Cyril Ferlicot D." <[hidden email]>
> An: [hidden email]
> Cc: "Seaside - developer list" <[hidden email]>
> Betreff: Re: [Pharo-dev] [Seaside-dev] Seaside loading broken in Pharo 7
>
> Le 18/05/2018 à 15:21, Torsten Bergmann a écrit :
> > Thanks Sven for the #stable definition.
> >
> > That seems to solve the Zinc issue ... but now I run into a problem with #greaseInteger sent to a character
> > in WAUrlEncoder class when loading Seaside-Core-Johan-Brichau.875.
> >
> > Screenshot attached.
> >
> > But #greaseInteger is not defined for Character, only for Number, Integer and String.
> >
> > To reproduce: I loaded Seaside from STHub using
> >
> >   Metacello new
> >     baseline:'Seaside3';
> >     repository: 'github://SeasideSt/Seaside:master/repository';
> >     load
> >
> > on latest Pharo-7.0+alpha.build.917.
> >
>
> I did not get the problem (yet).
>
> Can you check that your local Seaside and Grease clones are up to date?
> Iceberg does not manage yet upgrade of the local clones :(
>
> > Thanks
> > Torsten
> >
>
>
> --
> Cyril Ferlicot
> https://ferlicot.fr
>
>

> On 18 May 2018, at 15:24, Cyril Ferlicot D. <[hidden email]> wrote:
>
>> Le 18/05/2018 à 15:21, Torsten Bergmann a écrit :
>> Thanks Sven for the #stable definition.
>>
>> That seems to solve the Zinc issue ... but now I run into a problem with #greaseInteger sent to a character
>> in WAUrlEncoder class when loading Seaside-Core-Johan-Brichau.875.
>>
>> Screenshot attached.
>>
>> But #greaseInteger is not defined for Character, only for Number, Integer and String.
>>
>> To reproduce: I loaded Seaside from STHub using
>>
>>  Metacello new
>>    baseline:'Seaside3';
>>    repository: 'github://SeasideSt/Seaside:master/repository';
>>    load
>>
>> on latest Pharo-7.0+alpha.build.917.
>>
>
> I did not get the problem (yet).
>
> Can you check that your local Seaside and Grease clones are up to date?
> Iceberg does not manage yet upgrade of the local clones :(
>
>> Thanks
>> Torsten
>>
>
>
> --
> Cyril Ferlicot
> https://ferlicot.fr
>

> On 19 May 2018, at 22:10, Stephan Eggermont <[hidden email]> wrote:
>
> Sean P. DeNigris <[hidden email]> wrote:
>> Tim Mackinnon wrote
>>> Hi what does it mean “Iceberg does not manage yet upgrade of the local
>>> clones”
>>
>> This is most commonly encountered when one enables shared repository
>> location in Iceberg.
>
> And that also breaks when you need to work on different branches, so a
> shared repository location is at the moment not a recommended setting?
>
> Stephan
>
>

> On 24 May 2018, at 16:02, Sven Van Caekenberghe <[hidden email]> wrote:
>
> Hi Torsten,
>
> Thanks for taking care.
>
> I can confirm, from a quick test, that Seaside loads/works fine in the latest Pharo 7.
>
> I had trouble opening the Seaside Control Panel, 10s of deprecation warnings opening for the icon base64 decoding, I had to comment out the #deprecated: message send in #mimeDecodeToBytes:
>
> I don't understand why the Grease stream tests are failing since they seem to be testing ReadWriteStream, a class that was not changed, at all.
>
> Sven
>
>> On 22 May 2018, at 22:01, Torsten Bergmann <[hidden email]> wrote:
>>
>> Just as an info: after fixing the #mimeDecodeToBytes: issue with recent image 70934 and later it is possible
>> to load Seaside again from GitHub using
>>
>> Metacello new
>> baseline:'Seaside3';
>> repository: 'github://SeasideSt/Seaside:master/repository';
>> load
>>
>>
>> into a recent Pharo 7.0 (load instruction as recommended on https://github.com/SeasideSt/Seaside).
>>
>> For the deprecated warnings you either "Proceed" or disable them for the time being.
>>
>> 799 of 806 Seaside tests passes
>> 470 of 457 Grease  tests passes
>>
>> primarily failing to to non-compatible streams. Seaside and Grease tests seem to test
>> some ANSI related things - who fail now.
>>
>> _______________________________________________
>> seaside-dev mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>
>

> On 21 Jun 2018, at 14:58, Tim Mackinnon <[hidden email]> wrote:
>
> Hi guys - how did you load Seaside into Pharo 7 as part of a baseline? I’ve hit a similar same problem and am getting a walkback error when trying to load a baseline for a project I wanted to try on P7 which uses seaside.
>
> I get: MetacelloNameNotDefinedError: project group, or package named: 'Seaside-Pharo-Development' not found when used in requires: or includes: field of package: 'Seaside-Tests-Pharo-Development' for version: baseline of BaselineOfSeaside3.
>
> My baseline has the following:
>
> setUpDependencies: spec
>
> spec
> baseline: 'Seaside3'
> with: [ spec
> repository: 'github://SeasideSt/Seaside:master/repository';
> loads: #('Seaside-Environment') ].
>
>
> If did have (copied from a Willow example) - and I’m wondering if something is getting cached and that its not actually using the above - but I’m not clear on how to ensure any caches are cleared?
>
> spec
> baseline: 'Seaside3'
> with: [ spec
> repository: 'github://SeasideSt/Seaside:v3.2.4/repository';
> loads: #('Seaside-Environment' 'JQuery' 'Zinc') ];
> project: 'Seaside3-Tests' copyFrom: 'Seaside3' with: [ spec loads: #('Seaside-Tests-Core') ].
>
> Any tips gratefully received.
>
> Tim
>
>> On 24 May 2018, at 16:02, Sven Van Caekenberghe <[hidden email]> wrote:
>>
>> Hi Torsten,
>>
>> Thanks for taking care.
>>
>> I can confirm, from a quick test, that Seaside loads/works fine in the latest Pharo 7.
>>
>> I had trouble opening the Seaside Control Panel, 10s of deprecation warnings opening for the icon base64 decoding, I had to comment out the #deprecated: message send in #mimeDecodeToBytes:
>>
>> I don't understand why the Grease stream tests are failing since they seem to be testing ReadWriteStream, a class that was not changed, at all.
>>
>> Sven
>>
>>> On 22 May 2018, at 22:01, Torsten Bergmann <[hidden email]> wrote:
>>>
>>> Just as an info: after fixing the #mimeDecodeToBytes: issue with recent image 70934 and later it is possible
>>> to load Seaside again from GitHub using
>>>
>>> Metacello new
>>> baseline:'Seaside3';
>>> repository: 'github://SeasideSt/Seaside:master/repository';
>>> load
>>>
>>>
>>> into a recent Pharo 7.0 (load instruction as recommended on https://github.com/SeasideSt/Seaside).
>>>
>>> For the deprecated warnings you either "Proceed" or disable them for the time being.
>>>
>>> 799 of 806 Seaside tests passes
>>> 470 of 457 Grease  tests passes
>>>
>>> primarily failing to to non-compatible streams. Seaside and Grease tests seem to test
>>> some ANSI related things - who fail now.
>>>
>>> _______________________________________________
>>> seaside-dev mailing list
>>> [hidden email]
>>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>>
>>
>
>