- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Something is happening...

by Marcus Denker

> On 13 Mar 2018, at 08:27, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > There is something odd happeningâ¦ or better: There is *a lot* happening. > > Just one example: for the Newsletter, the original idea was to send out once a month a post with 3 things, some of them recycled (e.g. pointers to existing projects, re-use âsuccess storiesâ, things like that. > > Now already some months ago I had to add âand here are some other interesting announcements, blog posts, videosâ. > > But this month, the list of things for the newsletter TODO list contains over 60 entries. With the exception of maybe 5, these are just things that happened between sending the February newsletter and today. > > Newsletter March should be ready till this thursday, I hope, subscribe or read the oder ones here: http://newsletter.pharo.org <http://newsletter.pharo.org/> > Newsletter is doneâ¦ will be send out by the system at 3pm local time. This time it took a while to go through all the linksâ¦ it is still odd that all this is just Feb 1 to now. Marcus

March 14, 2018

Re: [Pharo-dev] cannot write to the changes file

by Guillermo Polito

Yes, the changes files were being opened twice, and the second time it failed :). On Tue, Mar 13, 2018 at 11:11 PM, Cyril Ferlicot D. < cyril.ferlicot(a)gmail.com> wrote: > Le 13/01/2018 Ã 18:03, Ben Coman a Ã©crit : > > > > Great! That was quick work (thanks Pavel.) > > Do you have an issue for me to follow, or should I create it? > > > > cheers -ben > > > > It seems that the problem was corrected today (probably the change in > File usage). > > Can someone else confirm? > > -- > Cyril Ferlicot > https://ferlicot.fr > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

March 13, 2018

Re: [Pharo-dev] cannot write to the changes file

by Cyril Ferlicot D.

Le 13/01/2018 Ã 18:03, Ben Coman a Ã©critÂ : > > Great! That was quick work (thanks Pavel.) > Do you have an issue for me to follow, or should I create it? > > cheers -ben > It seems that the problem was corrected today (probably the change in File usage). Can someone else confirm? -- Cyril Ferlicot https://ferlicot.fr

March 13, 2018

Re: [Pharo-dev] Seaside loading broken in Pharo 7

by Cyril Ferlicot

On mar. 13 mars 2018 at 21:11, Torsten Bergmann <astares(a)gmx.de> 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

March 13, 2018

Seaside loading broken in Pharo 7

by Torsten Bergmann

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? Bye T.

March 13, 2018

Re: [Pharo-dev] MCMczWriter>>#flush breaks

by Sven Van Caekenberghe

> On 13 Mar 2018, at 20:22, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > > > On Tue, Mar 13, 2018 at 8:08 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > I was trying to merge in Zinc changes from the latest Pharo 7 back to the MC Zinc repos. It seems like MCMczWriter>>#flush breaks [1]. I can save to the package cache but not to an Http repo, nor copy to it. > > Guile, has this been tested, or do you no longer use the old MC ? > > I do not use old MC since some time already... > > I'll take a look at this tomorrow morning. But if this is broken it means it was not covered by tests :/ Guille (I got your name wrong before, sorry about that), Thanks. Yes there are probably no tests, too bad. I am guessing, the following is wrong, after your changes: MCHttpRepository>>#entityStreamContents: aBlock "Generate output in a buffer because we need the length" | stream | stream := RWBinaryOrTextStream on: String new. aBlock value: stream. stream reset. ^ (ZnStreamingEntity type: ZnMimeType applicationOctetStream) stream: stream; contentLength: stream size; yourself there probably should be no String there. > Sven > > [1] > ByteString(Object)>>error: > ByteString(Object)>>errorImproperStore > ByteString>>at:put: > ZipWriteStream(WriteStream)>>nextPut: > [ :ch | self nextPut: ch ] in ZipWriteStream(DeflateStream)>>next:putAll:startingAt: in Block: [ :ch | self nextPut: ch ] > ByteArray(SequenceableCollection)>>do: > ZipWriteStream(DeflateStream)>>next:putAll:startingAt: > ZipWriteStream(DeflateStream)>>nextPutAll: > ZipStringMember(ZipArchiveMember)>>compressDataTo: > ZipStringMember(ZipArchiveMember)>>writeDataTo: > ZipStringMember(ZipArchiveMember)>>writeTo: > [ :member | > member writeTo: stream. > member endRead ] in ZipArchive>>writeTo: in Block: [ :member | ... > OrderedCollection>>do: > ZipArchive>>writeTo: > MCMczWriter>>flush > MCMczWriter class>>fileOut:on: > MCVersion>>fileOutOn: > [ :s | aVersion fileOutOn: s ] in MCHttpRepository(MCFileBasedRepository)>>basicStoreVersion: in Block: [ :s | aVersion fileOutOn: s ] > MCHttpRepository>>entityStreamContents: > MCHttpRepository>>writeStreamForFileNamed:replace:do: > MCHttpRepository(MCFileBasedRepository)>>writeStreamForFileNamed:do: > MCHttpRepository(MCFileBasedRepository)>>basicStoreVersion: > MCHttpRepository(MCRepository)>>storeVersion: > MCHttpRepository(MCFileBasedRepository)>>storeVersion: > [ super storeVersion: aVersion ] in MCHttpRepository>>storeVersion: in Block: [ super storeVersion: aVersion ] > BlockClosure>>on:do: > MCHttpRepository>>retryOnCredentialRequest: > MCHttpRepository>>storeVersion: > MCWorkingCopyBrowser>>storeVersion:in: > [ self > storeVersion: newVersion in: aRepository; > storeDependencies: newVersion in: aRepository ] in [ [ self > storeVersion: newVersion in: aRepository; > storeDependencies: newVersion in: aRepository ] > ensure: [ (MCVersionInspector new version: newVersion) show ] ] in MCWorkingCopyBrowser>>basicSaveVersionIn: in Block: [ self... > > > > > > -- > > Guille Polito > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > CRIStAL - UMR 9189 > French National Center for Scientific Research - http://www.cnrs.fr > > Web: http://guillep.github.io > Phone: +33 06 52 70 66 13

March 13, 2018

Re: [Pharo-dev] MCMczWriter>>#flush breaks

by Guillermo Polito

On Tue, Mar 13, 2018 at 8:08 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > I was trying to merge in Zinc changes from the latest Pharo 7 back to the > MC Zinc repos. It seems like MCMczWriter>>#flush breaks [1]. I can save to > the package cache but not to an Http repo, nor copy to it. > Guile, has this been tested, or do you no longer use the old MC ? > I do not use old MC since some time already... I'll take a look at this tomorrow morning. But if this is broken it means it was not covered by tests :/ > > Sven > > [1] > ByteString(Object)>>error: > ByteString(Object)>>errorImproperStore > ByteString>>at:put: > ZipWriteStream(WriteStream)>>nextPut: > [ :ch | self nextPut: ch ] in ZipWriteStream(DeflateStream)>>next:putAll:startingAt: > in Block: [ :ch | self nextPut: ch ] > ByteArray(SequenceableCollection)>>do: > ZipWriteStream(DeflateStream)>>next:putAll:startingAt: > ZipWriteStream(DeflateStream)>>nextPutAll: > ZipStringMember(ZipArchiveMember)>>compressDataTo: > ZipStringMember(ZipArchiveMember)>>writeDataTo: > ZipStringMember(ZipArchiveMember)>>writeTo: > [ :member | > member writeTo: stream. > member endRead ] in ZipArchive>>writeTo: in Block: [ :member | ... > OrderedCollection>>do: > ZipArchive>>writeTo: > MCMczWriter>>flush > MCMczWriter class>>fileOut:on: > MCVersion>>fileOutOn: > [ :s | aVersion fileOutOn: s ] in MCHttpRepository( > MCFileBasedRepository)>>basicStoreVersion: in Block: [ :s | aVersion > fileOutOn: s ] > MCHttpRepository>>entityStreamContents: > MCHttpRepository>>writeStreamForFileNamed:replace:do: > MCHttpRepository(MCFileBasedRepository)>>writeStreamForFileNamed:do: > MCHttpRepository(MCFileBasedRepository)>>basicStoreVersion: > MCHttpRepository(MCRepository)>>storeVersion: > MCHttpRepository(MCFileBasedRepository)>>storeVersion: > [ super storeVersion: aVersion ] in MCHttpRepository>>storeVersion: in > Block: [ super storeVersion: aVersion ] > BlockClosure>>on:do: > MCHttpRepository>>retryOnCredentialRequest: > MCHttpRepository>>storeVersion: > MCWorkingCopyBrowser>>storeVersion:in: > [ self > storeVersion: newVersion in: aRepository; > storeDependencies: newVersion in: aRepository ] in [ [ self > storeVersion: newVersion in: aRepository; > storeDependencies: newVersion in: aRepository ] > ensure: [ (MCVersionInspector new version: newVersion) show ] ] in > MCWorkingCopyBrowser>>basicSaveVersionIn: in Block: [ self... > > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

March 13, 2018

MCMczWriter>>#flush breaks

by Sven Van Caekenberghe

Hi, I was trying to merge in Zinc changes from the latest Pharo 7 back to the MC Zinc repos. It seems like MCMczWriter>>#flush breaks [1]. I can save to the package cache but not to an Http repo, nor copy to it. Guile, has this been tested, or do you no longer use the old MC ? Sven [1] ByteString(Object)>>error: ByteString(Object)>>errorImproperStore ByteString>>at:put: ZipWriteStream(WriteStream)>>nextPut: [ :ch | self nextPut: ch ] in ZipWriteStream(DeflateStream)>>next:putAll:startingAt: in Block: [ :ch | self nextPut: ch ] ByteArray(SequenceableCollection)>>do: ZipWriteStream(DeflateStream)>>next:putAll:startingAt: ZipWriteStream(DeflateStream)>>nextPutAll: ZipStringMember(ZipArchiveMember)>>compressDataTo: ZipStringMember(ZipArchiveMember)>>writeDataTo: ZipStringMember(ZipArchiveMember)>>writeTo: [ :member | member writeTo: stream. member endRead ] in ZipArchive>>writeTo: in Block: [ :member | ... OrderedCollection>>do: ZipArchive>>writeTo: MCMczWriter>>flush MCMczWriter class>>fileOut:on: MCVersion>>fileOutOn: [ :s | aVersion fileOutOn: s ] in MCHttpRepository(MCFileBasedRepository)>>basicStoreVersion: in Block: [ :s | aVersion fileOutOn: s ] MCHttpRepository>>entityStreamContents: MCHttpRepository>>writeStreamForFileNamed:replace:do: MCHttpRepository(MCFileBasedRepository)>>writeStreamForFileNamed:do: MCHttpRepository(MCFileBasedRepository)>>basicStoreVersion: MCHttpRepository(MCRepository)>>storeVersion: MCHttpRepository(MCFileBasedRepository)>>storeVersion: [ super storeVersion: aVersion ] in MCHttpRepository>>storeVersion: in Block: [ super storeVersion: aVersion ] BlockClosure>>on:do: MCHttpRepository>>retryOnCredentialRequest: MCHttpRepository>>storeVersion: MCWorkingCopyBrowser>>storeVersion:in: [ self storeVersion: newVersion in: aRepository; storeDependencies: newVersion in: aRepository ] in [ [ self storeVersion: newVersion in: aRepository; storeDependencies: newVersion in: aRepository ] ensure: [ (MCVersionInspector new version: newVersion) show ] ] in MCWorkingCopyBrowser>>basicSaveVersionIn: in Block: [ self...

March 13, 2018

Re: [Pharo-dev] Family contact book ?

by Stephane Ducasse

:) On Tue, Mar 13, 2018 at 5:15 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Yes, it is example how access commands from World menu and by global > shortcut (there is section in Commander booklet). > > It will be disabled in next Calypso integration. > > > > 2018-03-13 17:10 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> >> This is an example for commander :) >> >> >> On Tue, Mar 13, 2018 at 5:08 PM, Sven Van Caekenberghe <sven(a)stfx.eu> >> wrote: >> > There is (probably an example) called 'Family contact book' in the World >> > menu ... weird. >> >

March 13, 2018

Re: [Pharo-dev] Family contact book ?

by Denis Kudriashov

Yes, it is example how access commands from World menu and by global shortcut (there is section in Commander booklet). It will be disabled in next Calypso integration. 2018-03-13 17:10 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > This is an example for commander :) > > > On Tue, Mar 13, 2018 at 5:08 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > > There is (probably an example) called 'Family contact book' in the World > menu ... weird. > >

March 13, 2018