- Pharo-dev - lists.pharo.org

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

by Esteban Lorenzano

> 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 <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. > > 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 Stephane Ducasse

Hi esteban I did not find the script that you mentioned. 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

[ANN] Iceberg 0.6 released

by Esteban Lorenzano

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 Cyril Ferlicot D.

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] [Pharo-users] ZnClient in Pharo 6.1 not working for Https on Windows

by Stephane Ducasse

both now I do not see what we can do if a third party tools consider that we are a virus. On Fri, Oct 6, 2017 at 6:09 PM, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > Le 06/10/2017 Ã 13:02, kmo a Ã©crit : >> I was trying to Soup on Windows 7 and found I could not access https sites >> >> On windows 7 and 10 the following code fails: >> >> ZnEasy get:'https://genius.com/Alice-nuvole-lyrics'. >> >> This works fine in Pharo 5 on Windows. Also works fine with Pharo 6.1 (32 >> bit) on Linux. >> >> The problem is Pharo 6.1 on Windows. >> >> The error is: >> >> "SSL/TLS plugin initialization failed (VM plugin missing ? OS libraries >> missing ?)" >> >> I know that his has been seen on Linux in the past - see >> http://forum.world.st/SSL-TLS-plugin-initailization-failed-VM-plugin-missin… >> >> I'm running the latest vm and 6.1 image. >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> > > I just saw that Windows Defender consider this plugin as a Trojan and > delete it. > > Name of the menace: Trojan:Win32/Azden.A!cl > > Should this be reported on Pharo's issue tracker or on opensmalltalk one? > > -- > 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] [Pharo-users] ZnClient in Pharo 6.1 not working for Https on Windows

by Cyril Ferlicot D.

Le 06/10/2017 Ã 13:02, kmo a Ã©critÂ : > I was trying to Soup on Windows 7 and found I could not access https sites > > On windows 7 and 10 the following code fails: > > ZnEasy get:'https://genius.com/Alice-nuvole-lyrics'. > > This works fine in Pharo 5 on Windows. Also works fine with Pharo 6.1 (32 > bit) on Linux. > > The problem is Pharo 6.1 on Windows. > > The error is: > > "SSL/TLS plugin initialization failed (VM plugin missing ? OS libraries > missing ?)" > > I know that his has been seen on Linux in the past - see > http://forum.world.st/SSL-TLS-plugin-initailization-failed-VM-plugin-missin… > > I'm running the latest vm and 6.1 image. > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > I just saw that Windows Defender consider this plugin as a Trojan and delete it. Name of the menace: Trojan:Win32/Azden.A!cl Should this be reported on Pharo's issue tracker or on opensmalltalk one? -- 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 Gabriel Cotelli

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> 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. 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 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. > With all this data, I hope they can spot the problem quickly. > > Thanks, > Christophe >

Oct. 6, 2017

Re: [Pharo-dev] Never-ending computations and cmd-dot

by Guillermo Polito

On Fri, Oct 6, 2017 at 4:52 PM, HernÃ¡n Morales Durand < hernan.morales(a)gmail.com> wrote: > Hi Guille > > 2017-10-03 9:15 GMT-03:00 Guillermo Polito <guillermopolito(a)gmail.com>: > >> I've been bitten by this dozens of times. >> >> The problem seems to be that a second UI process is created and thus the >> DNU exception is automatically resumed (indefinitely). Executing the >> following expression seems to remove the problem: >> >> UIManager default spawnNewProcess >> >> > Thanks. > > That expression prevents the recursive exception windows from opening? Or > it is a post-mortem measure? > It's for once "you have the problem". As you may notice, usually when you have an exception you'll be given a debugger. This infinite debugger bug happens really occasionally. I use that expression to fix my system, but still don't know what makes it go nuts :( > So it should be executed at image startup? > > I will check. > > > > >> Still, I do not know the cause of it. >> >> On Wed, Sep 27, 2017 at 4:28 AM, Stephane Ducasse < >> stepharo.self(a)gmail.com> wrote: >> >>> Hi hernan >>> >>> Indeed it would be nice to have a solution for such case. Now we did >>> not look at it. >>> >>> Stef >>> >>> On Tue, Sep 26, 2017 at 5:58 AM, HernÃ¡n Morales Durand >>> <hernan.morales(a)gmail.com> wrote: >>> > Hi Tim, >>> > >>> > Yes, I am aware of such menu item. However I would like to know if >>> > someone is working in a more architectural solution. >>> > Because I guess this would imply to hook message sends into the main >>> > feedback loop. >>> > >>> > Cheers, >>> > >>> > HernÃ¡n >>> > >>> > >>> > 2017-09-25 20:08 GMT-03:00 Tim Mackinnon <tim(a)testit.works>: >>> >> Its not quite what you are asking for, but if you right click on one >>> of those windows, someone has helpfully added a âclose all windows to >>> rightâ option, which does let you rapidly get rid of them. >>> >> >>> >> Tim >>> >> >>> >>> On 25 Sep 2017, at 23:16, HernÃ¡n Morales Durand < >>> hernan.morales(a)gmail.com> wrote: >>> >>> >>> >>> Hi, >>> >>> >>> >>> Guys I have the situation you will recognize in the attached picture: >>> >>> A never-ending recursive computation which generate zillions of >>> >>> pre-debug windows when cmd-dot key is pressed. >>> >>> >>> >>> Is there any setting, or any way to put a monitor to detect that >>> >>> cmd-dot is creating too many windows so will pop-up just one or two? >>> >>> Maybe someone researched this issue, does it makes sense? >>> >>> >>> >>> Cheers, >>> >>> >>> >>> HernÃ¡n >>> >>> <rw.png> >>> >> >>> >> >>> > >>> >>> >> >> >> -- >> >> >> >> 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 <+33%206%2052%2070%2066%2013> >> > > -- 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

Oct. 6, 2017

Re: [Pharo-dev] Never-ending computations and cmd-dot

by HernÃ¡n Morales Durand

Hi Guille 2017-10-03 9:15 GMT-03:00 Guillermo Polito <guillermopolito(a)gmail.com>: > I've been bitten by this dozens of times. > > The problem seems to be that a second UI process is created and thus the > DNU exception is automatically resumed (indefinitely). Executing the > following expression seems to remove the problem: > > UIManager default spawnNewProcess > > Thanks. That expression prevents the recursive exception windows from opening? Or it is a post-mortem measure? So it should be executed at image startup? I will check. > Still, I do not know the cause of it. > > On Wed, Sep 27, 2017 at 4:28 AM, Stephane Ducasse <stepharo.self(a)gmail.com > > wrote: > >> Hi hernan >> >> Indeed it would be nice to have a solution for such case. Now we did >> not look at it. >> >> Stef >> >> On Tue, Sep 26, 2017 at 5:58 AM, HernÃ¡n Morales Durand >> <hernan.morales(a)gmail.com> wrote: >> > Hi Tim, >> > >> > Yes, I am aware of such menu item. However I would like to know if >> > someone is working in a more architectural solution. >> > Because I guess this would imply to hook message sends into the main >> > feedback loop. >> > >> > Cheers, >> > >> > HernÃ¡n >> > >> > >> > 2017-09-25 20:08 GMT-03:00 Tim Mackinnon <tim(a)testit.works>: >> >> Its not quite what you are asking for, but if you right click on one >> of those windows, someone has helpfully added a âclose all windows to >> rightâ option, which does let you rapidly get rid of them. >> >> >> >> Tim >> >> >> >>> On 25 Sep 2017, at 23:16, HernÃ¡n Morales Durand < >> hernan.morales(a)gmail.com> wrote: >> >>> >> >>> Hi, >> >>> >> >>> Guys I have the situation you will recognize in the attached picture: >> >>> A never-ending recursive computation which generate zillions of >> >>> pre-debug windows when cmd-dot key is pressed. >> >>> >> >>> Is there any setting, or any way to put a monitor to detect that >> >>> cmd-dot is creating too many windows so will pop-up just one or two? >> >>> Maybe someone researched this issue, does it makes sense? >> >>> >> >>> Cheers, >> >>> >> >>> HernÃ¡n >> >>> <rw.png> >> >> >> >> >> > >> >> > > > -- > > > > 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 >

Oct. 6, 2017

[Pharo 7.0-dev] Build #172: 20494-update-Epicea-to-version-8-2-5

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #172 was: SUCCESS. The Pull Request #332 was integrated: "20494-update-Epicea-to-version-8-2-5" Pull request url: https://github.com/pharo-project/pharo/pull/332 Issue Url: https://pharo.fogbugz.com/f/cases/20494 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 6, 2017