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

Re: [Pharo-dev] [OpenSmalltalk/opensmalltalk-vm] Crashes while typing on macOS Sierra (#141)

by Eliot Miranda

Hi Tobias, > On Feb 6, 2018, at 4:43 AM, Tobias Pape <notifications(a)github.com> wrote: > > Closed #141 via ecd41af. > thank you very much for this fix! Lots of people have been hurting from this. > â > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub, or mute the thread. >

Feb. 6, 2018

Re: [Pharo-dev] VMs build process restored

by Cyril Ferlicot D.

Le 06/02/2018 Ã 17:58, Esteban Lorenzano a Ã©critÂ : > (it was broken since december) > > Which means latest vm versions are latest builds from OSVM: > > 64bit > > â¢ http://files.pharo.org/get-files/70/pharo64-mac-latest.zip > â¢ http://files.pharo.org/get-files/70/pharo64-linux-threaded-latest.zip > â¢ http://files.pharo.org/get-files/70/pharo64-linux-latest.zip > â¢ http://files.pharo.org/get-files/70/pharo64-win-latest.zip > 32bit > > â¢ http://files.pharo.org/get-files/70/pharo-linux-threaded-latest.zip > â¢ http://files.pharo.org/get-files/70/pharo-linux-latest.zip > â¢ http://files.pharo.org/get-files/70/pharo-mac-latest.zip > â¢ http://files.pharo.org/get-files/70/pharo-win-latest.zip > > Hints > > â¢ MacOS VMs now are signed! This should fix a lot of problems we had before. > â¢ Please take note that win64 build lacks all library dependencies, and many things will not work (working on that). > Thanks to Fabio to help me put all the pieces together. > > > cheers, > Esteban > Thank you very much! Is it planned to release some of those vm as stable for Pharo 6.1 if they fix the metacello loading crash in linux 64bits? -- Cyril Ferlicot https://ferlicot.fr

Feb. 6, 2018

Which was the way to tag methods so that Spotter think they are examples?

by Mariano Martinez Peck

I remember that Spotter was able to detect that some methods were examples and display them differently. Do I remember correctly? I guess some pragma? Anyway, appreciated any hint. Cheers, -- Mariano http://marianopeck.wordpress.com

Feb. 6, 2018

Re: [Pharo-dev] VMs build process restored

by ClÃ©ment Bera

Thank you very much Esteban, Thanks Fabio. On Tue, Feb 6, 2018 at 5:58 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > (it was broken since december) > > Which means latest vm versions are latest builds from OSVM: > > 64bit > > â¢ http://files.pharo.org/get-files/70/pharo64-mac-latest.zip > â¢ http://files.pharo.org/get-files/70/pharo64-linux- > threaded-latest.zip > â¢ http://files.pharo.org/get-files/70/pharo64-linux-latest.zip > â¢ http://files.pharo.org/get-files/70/pharo64-win-latest.zip > 32bit > > â¢ http://files.pharo.org/get-files/70/pharo-linux-threaded- > latest.zip > â¢ http://files.pharo.org/get-files/70/pharo-linux-latest.zip > â¢ http://files.pharo.org/get-files/70/pharo-mac-latest.zip > â¢ http://files.pharo.org/get-files/70/pharo-win-latest.zip > > Hints > > â¢ MacOS VMs now are signed! This should fix a lot of problems we > had before. > â¢ Please take note that win64 build lacks all library > dependencies, and many things will not work (working on that). > Thanks to Fabio to help me put all the pieces together. > > > cheers, > Esteban > -- ClÃ©ment BÃ©ra Pharo consortium engineer https://clementbera.wordpress.com/ BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq

Feb. 6, 2018

VMs build process restored

by Esteban Lorenzano

(it was broken since december) Which means latest vm versions are latest builds from OSVM: 64bit â¢ http://files.pharo.org/get-files/70/pharo64-mac-latest.zip â¢ http://files.pharo.org/get-files/70/pharo64-linux-threaded-latest.zip â¢ http://files.pharo.org/get-files/70/pharo64-linux-latest.zip â¢ http://files.pharo.org/get-files/70/pharo64-win-latest.zip 32bit â¢ http://files.pharo.org/get-files/70/pharo-linux-threaded-latest.zip â¢ http://files.pharo.org/get-files/70/pharo-linux-latest.zip â¢ http://files.pharo.org/get-files/70/pharo-mac-latest.zip â¢ http://files.pharo.org/get-files/70/pharo-win-latest.zip Hints â¢ MacOS VMs now are signed! This should fix a lot of problems we had before. â¢ Please take note that win64 build lacks all library dependencies, and many things will not work (working on that). Thanks to Fabio to help me put all the pieces together. cheers, Esteban

Feb. 6, 2018

[Pharo 7.0-dev] Build #506: 21124 ffi should work without the sources

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

There is a new Pharo build available! The status of the build #506 was: FAILURE. The Pull Request #750 was integrated: "21124 ffi should work without the sources" Pull request url: https://github.com/pharo-project/pharo/pull/750 Issue Url: https://pharo.fogbugz.com/f/cases/21124 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 6, 2018

[Pharo 7.0-dev] Build #505: 21242-improve-includesMethod

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

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

Feb. 6, 2018

Re: [Pharo-dev] Reviewing Changes ?

by Marcus Denker

another thing I was thinking about is to just do to do âliveâ youtube sessionsâ¦ e.g. if I do a tiny fix, to just stream the whole thing, from start to finish. (but then, I guess the tech talk will be just that) > On 6 Feb 2018, at 13:42, Tim Mackinnon <tim(a)testit.works> wrote: > > As an idea - might someone do a tech talk on this and take us through some scenarios? Every time I think about how to help - I read the pain here and shy away from it (yes the mental barrier is mine, and also alack of time to really get to grips with it) - but I was thinking that it someone walked through it - it might make it all much less scary. > > Tim > > >> On 5 Feb 2018, at 15:57, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Ah, Esteban's PR review tool is exactly what I was looking for. It works ! >> >> Still, please, please (Pavel) write down somewhere what you just explained to me, else it will eventually be lost. >> >> Docs needed >> >> (1) contribute to Pharo (we have that) >> (2) keep in sync once you have done (1) (we have that, but not about image side) >> (3) review pull requests of others (new, this email to start) >> >> Anyway, thanks for the answers. >> >>> On 5 Feb 2018, at 15:10, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: >>> >>> 2018-02-05 13:54 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >>>> Hi, >>>> >>>> With pull requests, it is relatively easy to see what changed in GitHub. >>>> >>>> Eg. Marcus' latest fix: >>>> >>>> https://github.com/pharo-project/pharo/pull/797 >>>> >>>> shows 6 files/classes changed, reasonably readable diff. >>>> >>>> How does one review such a PR in an image, to test it out ? >>> >>> The easiest way is to download an image bootstrapped from that PR. >>> Next to the commits you have a validation status (red cross here), >>> click on it, go to "Artifacts" and then download the image >>> (bootstrap-cache/Pharo7.0-32bit-6ccdd62.zip) >>> >>> Esteban did a Pull request review tool: >>> >>> - register your local Pharo repository copy to Iceberg >>> - in the "Remotes" open context menu on the pharo-project remote (not >>> origin, which is probably our fork) >>> - GitHub - Review pull requests... >>> - open context menu on an issue and select "Review pull request..." >>> - select the newest commit and check changes >>> - to test it locally, do "Merge into image", answer "Yes" >>> >>>> Has someone written a guide on how to do this best/most-easily ? >>> >>> No idea, but Esteban presented that several times on ESUG and other places. >>> >>>> How is/can this be related to contributing ? >>> >>> If you want to use the PR review tool, you should have own fork and >>> local repository - the same for contributing >>> >>> If you then want to propose a modification fo the PR, you already have >>> a branch from the PR merging. >>> - do your change and synchronize the repository so your branch will be >>> present on your fork. >>> - then go to "Remotes" tab, open context menu on "MarcusDenker" remote >>> (it will be created during merging of the PR into your image) and then >>> do pull request. >>> - in Head select your fork and your issue branch name >>> - in Base select Marcus/Denker/pharo and the issue branch name >>> - click on Create Pull request >>> >>> It will create a PR on the repository that Marcus has. Like >>> https://github.com/MarcusDenker/pharo/pull/1 >>> When he will merge it, his PR to on Pharo repository will be updated >>> automatically. >>> >>> Cheers, >>> -- Pavel >>> >>>> >>>> Sven >> >> > >

Feb. 6, 2018

[Pharo 7.0-dev] Build #504: 21243-add-testReifyMethodArgsByNameBefore

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

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

Feb. 6, 2018

How to force a BaselineOf to load ?

by Sven Van Caekenberghe

Hi, I have a Pharo 4 (#40627) image that already contains P3. Now I want to update P3, without completely rebuilding this image from scratch. It seems as if an expression like Metacello new baseline: 'P3'; repository: 'github://svenvc/P3'; load. executed like $ ../bin/pharo build-trackit.image eval --save "Metacello new baseline: 'P3'; repository: 'github://svenvc/P3'; load" does not really reload the code. How can I force it to (re)load ? Thx, Sven

Feb. 6, 2018