November 2019 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Pharo 7 Release Update

by Sabine Manaa

I am happy about this, too. Thank you! I just tested it with my config and can confirm that zinc loads correct. But the other problem (I remember other had this, too) remains: after loading, I have an empty debugger with "Instances of Process did not understand #isValid" Anyone having this, too? I can close this debugger and everything seems fine but I just want to report. Sabine Am Di., 5. Nov. 2019 um 08:43 Uhr schrieb Sven Van Caekenberghe < sven(a)stfx.eu>: > Hi, > > As reported (by Jonathan and checked by me), the launcher now creates an > Pharo 7.0 images from version Pharo7.0.4 build: 172, commit: ecc855d. This > build correctly loads the Zinc baseline ! > > This is very good news. Thanks again Pablo. > > Now this version has to be released so that it is served by the ZeroConf > tools (get.pharo.org) which is a manual process, IIUC. > > Do we have to go to 7.0.5 ? > > Can someone do the necessary steps please ? > > Sven > > > >

Nov. 5, 2019

[Pharo 8.0] Build #937: FileSystem>>copyFileAndDelete:to: don't raise a FileDoesNotExistException if the destination doesn't exist

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

There is a new Pharo build available! The status of the build #937 was: FAILURE. The Pull Request #5041 was integrated: "FileSystem>>copyFileAndDelete:to: don't raise a FileDoesNotExistException if the destination doesn't exist" Pull request url: https://github.com/pharo-project/pharo/pull/5041 Issue Url: https://github.com/pharo-project/pharo/issues/copyFileAndDeleteto Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 5, 2019

Pharo 7 Release Update

by Sven Van Caekenberghe

Hi, As reported (by Jonathan and checked by me), the launcher now creates an Pharo 7.0 images from version Pharo7.0.4 build: 172, commit: ecc855d. This build correctly loads the Zinc baseline ! This is very good news. Thanks again Pablo. Now this version has to be released so that it is served by the ZeroConf tools (get.pharo.org) which is a manual process, IIUC. Do we have to go to 7.0.5 ? Can someone do the necessary steps please ? Sven

Nov. 5, 2019

[Pharo 8.0] Build #936: close all windows like this

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

There is a new Pharo build available! The status of the build #936 was: SUCCESS. The Pull Request #5046 was integrated: "close all windows like this" Pull request url: https://github.com/pharo-project/pharo/pull/5046 Issue Url: https://github.com/pharo-project/pharo/issues/toolbar Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 4, 2019

[Pharo 8.0] Build #935: 4829-SugsNautilusContext-can-be-removed

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

There is a new Pharo build available! The status of the build #935 was: SUCCESS. The Pull Request #5049 was integrated: "4829-SugsNautilusContext-can-be-removed" Pull request url: https://github.com/pharo-project/pharo/pull/5049 Issue Url: https://github.com/pharo-project/pharo/issues/4829 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 4, 2019

[Pharo 8.0] Build #934: Cleanup: #wantsRecompilationProgressReported

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

There is a new Pharo build available! The status of the build #934 was: FAILURE. The Pull Request #5048 was integrated: "Cleanup: #wantsRecompilationProgressReported" Pull request url: https://github.com/pharo-project/pharo/pull/5048 Issue Url: https://github.com/pharo-project/pharo/issues/wantsRecompilationProgressRep… Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 4, 2019

[Pharo 8.0] Build #933: Completion: use #hasEntries instead of isEmpty/notEmpty

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

There is a new Pharo build available! The status of the build #933 was: SUCCESS. The Pull Request #5047 was integrated: "Completion: use #hasEntries instead of isEmpty/notEmpty" Pull request url: https://github.com/pharo-project/pharo/pull/5047 Issue Url: https://github.com/pharo-project/pharo/issues/CompletionHasEntries Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 4, 2019

Re: [Pharo-dev] Git URL issues

by Esteban Lorenzano

I made a PR to allow âgenericâ git repositories to be referenced: https://github.com/pharo-vcs/iceberg/pull/1324 <https://github.com/pharo-vcs/iceberg/pull/1324> Butâ¦ problem is more complicated than you may think: Metacello âvanillaâ relies on download a zip file with the sources, it cannot have a âgenericâ way to act. This means the PR will work just if you use iceberg. And maybe you do not want to declare your baselines relying on iceberg. In that case, you have just one workaround possible: 1) clone locally the remove private sources outside the image. 2) load them using plain metacello and filetree://. 3) âlockâ those repositories. Then you can run your installation. Esteban > On 4 Nov 2019, at 12:52, Norbert Hartl <norbert(a)hartl.name> wrote: > > > >> Am 01.11.2019 um 17:44 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >> >> >> >>> On 31 Oct 2019, at 12:18, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>> >>> >>>> Am 31.10.2019 um 12:12 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >>>> >>>> >>>> >>>>> On 25 Oct 2019, at 14:49, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>>> >>>>> How do you build/deploy non-public production code using the command line ? >>>> >>>> I just learned about the following technique: >>>> >>>> Using SSH agent forwarding >>>> >>>> https://developer.github.com/v3/guides/using-ssh-agent-forwarding/ >>>> >>>> This certainly makes using certificates on production servers much easier since you do no longer have to manage or install special ones on the deployment servers, you can just use your standard developer certificates. >>>> >>> That is quite late :P I always use this as it also chains through all the machins you log in. We use jenkins for building our software there it does not work. We just have a deployment key for that. That is a key pair without passphrase that is registered in the git repository and installed on the jenkins server. >>> >>> Norbert >> >> Indeed, the SSH forwarding cannot be used for independent CI builds. >> >> I am curious though: how do you do the initial checkout (clone) from your private repository ? Using regular git command line tools or using Iceberg/Metacello ? >> >> If the latter, how do you specify your URL, exactly ? >> >> The first case works for me too, using a gitlocal:// URL, but that is cheating a bit, I feel like we should be able to do this directly in Pharo. > > If checking out from private repo your problem is as deep as you reference private repos. My project (1) is in a private repository, it contains a baseline that references a project in a private repository (2) and this references a project in a private repo (3). > > * Project (1) is checked out by jenkins. I have a deployment key pair without passphrase where the public key is registered in the bitbucket project and the private key is deployed on jenkins. > > * I try to avoid iceberg as much as possible for deployment builds because later I want to have an image without iceberg. And it is not reliable to use iceberg because metacello won't update git repos automatically and the odds are high that you load old content. So I load the project with the eval commandline handler with > > Metacello new > repository: 'filetree://source <filetree://source>'; > baseline â¦ > â¦ > > * In order to load the private projects in the the baseline of the main project I run a script before build that hacks the image in a way that > > MCBitbucketRepository compile: 'httpsUrl > ^ ''https://USER:PASS@bitbucket.org/'', projectPath, ''.git'' <https://USER:PASS@bitbucket.org/'',%20projectPath,%20''.git''>'. > > MCBitbucketRepository compile: 'projectZipUrlFor: projectPath versionString: versionString > ^ ''https://USER:PASS@bitbucket.org/'' , projectPath , ''/get/'' , versionString , ''.zip'' <https://USER:PASS@bitbucket.org/''%20,%20projectPath%20,%20''/get/''%20,%20versionString%20,%20''.zip''>'. > > MCBitbucketRepository class compile: 'projectZipUrlFor: projectPath versionString: versionString > ^ ''https://USER:PASS@bitbucket.org/'' , projectPath , ''/get/'' , versionString , ''.zip'' <https://USER:PASS@bitbucket.org/''%20,%20projectPath%20,%20''/get/''%20,%20versionString%20,%20''.zip''>'. > > This works only because all private projects are on bitbucket and no public one. > > * Project (3) I made public because I did not see how to make that work > > Hope this helps. I feel this to be far too complicated. Together with the confusion between pharo5/pharo6/pharo7 with iceberg, tonel and iceberg and/or tonel support killed two weeks of my time at least. So I would welcome if there would be a better way to manage credentials > > Norbert

Nov. 4, 2019

Re: [Pharo-dev] Git URL issues

by Norbert Hartl

> Am 01.11.2019 um 17:44 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > > >> On 31 Oct 2019, at 12:18, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> >> >>> Am 31.10.2019 um 12:12 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >>> >>> >>> >>>> On 25 Oct 2019, at 14:49, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> >>>> How do you build/deploy non-public production code using the command line ? >>> >>> I just learned about the following technique: >>> >>> Using SSH agent forwarding >>> >>> https://developer.github.com/v3/guides/using-ssh-agent-forwarding/ >>> >>> This certainly makes using certificates on production servers much easier since you do no longer have to manage or install special ones on the deployment servers, you can just use your standard developer certificates. >>> >> That is quite late :P I always use this as it also chains through all the machins you log in. We use jenkins for building our software there it does not work. We just have a deployment key for that. That is a key pair without passphrase that is registered in the git repository and installed on the jenkins server. >> >> Norbert > > Indeed, the SSH forwarding cannot be used for independent CI builds. > > I am curious though: how do you do the initial checkout (clone) from your private repository ? Using regular git command line tools or using Iceberg/Metacello ? > > If the latter, how do you specify your URL, exactly ? > > The first case works for me too, using a gitlocal:// URL, but that is cheating a bit, I feel like we should be able to do this directly in Pharo. If checking out from private repo your problem is as deep as you reference private repos. My project (1) is in a private repository, it contains a baseline that references a project in a private repository (2) and this references a project in a private repo (3). * Project (1) is checked out by jenkins. I have a deployment key pair without passphrase where the public key is registered in the bitbucket project and the private key is deployed on jenkins. * I try to avoid iceberg as much as possible for deployment builds because later I want to have an image without iceberg. And it is not reliable to use iceberg because metacello won't update git repos automatically and the odds are high that you load old content. So I load the project with the eval commandline handler with Metacello new repository: 'filetree://source'; baseline â¦ â¦ * In order to load the private projects in the the baseline of the main project I run a script before build that hacks the image in a way that MCBitbucketRepository compile: 'httpsUrl ^ ''https://USER:PASS@bitbucket.org/'', projectPath, ''.git'''. MCBitbucketRepository compile: 'projectZipUrlFor: projectPath versionString: versionString ^ ''https://USER:PASS@bitbucket.org/'' , projectPath , ''/get/'' , versionString , ''.zip'''. MCBitbucketRepository class compile: 'projectZipUrlFor: projectPath versionString: versionString ^ ''https://USER:PASS@bitbucket.org/'' , projectPath , ''/get/'' , versionString , ''.zip'''. This works only because all private projects are on bitbucket and no public one. * Project (3) I made public because I did not see how to make that work Hope this helps. I feel this to be far too complicated. Together with the confusion between pharo5/pharo6/pharo7 with iceberg, tonel and iceberg and/or tonel support killed two weeks of my time at least. So I would welcome if there would be a better way to manage credentials Norbert

Nov. 4, 2019

Horizontal scrolling in FastTable

by Danil Osipchuk

Hi all I wonder what is happening to the horizontal scrolling in FastTable, the stub is there for years (I've checked the latest 8.0). I need it rather badly, could someone advise what is the hindrance there? I would try doing it myself, but I've never was doing much of UI programming and only recently returned to Pharo again, so have to catch up (a lot of things changed for good). How difficult would be to adopt vertical scrolling approach (which seems to be the same problem already solved to layperson ) horizontalScrollBarValue: aNumber trialHSB ifNotNil: [ self inform: 'FTTableMorph>>#horizontalScrollBarValue: ', aNumber printString , String cr, 'Does nothing yet.' , String cr, 'Need some advise here.' ]. regards, Danil

Nov. 4, 2019