October 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] Iceberg 0.6 released

by Tim Mackinnon

Gosh - It actually work quite well to be able to easily browse code online in a more traditional format of seeing an entire class. Hopefully this leads to us being able to share solutions to common language agnostic problems. One small observation - I quickly grokâd the use of class { â¦. } (with the curly braces) - but given that smalltalk methods often have lots of [ ] (square braces in them), I was a bit surprised to see that method declarations in tonal donât use { â¦ } (curly braces) to denote them, but instead use [ ] - which feels slightly strange given the class declaration above has. {}. Was it easier to parse this way, or is there some subtlety I missed? I would have been tempted to use {} for classes and methods and [] for the protocols as this more closely matches what other languages do - and it might actually make it more easily readable for other programmers. Given we have to learn this new format anyway - Iâd be prepared to give a nod to what others doâ¦ Possibly this observation comes to late - and maybe there is compelling reason to go the route we have gone - but maybe its worth a quick double check as its an exciting development. Tim > On 6 Oct 2017, at 18:18, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi all, > > I released Iceberg version 0.6. It includes a lot of small tweaks and fixes, but the most important inclusion is tonel file format which aims to replace file tree. > > What is Tonel? (https://github.com/pharo-vcs/tonel <https://github.com/pharo-vcs/tonel>) > Tonel is a file-per-class file format for monticello repositories. Itâs purpose is to reduce the amount of files touched each operation, make the IO faster an compact the repositories database. > It has also as an objective to offer an âeasy-to-readâ format, so people wanting to understand a chunk of code will recognise it easily. > For testing, I migrated several of my projects to Tonel and Iâve been using it, you can see some as examples: > > https://github.com/estebanlm/MUDClient <https://github.com/estebanlm/MUDClient> > https://github.com/estebanlm/pharo-tonel <https://github.com/estebanlm/pharo-tonel> (this was just an example and it has some minimal errors already fixed) > > We plan to migrate Pharo development to tonel to address some problems we have: > > - since it has to read/write a lot of files, IO operations are slow > - and even much more slow in Windows > - Windows also has a problem with longpaths. > > Iceberg 0.6 will be integrated to Pharo7 soon :) > To update Pharo 6.1, there are instructions in the readme: https://github.com/pharo-vcs/iceberg/blob/master/README.md <https://github.com/pharo-vcs/iceberg/blob/master/README.md> > now, if you wan to migrate your projects to Tonel (from FileTree), here is a script you can use: https://github.com/pharo-vcs/tonel/blob/master/MigrateFromFileTree.md <https://github.com/pharo-vcs/tonel/blob/master/MigrateFromFileTree.md> > > btw, tonel is independent of Iceberg and can be used with plain Monticello (but it is a metadaless format, history will reside on git, not on monticello). > > cheers, > Esteban

Oct. 6, 2017

Re: [Pharo-dev] [Pharo-users] ZnClient in Pharo 6.1 not working for Https on Windows

by Tim Mackinnon

Can we not contact the windows defender team and find a way to improve their detection? Presumably the signature they are finding is not good enough? Doesnât one of the Dolphin guys work at MS - or does someone in our network have a contact? Tim > On 6 Oct 2017, at 17:54, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > Le 06/10/2017 Ã 18:32, Stephane Ducasse a Ã©crit : >> both now I do not see what we can do if a third party tools consider >> that we are a virus. >> >> > > Done. > > I don't know how to not be detected but Windows Defender is the default > anti-virus on windows. The majority of windows user use it now. If it is > possible to improve this, it would be cool. Maybe someone has experience > in that area? > > > -- > Cyril Ferlicot > https://ferlicot.fr > > http://www.synectique.eu > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France >

Oct. 6, 2017

Re: [Pharo-dev] State of files.pharo.org

by Christophe Demarey

Thanks a lot for the data. Christophe > Le 6 oct. 2017 Ã 17:13, Gabriel Cotelli <g.cotelli(a)gmail.com> a Ã©crit : > > I've added my testing info in the shared notepad. The download of Pharo6.0-linux.zip took 11m 33s on a 30Mbps connection (I've looked while it was downloading and for the first half it was downloading at 40/50 Kbs), so I think it's representative of the slowness we get. As I previously said it's not always slow, sometimes I works fine. > > Regards, > Gabriel > > On Fri, Oct 6, 2017 at 11:07 AM, Christophe Demarey <christophe.demarey(a)inria.fr <mailto:christophe.demarey@inria.fr>> wrote: > Hello, > > I just finished the meeting with a guy from Inria datacenter. > From Inria, we do not see any problem with files.pharo.org <http://files.pharo.org/>. We do not have tools ready to simulate poor networks nor remote network sensors available :( > Thatâs why if some of you could help to collect some data to guess what is the problem, it would be great: If you can run the commands listed there: https://pad.inria.fr/p/IvdGLh650VN8lkoN <https://pad.inria.fr/p/IvdGLh650VN8lkoN> and also put the results at the bottom of the page, it would be very helpful. > In the same time, I created a project on github to run these command on travis CI: https://travis-ci.org/demarey/test-files-pharo-org <https://travis-ci.org/demarey/test-files-pharo-org>. > With all this data, I hope they can spot the problem quickly. > > Thanks, > Christophe >

Oct. 6, 2017

Re: [Pharo-dev] [ANN] Iceberg 0.6 released

by Mariano Martinez Peck

On Fri, Oct 6, 2017 at 4:46 PM, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > Le 06/10/2017 Ã 21:38, Cyril Ferlicot D. a Ã©crit : > > Le 06/10/2017 Ã 21:34, Mariano Martinez Peck a Ã©crit : > >> I followed the instructions to update Iceberg from in a 6.1 image. When > >> I tried to clone the repository, I have the attached error (DNU on > >> #dangerTextColor). I workedaround that by doing: > >> > >> IceAbstractModel >> colorError > >> ^ Color red > >> > >> After I manage to make some progress and I finally was able to clone the > >> repository, I get a #free DNU (see attached too). > >> > > > > Hi, > > > > I introduced #dangerTextColor in Pharo 7 and used it on Iceberg. But I > > though I added it to #Iceberg-Pharo6 package. > > > > I'll check and do a hotfix when I'll have the time. > > > > Humâ¦ This is weird because I see those methods in the Iceberg-Pharo6 > package and I see this package in the baseline. > > Can you check if you have this package? > > Weird.... that package is not being loaded... sure I can explicitly load it ... but I think we must fix the baseline... but the baseline looks correct doesnt it ? I don't understand. -- Mariano http://marianopeck.wordpress.com

Oct. 6, 2017

Re: [Pharo-dev] [ANN] Iceberg 0.6 released

by Cyril Ferlicot D.

Le 06/10/2017 Ã 21:38, Cyril Ferlicot D. a Ã©critÂ : > Le 06/10/2017 Ã 21:34, Mariano Martinez Peck a Ã©critÂ : >> I followed the instructions to update Iceberg from in a 6.1 image. When >> I tried to clone the repository, I have the attached error (DNU on >> #dangerTextColor). I workedaround that by doing: >> >> IceAbstractModel >>Â colorError >> ^ Color red >> >> After I manage to make some progress and I finally was able to clone the >> repository, I get a #free DNU (see attached too).Â >> > > Hi, > > I introduced #dangerTextColor in Pharo 7 and used it on Iceberg. But I > though I added it to #Iceberg-Pharo6 package. > > I'll check and do a hotfix when I'll have the time. > Humâ¦ This is weird because I see those methods in the Iceberg-Pharo6 package and I see this package in the baseline. Can you check if you have this package? (See screen) >> Cheers,Â >> Â >> >> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com > > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Oct. 6, 2017

Re: [Pharo-dev] [ANN] Iceberg 0.6 released

by Mariano Martinez Peck

Another error... I clicked "Open" to the git repository from the MC browser, and I also get an error. See attached. On Fri, Oct 6, 2017 at 4:38 PM, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > Le 06/10/2017 Ã 21:34, Mariano Martinez Peck a Ã©crit : > > I followed the instructions to update Iceberg from in a 6.1 image. When > > I tried to clone the repository, I have the attached error (DNU on > > #dangerTextColor). I workedaround that by doing: > > > > IceAbstractModel >> colorError > > ^ Color red > > > > After I manage to make some progress and I finally was able to clone the > > repository, I get a #free DNU (see attached too). > > > > Hi, > > I introduced #dangerTextColor in Pharo 7 and used it on Iceberg. But I > though I added it to #Iceberg-Pharo6 package. > > I'll check and do a hotfix when I'll have the time. > > > Cheers, > > > > > > > > > > > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > -- > Cyril Ferlicot > https://ferlicot.fr > > http://www.synectique.eu > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France > > -- Mariano http://marianopeck.wordpress.com

Oct. 6, 2017

Re: [Pharo-dev] [ANN] Iceberg 0.6 released

by Cyril Ferlicot D.

Le 06/10/2017 Ã 21:34, Mariano Martinez Peck a Ã©critÂ : > I followed the instructions to update Iceberg from in a 6.1 image. When > I tried to clone the repository, I have the attached error (DNU on > #dangerTextColor). I workedaround that by doing: > > IceAbstractModel >>Â colorError > ^ Color red > > After I manage to make some progress and I finally was able to clone the > repository, I get a #free DNU (see attached too).Â > Hi, I introduced #dangerTextColor in Pharo 7 and used it on Iceberg. But I though I added it to #Iceberg-Pharo6 package. I'll check and do a hotfix when I'll have the time. > Cheers,Â > Â > > > > > > -- > Mariano > http://marianopeck.wordpress.com -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Oct. 6, 2017

Re: [Pharo-dev] [ANN] Iceberg 0.6 released

by Stephane Ducasse

Hi gabriel I think so because this is important for many people. Stef On Fri, Oct 6, 2017 at 8:46 PM, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > Will it be also integrated on Pharo 6.1? > > On Fri, Oct 6, 2017 at 3:10 PM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: >> >> >> On 6 Oct 2017, at 20:08, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> >> On 6 Oct 2017, at 20:05, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> >> Hi esteban >> >> I did not find the script that you mentioned. >> >> >> the one for filetree to tonel? >> >> https://github.com/pharo-vcs/tonel/blob/master/MigrateFromFileTree.md >> >> I will copy here: >> >> locationDir := 'path/to/your/repo' asFileReference. >> subDir := 'your-source-dir-or-empty'. >> sourceDir := locationDir. >> subDir >> ifNotNil: [ >> subDirWithDelim := subDir, '/'. >> sourceDir := sourceDir / subDir ] >> ifNil: [ >> subDirWithDelim := '' ]. >> >> repo := IceRepositoryCreator new >> location: locationDir; >> subdirectory: subDir; >> createRepository. >> >> "branch if you want to perform the migration on separated place (you can >> later do a PR)" >> repo createBranch: 'migrate-sources-to-tonel'. >> >> commit := repo branch lastCommit. >> repo savedPackages do: [ :each | | filetreePackage | >> TonelWriter fileOut: (commit versionFor: each) on: sourceDir. >> filetreePackage := IceLibgitFiletreeWriter directoryNameFor: each. >> (sourceDir / filetreePackage) ensureDeleteAll. >> repo addFilesToIndex: { >> subDirWithDelim, (IceLibgitTonelWriter directoryNameFor: each). >> subDirWithDelim, (IceLibgitFiletreeWriter directoryNameFor: each). } ]. >> >> repo addProperties: (IceRepositoryProperties fromDictionary: { #format -> >> #tonel } asDictionary). >> >> repo >> commitIndexWithMessage: 'sources migrated' >> andParents: { commit }. >> >> repo push. >> >> >> >> >> but beware, to use 0.6 on Pharo7, better wait until integration (next >> week): update is not trivial because pharo project comes with some >> IceMCVersionInfo inside that will become obsolete, etc., etc., etc. >> >> Esteban >> >> >> >> Stef >> >> On Fri, Oct 6, 2017 at 7:18 PM, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >> >> Hi all, >> >> I released Iceberg version 0.6. It includes a lot of small tweaks and >> fixes, >> but the most important inclusion is tonel file format which aims to >> replace >> file tree. >> >> What is Tonel? (https://github.com/pharo-vcs/tonel) >> Tonel is a file-per-class file format for monticello repositories. Itâs >> purpose is to reduce the amount of files touched each operation, make the >> IO >> faster an compact the repositories database. >> It has also as an objective to offer an âeasy-to-readâ format, so people >> wanting to understand a chunk of code will recognise it easily. >> For testing, I migrated several of my projects to Tonel and Iâve been >> using >> it, you can see some as examples: >> >> https://github.com/estebanlm/MUDClient >> https://github.com/estebanlm/pharo-tonel (this was just an example and it >> has some minimal errors already fixed) >> >> We plan to migrate Pharo development to tonel to address some problems we >> have: >> >> - since it has to read/write a lot of files, IO operations are slow >> - and even much more slow in Windows >> - Windows also has a problem with longpaths. >> >> Iceberg 0.6 will be integrated to Pharo7 soon :) >> To update Pharo 6.1, there are instructions in the readme: >> https://github.com/pharo-vcs/iceberg/blob/master/README.md >> now, if you wan to migrate your projects to Tonel (from FileTree), here is >> a >> script you can use: >> https://github.com/pharo-vcs/tonel/blob/master/MigrateFromFileTree.md >> >> btw, tonel is independent of Iceberg and can be used with plain Monticello >> (but it is a metadaless format, history will reside on git, not on >> monticello). >> >> cheers, >> Esteban >> >> >> >> >

Oct. 6, 2017

Re: [Pharo-dev] [ANN] Iceberg 0.6 released

by Mariano Martinez Peck

I followed the instructions to update Iceberg from in a 6.1 image. When I tried to clone the repository, I have the attached error (DNU on #dangerTextColor). I workedaround that by doing: IceAbstractModel >> colorError ^ Color red After I manage to make some progress and I finally was able to clone the repository, I get a #free DNU (see attached too). Cheers, On Fri, Oct 6, 2017 at 3:46 PM, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > Will it be also integrated on Pharo 6.1? > > On Fri, Oct 6, 2017 at 3:10 PM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >> >> On 6 Oct 2017, at 20:08, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> >> On 6 Oct 2017, at 20:05, Stephane Ducasse <stepharo.self(a)gmail.com> >> wrote: >> >> Hi esteban >> >> I did not find the script that you mentioned. >> >> >> the one for filetree to tonel? >> >> https://github.com/pharo-vcs/tonel/blob/master/MigrateFromFileTree.md >> >> I will copy here: >> >> locationDir := 'path/to/your/repo' asFileReference. >> subDir := 'your-source-dir-or-empty'. >> sourceDir := locationDir. >> subDir >> ifNotNil: [ >> subDirWithDelim := subDir, '/'. >> sourceDir := sourceDir / subDir ] >> ifNil: [ >> subDirWithDelim := '' ]. >> >> repo := IceRepositoryCreator new >> location: locationDir; >> subdirectory: subDir; >> createRepository. >> "branch if you want to perform the migration on separated place (you can later do a PR)" >> repo createBranch: 'migrate-sources-to-tonel'. >> >> commit := repo branch lastCommit. >> repo savedPackages do: [ :each | | filetreePackage | >> TonelWriter fileOut: (commit versionFor: each) on: sourceDir. >> filetreePackage := IceLibgitFiletreeWriter directoryNameFor: each. >> (sourceDir / filetreePackage) ensureDeleteAll. >> repo addFilesToIndex: { >> subDirWithDelim, (IceLibgitTonelWriter directoryNameFor: each). >> subDirWithDelim, (IceLibgitFiletreeWriter directoryNameFor: each). } ]. >> >> repo addProperties: (IceRepositoryProperties fromDictionary: { #format -> #tonel } asDictionary). >> >> repo >> commitIndexWithMessage: 'sources migrated' >> andParents: { commit }. >> >> repo push. >> >> >> >> >> but beware, to use 0.6 on Pharo7, better wait until integration (next >> week): update is not trivial because pharo project comes with some >> IceMCVersionInfo inside that will become obsolete, etc., etc., etc. >> >> Esteban >> >> >> >> Stef >> >> On Fri, Oct 6, 2017 at 7:18 PM, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >> >> Hi all, >> >> I released Iceberg version 0.6. It includes a lot of small tweaks and >> fixes, >> but the most important inclusion is tonel file format which aims to >> replace >> file tree. >> >> What is Tonel? (https://github.com/pharo-vcs/tonel) >> Tonel is a file-per-class file format for monticello repositories. Itâs >> purpose is to reduce the amount of files touched each operation, make the >> IO >> faster an compact the repositories database. >> It has also as an objective to offer an âeasy-to-readâ format, so people >> wanting to understand a chunk of code will recognise it easily. >> For testing, I migrated several of my projects to Tonel and Iâve been >> using >> it, you can see some as examples: >> >> https://github.com/estebanlm/MUDClient >> https://github.com/estebanlm/pharo-tonel (this was just an example and it >> has some minimal errors already fixed) >> >> We plan to migrate Pharo development to tonel to address some problems we >> have: >> >> - since it has to read/write a lot of files, IO operations are slow >> - and even much more slow in Windows >> - Windows also has a problem with longpaths. >> >> Iceberg 0.6 will be integrated to Pharo7 soon :) >> To update Pharo 6.1, there are instructions in the readme: >> https://github.com/pharo-vcs/iceberg/blob/master/README.md >> now, if you wan to migrate your projects to Tonel (from FileTree), here >> is a >> script you can use: >> https://github.com/pharo-vcs/tonel/blob/master/MigrateFromFileTree.md >> >> btw, tonel is independent of Iceberg and can be used with plain Monticello >> (but it is a metadaless format, history will reside on git, not on >> monticello). >> >> cheers, >> Esteban >> >> >> >> >> > -- Mariano http://marianopeck.wordpress.com

Oct. 6, 2017

Re: [Pharo-dev] [ANN] OSSubprocess Bugfix and enhancements release

by Stephane Ducasse

Tx you both this is super cool because we really need a strong process integration. **THANKS** I love to be lucky to work with a smart and cool community. On Fri, Oct 6, 2017 at 8:49 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Dear all, > > I have just released a new bugfix and enhancements release v0.2.5 for > OSSubprocess as you can see in [1]. > > This new release is thanks to the awesome work of Guillermo Polito [2]. He > found a problem (and a fix) that would hung/block the Pharo image in a wait > state. This problem has been forever and I have faced it myself. It would > only happen when using #waitForExit and under certain scenario. Because of > that, I recommend everyone to move to this release. > > Aside from that serious bug, he has also done quite some improvements in the > tests and in the Travis setup. Once this PR [3] has been merged and > SmalltalkCI updated, our Travis build [4] should show all green builds for > Linux/OSX and Pharo 5.0 and 6.1. > > I have also copied the configuration into Pharo 5.0 and 6.0 catalog so as of > tomorrow, it should be there. > > > Cheers, > > [1] https://github.com/marianopeck/OSSubprocess/releases/tag/v0.2.5 > [2] https://github.com/marianopeck/OSSubprocess/pull/25 > [3] https://github.com/hpi-swa/smalltalkCI/pull/320 > [4] https://travis-ci.org/marianopeck/OSSubprocess > > > -- > Mariano > http://marianopeck.wordpress.com

Oct. 6, 2017