June 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Ann] Iceberg v1.1.0

by Sean P. DeNigris

Guillermo Polito wrote >> I also wonder if we are trying to be too clever with how you specify a >> Gitlab/Github project > > Maybe... but for that you have the last option "Clone remote repository" > that allows you to just paste a url. This issue has come up a few times already. Does anyone have a use case for the custom Gitlab/Github forms? If not, maybe it would be simpler for everyone to remove them and use the generic oneâ¦ ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

June 13, 2018

Re: [Pharo-dev] [Ann] Iceberg v1.1.0

by Guillermo Polito

On Wed, Jun 13, 2018 at 1:40 PM Tim Mackinnon <tim(a)testit.works> wrote: > I have installed it fine now - I think the message is less ambiguous if > the latest Pharo, is called the âlatest Pharo 7â - thats where my confusion > was. > > Is it worth reporting any bugs with this version in 6.1? I got an error > dialog that was telling me about the project I was trying to load already > existing on my disk - however the window is too small and so you donât see > that there is a Debug/Ignore button way off to the right (you have to > stretch the dialog to see them). > Nope, that version is not maintained anymore... > > I also wonder if we are trying to be too clever with how you specify a > Gitlab/Github project - both those sites have a little button you click to > copy the full url of the project you want to clone - we are now asking > people to not use that, but instead to copy the name of the project (which > is typically the title Text above that url and copy button). This is very > different from how every tool I use works and is a bit confusing. > Maybe... but for that you have the last option "Clone remote repository" that allows you to just paste a url. > Tim > > > On 13 Jun 2018, at 12:13, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> > wrote: > > > > On 13/06/2018 12:57, Tim Mackinnon wrote: > >> Hi Iâm a bit confused by what is described below - when it says "This is > >> already in latest Pharo build. If you want to try it in a Pharo 6.1 â¦.â > >> - does that mean its already in the latest Pharo 7 (emphasis on 7?) > >> build (and I can see it in Pharo 7) - but the latest 6.1 build doesnât > >> have it and you must follow the steps you described? > >> > > > > Hi! > > > > Each time an Iceberg stable version is released, it is integrated to > > Pharo 7. (Usually, it's available the next day the time to do the PR, > > test it, integrate it and build the new version) > > > > Pharo 6.1 is still at the v0.6 of Iceberg. IIUC, thi is mostly because > > the new UI depends on a lot of changes from Pharo 7 and backporting it > > would mean backport too many changes. The goal is to keep Pharo 6.1 as > > stable as possible. > > > > So the steps to update yourself Iceberg to v1.? is for Pharo 6 only. > > > >> I initially read it to mean that new Pharo 6.1 builds would > >> automatically get it - but that doesnât seem to be the case? > >> > >> Tim > >> > > > > > > -- > > 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

June 13, 2018

Re: [Pharo-dev] [Ann] Iceberg v1.1.0

by Tim Mackinnon

I have installed it fine now - I think the message is less ambiguous if the latest Pharo, is called the âlatest Pharo 7â - thats where my confusion was. Is it worth reporting any bugs with this version in 6.1? I got an error dialog that was telling me about the project I was trying to load already existing on my disk - however the window is too small and so you donât see that there is a Debug/Ignore button way off to the right (you have to stretch the dialog to see them). I also wonder if we are trying to be too clever with how you specify a Gitlab/Github project - both those sites have a little button you click to copy the full url of the project you want to clone - we are now asking people to not use that, but instead to copy the name of the project (which is typically the title Text above that url and copy button). This is very different from how every tool I use works and is a bit confusing. Tim > On 13 Jun 2018, at 12:13, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > On 13/06/2018 12:57, Tim Mackinnon wrote: >> Hi Iâm a bit confused by what is described below - when it says "This is >> already in latest Pharo build. If you want to try it in a Pharo 6.1 â¦.â >> - does that mean its already in the latest Pharo 7 (emphasis on 7?) >> build (and I can see it in Pharo 7) - but the latest 6.1 build doesnât >> have it and you must follow the steps you described? >> > > Hi! > > Each time an Iceberg stable version is released, it is integrated to > Pharo 7. (Usually, it's available the next day the time to do the PR, > test it, integrate it and build the new version) > > Pharo 6.1 is still at the v0.6 of Iceberg. IIUC, thi is mostly because > the new UI depends on a lot of changes from Pharo 7 and backporting it > would mean backport too many changes. The goal is to keep Pharo 6.1 as > stable as possible. > > So the steps to update yourself Iceberg to v1.? is for Pharo 6 only. > >> I initially read it to mean that new Pharo 6.1 builds would >> automatically get it - but that doesnât seem to be the case? >> >> Tim >> > > > -- > Cyril Ferlicot > https://ferlicot.fr >

June 13, 2018

Re: [Pharo-dev] [Ann] Iceberg v1.1.0

by Guillermo Polito

On Wed, Jun 13, 2018 at 1:13 PM Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > On 13/06/2018 12:57, Tim Mackinnon wrote: > > Hi Iâm a bit confused by what is described below - when it says "This is > > already in latest Pharo build. If you want to try it in a Pharo 6.1 â¦.â > > - does that mean its already in the latest Pharo 7 (emphasis on 7?) > > build (and I can see it in Pharo 7) - but the latest 6.1 build doesnât > > have it and you must follow the steps you described? > > > > Hi! > > Each time an Iceberg stable version is released, it is integrated to > Pharo 7. (Usually, it's available the next day the time to do the PR, > test it, integrate it and build the new version) > > Pharo 6.1 is still at the v0.6 of Iceberg. IIUC, thi is mostly because > the new UI depends on a lot of changes from Pharo 7 and backporting it > would mean backport too many changes. The goal is to keep Pharo 6.1 as > stable as possible. > Actually, the main reason is that Metacello integration has some different semantics that would bother people relying on the current behaviour. Ideally, we would like to have a Pharo6.2, but that means a lot of work infrastructure-wise (build servers, file server, zeroconf...). > So the steps to update yourself Iceberg to v1.? is for Pharo 6 only. > > > I initially read it to mean that new Pharo 6.1 builds would > > automatically get it - but that doesnât seem to be the case? > > > > Tim > > > > > -- > 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

June 13, 2018

Re: [Pharo-dev] [Ann] Iceberg v1.1.0

by Cyril Ferlicot D.

On 13/06/2018 12:57, Tim Mackinnon wrote: > Hi Iâm a bit confused by what is described below - when it says "This is > already in latest Pharo build. If you want to try it in a Pharo 6.1 â¦.â > - does that mean its already in the latest Pharo 7 (emphasis on 7?) > build (and I can see it in Pharo 7) - but the latest 6.1 build doesnât > have it and you must follow the steps you described? > Hi! Each time an Iceberg stable version is released, it is integrated to Pharo 7. (Usually, it's available the next day the time to do the PR, test it, integrate it and build the new version) Pharo 6.1 is still at the v0.6 of Iceberg. IIUC, thi is mostly because the new UI depends on a lot of changes from Pharo 7 and backporting it would mean backport too many changes. The goal is to keep Pharo 6.1 as stable as possible. So the steps to update yourself Iceberg to v1.? is for Pharo 6 only. > I initially read it to mean that new Pharo 6.1 builds would > automatically get it - but that doesnât seem to be the case? > > Tim > -- Cyril Ferlicot https://ferlicot.fr

June 13, 2018

Re: [Pharo-dev] [Ann] Iceberg v1.1.0

by Tim Mackinnon

Hi Iâm a bit confused by what is described below - when it says "This is already in latest Pharo build. If you want to try it in a Pharo 6.1 â¦.â - does that mean its already in the latest Pharo 7 (emphasis on 7?) build (and I can see it in Pharo 7) - but the latest 6.1 build doesnât have it and you must follow the steps you described? I initially read it to mean that new Pharo 6.1 builds would automatically get it - but that doesnât seem to be the case? Tim > On 11 Jun 2018, at 22:04, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > > > On Mon, Jun 11, 2018 at 7:23 PM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com <mailto:hernan.morales@gmail.com>> wrote: > Hi Guille, > > Thank you for the update. > Can this be installed in Pharo 6.1? How? > > This is already in latest Pharo build. If you want to try it in a Pharo 6.1 (I recommend to do it in a clean image), you can follow the instructions in the README > > https://github.com/pharo-vcs/iceberg#for-pharo-61 <https://github.com/pharo-vcs/iceberg#for-pharo-61> > > Those instructions will unload iceberg and install the latest 1.* version > > It was tested on Windows? > > I did not do it personally, but I know Cyril is using it in windows successfully for a couple of months already. > He's even using it to contribute to Pharo and Iceberg itself from windows. > > I'd like to have the tests running on windows, but for that we need OSSubprocess running on windows... (Or maybe depending on ProcessWrapper is a compromise solution?). If someone would like to help on that front, making use of ProcessWrapper in the tests should not be difficult (it was done before but that code rot because of the lack of CI in the past...) > > > Cheers, > > HernÃ¡n > > > 2018-06-11 14:04 GMT-03:00 Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>>: > > Time for the weekly Iceberg update. > > Thanks to all brave users, issue reporters and contributors :). > > > > Key changes: we have introduced some tag support, a new credential manager > > to manage keys and passwords per host or repository, a new version of tonel, > > and made a first step towards a simplified contribution to Iceberg by > > listing it as Pharo's repository. > > > > Enjoy, > > Guille in behalf of all Iceberg contributors > > > > Following, the detailed changes log. > > > > New Features > > #842 Adding Credentials Store > > #843 Update Tonel to 1.0.7 > > #823 Iceberg repository should be listed as Pharo's one > > #841 Basic tag support (#372) > > > > Infrastructure > > #787 Add Windows ci with Appveyor (not yet green!) > > > > Enhancements > > #827 Add package dialog has some glitches > > #833 replace #asIcon with #iconNamed: > > #832 Move Iceberg from MostUsedTools to Tools > > #830 Better handling of not github remote urls > > #825 Enhance Migrate to tonel commit message > > #637 Show tag version instead of "Detached HEAD" > > #829 migrate-versions-browser > > > > Bug Fixes > > #835 Compare file definitions by their binary uninterpreted content > > #838 Clone from incorrect github repository fails with DNU > > #826 Pushing to virgin repository raises a DNU > > > > > -- > > 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

June 13, 2018

Re: [Pharo-dev] FileAttributesPlugin: request for comment and testing

by Guillermo Polito

Hi Alistair, This is great! I've overlooked the changes, I don't have much of a remark. Just a question: what would be the semantics of symlinks and character/block files in windows? On Tue, Jun 12, 2018 at 5:45 PM Alistair Grant <akgrant0710(a)gmail.com> wrote: > Hi Esteban, Guille, Marcus, Cyril and Everyone, > > I'm (finally!) almost ready to merge in the FileAttributesPlugin > changes... > > I have one bug to fix in the VM related to file creation, modification > and access times on Windows. > > While I sort that out (and probably lose what remaining hair I have) I > was hoping that a few people could have a look at the PR on linux and / > or Mac - since it is an admittedly big one. > > Note that you can't merge the changes in to an existing image as > Iceberg will attempt to use the file system in the middle of the merge > and fail. (I haven't tested this after the latest refactor, but I expect > that hasn't changed). You'll need to use the image that has been > bootstrapped from the PR (link below). > > > The source code for the plugin is at: > http://smalltalkhub.com/#!/~Alistair/FileAttributesPlugin > > PR: https://github.com/pharo-project/pharo/pull/1529 > > Fogbugz: > - https://pharo.fogbugz.com/f/cases/21368/Integrate-FileAttributesPlugin > - https://pharo.fogbugz.com/f/cases/18279/ > > Images: > > - 32 bit: > https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… > - 64 bit: > https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… > > It requires a recent VM, from May 9 or later (the current stable VM). > > > > What are the changes? > ===================== > > - Fixes FileReference>>isSymlink > Currently it only returns true for a broken symbolic link. > - Adds the ability to retrieve symbolic link attributes. > - Extends the set of file attributes that can be retrieved to all > attributes returned by the libc stat() and lstat() calls. > - Refactors the code to be more efficient. In particular > FileReference>>exists. > > > 1. #isSymlink now works properly on Linux (and it should also work on > MacOS and BSD). > 2. The list of file attributes available from DiskDirectoryEntry now is: > #accessTime (new) > #changeTime (new) > #deviceId (new) > #gid (new) > #inode (new) > #isBlock (new) > #isCharacter (new) > #isExecutable (new) > #isFIFO (new) > #isRegular (new) > #isSocket (new) > #isSymlink (works) > #numberOfHardLinks (new) > #targetFile (new) > #uid (new) > > #creationTime > #exists > #isDirectory > #isFile > #isReadable > #isWritable > #modificationTime > #permissions > #size > 3. FileReference>>exists is faster than before (well, at least on my > linux laptop). This is useful as it is called often. > 4. It is possible to retrieve symbolic link attributes, i.e. all the > attributes listed above plus the target path. > > > The public interface hasn't changed. There are a number of internal > changes to FileSystem. > > As implied above, the changes are all backward compatible (except > the broken #isSymlink), although a couple deserve mention: > > 1. Obviously #isSymlink now answers correctly (previously it would only > answer correctly for a broken link). > 2. Requesting any of the attributes listed above (except #isSymlink) > will return the value of the target path. If the FileReference is to a > broken symbolic link, it will return the attributes of the symbolic > link (keeping existing behaviour). > 3. The attributes of a symbolic link can be retrieved using > FileReference>>symlinkEntry. > > Overall, performance is slightly better than before. Code that accesses a > single attribute through FileReference will be faster than before (it used > to retrieve all supported elements and throw the unused ones away). Code > that needs to access multiple attributes and uses FileSystemDirectoryEntry > can access the new attributes without any additional performance cost. > > > > Rough development timeline > ========================== > > > April 2017: Started development > > May 2017: First working version. I've been using this in my personal > environment since May last year. > > August 2017: Plugin review by Nicolas Cellier (thanks, Nicolas!) > > September 2017 - January 2018 : Plugin review by Eliot Miranda (thanks > Eliot!) > This was very detailed and tidied up parameter checking, error > return codes, making the code simulator friendly, etc. > > November 2017: FileAttributesPlugin added to the VM. > > February 2018: Tidy up Windows specific code, fix error handling in > #creationTime. > > June 2018: Refactored to place primitives in File instead of > FileAttributesPluginPrims (which matched FilePluginPrims). > > > > Testing > ======= > > - As mentioned above I've been using this on a daily basis since May 2017. > Some of the packages I have loaded include: Roassal2, Glorp, > OSSubprocess, NeoCSV, DataFrame. > - Automated tests have been added for the new functionality. > - Additional automated tests have been added for existing functionality. > - All existing tests pass > > > Thanks! > Alistair > > -- 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

June 13, 2018

[Pharo 7.0-dev] Build #1050: 22129-haltIfInsideTest-should-be-removed-leftover-now-called-haltIfTest

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

There is a new Pharo build available! The status of the build #1050 was: FAILURE. The Pull Request #1532 was integrated: "22129-haltIfInsideTest-should-be-removed-leftover-now-called-haltIfTest" Pull request url: https://github.com/pharo-project/pharo/pull/1532 Issue Url: https://pharo.fogbugz.com/f/cases/22129 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 13, 2018

[Pharo 7.0-dev] Build #1049: 22127-SDL2-needs-to-keep-the-screensaver-enabled-by-default

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

There is a new Pharo build available! The status of the build #1049 was: FAILURE. The Pull Request #1531 was integrated: "22127-SDL2-needs-to-keep-the-screensaver-enabled-by-default" Pull request url: https://github.com/pharo-project/pharo/pull/1531 Issue Url: https://pharo.fogbugz.com/f/cases/22127 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 13, 2018

[Pharo 7.0-dev] Build #1048: 22118-Move-and-rename-AthensMorphicGradientPaint

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

There is a new Pharo build available! The status of the build #1048 was: SUCCESS. The Pull Request #1522 was integrated: "22118-Move-and-rename-AthensMorphicGradientPaint" Pull request url: https://github.com/pharo-project/pharo/pull/1522 Issue Url: https://pharo.fogbugz.com/f/cases/22118 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 13, 2018