- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] FileTree/Iceberg and SSDs, change the file format

by Dale Henrichs

Cuis uses a standard chunk file format[1] with a file per package. Given the fact that no two Smalltalk dialects share a common class creation protocol makes simply using chunk file format a non-starter. Squeak uses FileTree. As part of his work on Cypress 2.0 Martin McClure is planning on supporting a file per class disk format in addition to the file per method format and possibly a file per package format. I'm not sure whether Martin is at the point where he is ready to share his plans, but this is a problem that is being worked on and when Martin is ready for feedback he'll publish his spec. Dale [1] https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev/blob/master/Packages/A… On 5/21/17 8:25 AM, Stephan Eggermont wrote: > At the PharoDays I was painfully reminded that SSDs perform really badly when using small files. The Bloc tutorial used a github filetree repo and that has a lot of files. The whole folder is 116 MB in 16K files. Copying that amount of data should not be noticable, taking about a third of a second. With it being in so many files, it took more than half a minute, or a hundred times as long. > > That is too much overhead. How can we improve the file format in a way that keeps the cross-platform exchange advantages and a reasonable way to view diffs and propose small changes using the github web tools? > > Cuis uses a different format with git. How does that compare? What is used in Squeak? > > Stephan >

May 21, 2017

Re: [Pharo-dev] Git, FileTree/Cypress, missing Traits comments

by Dale Henrichs

Looks like Thierry has a nifty solution for Traits in FileTree that doesn't involve methods ... Bob's already your uncle:) Dale On 5/21/17 10:36 AM, Dale Henrichs wrote: > I'm not familiar with Traits and how they have been integrated into > Monticello, but reading comments from the snapshot is pretty wild --- > but I I suppose it works:) > > For FileTree Traits should be added as first class objects ... I > assume that Traits are just regular classes and that the trickery > comes with associating a method in a class with a method from a Trait. > > In Filetree (Cypress 1.0), the first line of an st file is interpreted > as the method protocol and monkeying with the method protocol would be > possible but not transparently portable. The "most recent" Cypress > format (Cypress 1.5) switched from a single line to a 4 line > structured comment[1]. > > Martin McClure is currently working on Cypress2.0 and I believe that > he is proposing that methods also have an attribute dictionary (like > classes [2]), so for Cypress 2.0 Traits methods could be first class > objects ... > > Cypress 2.0 is still a work in process. Cypress 1.0 is widely used, > while Cypress 1.5 is not... > > Sooo, I would suggest that the Cypress 1.5 format could be modified to > accommodate Traits methods ... FileTree already supports 3 or 4 > different disk formats, so FileTree could be updated to support > Cypress 1.5 format and then Bob's your uncle ... > > Dale > > [1]https://github.com/CampSmalltalk/Cypress/wiki#method-file-format > > [2] https://github.com/CampSmalltalk/Cypress/wiki#class-properties > > On 5/20/17 8:12 PM, Ben Coman wrote: >> Is this of concern for Pharo...? "Pull requests on GitHub where the >> Trait comments get removed (because they were not loaded with the >> package in the first place)." >> >> http://forum.world.st/Re-The-Inbox-System-jr-919-mcz-td4941798.html#none >> >> http://forum.world.st/The-Inbox-System-jr-919-mcz-td4933985.html >> >> cheers -ben >> >

May 21, 2017

Re: [Pharo-dev] Git, FileTree/Cypress, missing Traits comments

by Dale Henrichs

I'm not familiar with Traits and how they have been integrated into Monticello, but reading comments from the snapshot is pretty wild --- but I I suppose it works:) For FileTree Traits should be added as first class objects ... I assume that Traits are just regular classes and that the trickery comes with associating a method in a class with a method from a Trait. In Filetree (Cypress 1.0), the first line of an st file is interpreted as the method protocol and monkeying with the method protocol would be possible but not transparently portable. The "most recent" Cypress format (Cypress 1.5) switched from a single line to a 4 line structured comment[1]. Martin McClure is currently working on Cypress2.0 and I believe that he is proposing that methods also have an attribute dictionary (like classes [2]), so for Cypress 2.0 Traits methods could be first class objects ... Cypress 2.0 is still a work in process. Cypress 1.0 is widely used, while Cypress 1.5 is not... Sooo, I would suggest that the Cypress 1.5 format could be modified to accommodate Traits methods ... FileTree already supports 3 or 4 different disk formats, so FileTree could be updated to support Cypress 1.5 format and then Bob's your uncle ... Dale [1]https://github.com/CampSmalltalk/Cypress/wiki#method-file-format [2] https://github.com/CampSmalltalk/Cypress/wiki#class-properties On 5/20/17 8:12 PM, Ben Coman wrote: > Is this of concern for Pharo...? "Pull requests on GitHub where the > Trait comments get removed (because they were not loaded with the > package in the first place)." > > http://forum.world.st/Re-The-Inbox-System-jr-919-mcz-td4941798.html#none > > http://forum.world.st/The-Inbox-System-jr-919-mcz-td4933985.html > > cheers -ben >

May 21, 2017

Re: [Pharo-dev] FileTree/Iceberg and SSDs, change the file format

by philippe.back＠highoctane.be

There is the same kind of issues with Hadoop but the block size is 128MB. So, lots of small files give the same issue. This is solved by having HAR files (Hadoop Archive) that contain the files. The haddop filesystem is usually able to access the har contents somewhat transparently from userland. But I guess that libgit will not be too cooperative. We can also look into how to mount such an archive as a filesystem. Phil Le 21 mai 2017 17:27, "Stephan Eggermont" <stephan(a)stack.nl> a Ã©crit : At the PharoDays I was painfully reminded that SSDs perform really badly when using small files. The Bloc tutorial used a github filetree repo and that has a lot of files. The whole folder is 116 MB in 16K files. Copying that amount of data should not be noticable, taking about a third of a second. With it being in so many files, it took more than half a minute, or a hundred times as long. That is too much overhead. How can we improve the file format in a way that keeps the cross-platform exchange advantages and a reasonable way to view diffs and propose small changes using the github web tools? Cuis uses a different format with git. How does that compare? What is used in Squeak? Stephan

May 21, 2017

60494 Red-pane-of-death when sources file missing

by Ben Coman

We must be getting close to Pharo 6 Release. Due to missing PharoV60.soruces file, image 60494 get a red-pane-of-death in class pane. Even though the release would bypass this by including the file, we should be more robust to the missing sources file. Hopefully this fix can make it last minute into the release... https://pharo.fogbugz.com/f/cases/20074/Red-pane-of-death-when-sources-file… cheers -ben

May 21, 2017

FileTree/Iceberg and SSDs, change the file format

by Stephan Eggermont

At the PharoDays I was painfully reminded that SSDs perform really badly when using small files. The Bloc tutorial used a github filetree repo and that has a lot of files. The whole folder is 116 MB in 16K files. Copying that amount of data should not be noticable, taking about a third of a second. With it being in so many files, it took more than half a minute, or a hundred times as long. That is too much overhead. How can we improve the file format in a way that keeps the cross-platform exchange advantages and a reasonable way to view diffs and propose small changes using the github web tools? Cuis uses a different format with git. How does that compare? What is used in Squeak? Stephan

May 21, 2017

Re: [Pharo-dev] Git, FileTree/Cypress, missing Traits comments

by Ben Coman

Le 21/05/2017 Ã 05:12, Ben Coman a Ã©crit : > Is this of concern for Pharo...? "Pull requests on GitHub where the > Trait comments get removed (because they were not loaded with the > package in the first place)." > > http://forum.world.st/Re-The-Inbox-System-jr-919-mcz-td4941798.html#none > > http://forum.world.st/The-Inbox-System-jr-919-mcz-td4933985.html > > cheers -ben > > On Sun, May 21, 2017 at 5:12 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Hi Ben, > > There is two Traits tests in the FileTree repository, and they pass (both > under filetree and under gitfiletree) even if I notice that you can load > the test package fine, but you get a DNU when browsing that package from > the test repository inspector. > > The tests classes are MCFileTreeLoaderTraitsTest and > MCGitFileTreeLoaderTraitsTest, and the test repository is at: > https://github.com/dalehenrich/filetree/tree/pharo5.0/tests/ > testRepositories/traits. > > Would you be interested in checking if the Squeak bug applies, adding an > additional test to confirm or infirm with a pull request? > > I guess I could if no one else picks it up, but I don't think I'm best placed to do it. I've never used FileTree nor Traits, so I'm not sure where to look for the Trait's comment (is this just a class comment on a subclass of Trait) - and given the move to Iceberg/Git, I'm not sure the FileTree/Git learning curve is worth it for me. I was hoping someone familiar with both or one of them could at least confirm the problem first. cheers -ben

May 21, 2017

Re: [Pharo-dev] Iceberg ?

by Myroslava Romaniuk

Well it is a bit different with iceberg. Have a look at the FAQ <https://github.com/pharo-vcs/iceberg#FAQ> section here, and here <https://help.github.com/articles/connecting-to-github-with-ssh/>'s a general guide regarding connecting github with ssh. Let me know if this helps On 21 May 2017 at 12:35, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > yes and I should publish it on my git account? > I use git daily so I do not get why I should do something different with > iceberg/ > > On Sun, May 21, 2017 at 11:33 AM, Myroslava Romaniuk <romaniuk(a)ucu.edu.ua> > wrote: > >> Have you got a ssh key? >> >> On 21 May 2017 at 12:31, Stephane Ducasse <stepharo.self(a)gmail.com> >> wrote: >> >>> On mac with latest pharo vm and latest pharo 60 >>> Metacello new >>> baseline: 'Bloc'; >>> repository: 'github://pharo-graphics/Bloc/src'; >>> load:#core >>> >>> Then I got LGit_GIT_ERROR no ssh-agent suitable credentials found >>> >>> >>> >> >> >> -- >> Ð Ð¿Ð¾Ð²Ð°Ð³Ð¾Ñ, >> ÐÐ¸ÑÐ¾ÑÐ»Ð°Ð²Ð° Ð Ð¾Ð¼Ð°Ð½ÑÐº. >> > > -- Ð Ð¿Ð¾Ð²Ð°Ð³Ð¾Ñ, ÐÐ¸ÑÐ¾ÑÐ»Ð°Ð²Ð° Ð Ð¾Ð¼Ð°Ð½ÑÐº.

May 21, 2017

Re: [Pharo-dev] Iceberg ?

by Stephane Ducasse

yes and I should publish it on my git account? I use git daily so I do not get why I should do something different with iceberg/ On Sun, May 21, 2017 at 11:33 AM, Myroslava Romaniuk <romaniuk(a)ucu.edu.ua> wrote: > Have you got a ssh key? > > On 21 May 2017 at 12:31, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > >> On mac with latest pharo vm and latest pharo 60 >> Metacello new >> baseline: 'Bloc'; >> repository: 'github://pharo-graphics/Bloc/src'; >> load:#core >> >> Then I got LGit_GIT_ERROR no ssh-agent suitable credentials found >> >> >> > > > -- > Ð Ð¿Ð¾Ð²Ð°Ð³Ð¾Ñ, > ÐÐ¸ÑÐ¾ÑÐ»Ð°Ð²Ð° Ð Ð¾Ð¼Ð°Ð½ÑÐº. >

May 21, 2017

Re: [Pharo-dev] Iceberg ?

by Myroslava Romaniuk

Have you got a ssh key? On 21 May 2017 at 12:31, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > On mac with latest pharo vm and latest pharo 60 > Metacello new > baseline: 'Bloc'; > repository: 'github://pharo-graphics/Bloc/src'; > load:#core > > Then I got LGit_GIT_ERROR no ssh-agent suitable credentials found > > > -- Ð Ð¿Ð¾Ð²Ð°Ð³Ð¾Ñ, ÐÐ¸ÑÐ¾ÑÐ»Ð°Ð²Ð° Ð Ð¾Ð¼Ð°Ð½ÑÐº.

May 21, 2017