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

ESUG 2018 Call for Participation

by Stephane Ducasse

Call-for-Presentations 26rd International Smalltalk Joint Conference The ESUG board is pleased to announce that the 26th ESUG conference/summer-school will be held in Cagliari, Italy 10-14 September 2018; with Camp Smalltalk 8-9 September 2018. The conference is co-organized by University of Cagliari and the Agile Group of the faculty of computer science. http://www.esug.org/wiki/pier/Conferences/2018/ This call includes: - Developer Forum - Smalltalk Technology Award - International Workshop http://www.esug.org/wiki/pier/Conferences/2018/International-Workshop-IWST_… - Student Volunteer http://www.esug.org/wiki/pier/Conferences/2018/Student-volunteers You can support the ESUG conference in many different ways: =============================================== - Sponsor the conference. New sponsoring packages are described at http://www.esug.org/wiki/pier/About/BecomeSponsor - Submit a talk, a software or a paper to one of the events. See below. - Attend the conference. We'd like to beat the previous record of attendance. Students can get free registration and hosting if they enrol into the the Student Volunteers program. See below. Developers Forum: International Smalltalk Developers Conference Call For Participation ================ We are looking for YOUR experience on using Smalltalk. You will have 30 min for presentations and 45-60 min for hand-ons tutorial. The list of topics for the normal talks and tutorials includes, but is not limited to the following: -Micro Services, Container, Cloud, Big Data, -XP practices, Development tools, Experience reports -Model driven development, Web development, Team management -Meta-Modeling, Security, New libraries and frameworks -Educational material, Embedded systems and robotics -SOA and Web services, Interaction with other programming languages -Teaching Pearls and Show us Your Business -Show your business 10 min session (Get prepared!!) How to submit? ============ Submissions deadline is 15 of June 2018 Notification of acceptance will be on done on the fly. Pay attention: the places are limited so do not wait till the last minute to apply. Prospective presenters should submit a request to Stephane.Ducasse[at]inria.fr AND USE THE following header [ESUG 2018 Developers] Title: Please follow the template below the email will be automatically processed! Name: Email: Abstract: Bio: Any presentation not respecting this form will be discarded automatically. International Workshop on Smalltalk Technologies ====================================== Read the page: *http://www.esug.org/wiki/pier/Conferences/2018/International-Workshop-IWST_18* Technology Award Competition ======================== The top 3 teams with the most innovative software will receive, respectively, 500 Euros, 300 Euros and 200 Euros during an awards ceremony at the conference. Developers of any Smalltalk-based software are welcome to compete. More information at http://www.esug.org/wiki/pier/Conferences/2018/Innovation-Technology-Awards Student Volunteer Program ===================== If you are a student wanting to attend ESUG, have you considered being a student volunteer? Student volunteers help keep the conference running smoothly; in return, they have free accommodations, while still having most of the time to enjoy the conference. More information at http://www.esug.org/wiki/pier/Conferences/2018/Student-volunteers We hope to see you there and have fun together. -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Feb. 6, 2018

Re: [Pharo-dev] Feedback about "Contribute a Fix to Pharo" (For windows users)

by Stephane Ducasse

HI nicolai about left and right I totally agree and we should change it. Now we should get a new UI for iceberg too. I started to migrate my project for real using Iceberg and it is working (there are still some glitches). We are concerned about usability. So thanks a lot for your feedback. Stef On Sun, Feb 4, 2018 at 11:35 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > H, > > :( > I think the old VM isâ¦ old. > I need to promote new stables but I was waiting still a bit (something I see > I canât do). > > Can you try with the latest vm? > > wget -O- get.pharo.org/vmLatest70 | bash > > On 4 Feb 2018, at 02:34, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > And sometimes I get a debugger: > > <grafik.png> > > > And btw, the diff pane > "Left: working copy / Right: incoming updates" > > This is wrong, the working copy is on the right, no ? > > > > 2018-02-04 2:12 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: >> >> >> >> 2018-02-03 19:54 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >>> >>> >>> >>> On 3 Feb 2018, at 17:09, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> >>> wrote: >>> >>> Hi Nicolai, >>> >>> 2018-02-03 10:42 GMT-03:00 Nicolai Hess <nicolaihess(a)gmail.com>: >>> >>> The setup finally somehow works: >>> >>> I followed the guide at >>> https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo >>> >>> * wget -O- get.pharo.org/70+vm | bash >>> >>> >>> Does not work (windows msys-console) >>> It starts donwloading something but not pharo >>> >>> >>> this is very weird, I will check. >>> >>> >>> I tried to do at seperate steps: >>> Only the image >>> * wget -O- get.pharo.org/70 | bash >>> >>> Works >>> >>> * wget -O- get.pharo.org/vm | bash >>> >>> works, but is the wrong VM I guess, I can not open the image >>> >>> * wget -O- get.pharo.org/vm70 | bash >>> >>> works, seems to load the right vm >>> >>> * ./pharo-ui Pharo.image >>> >>> Starts the vm but complains about : >>> "Pharo cannot write to the changes file named >>> u:\tmp\pharo\Pharo.changes." >>> >>> I am sure the file is writable. >>> >>> The vm reports to be built on aug 27 2017, is this right? >>> >>> >>> I think is this one: >>> >>> >>> https://pharo.fogbugz.com/f/cases/20805/Cannot-write-to-the-changes-file-er… >>> >>> >>> yes, this is a known bug that we need to fix soon. >>> >>> Setting up Iceberg: >>> Yes, need option 2, that is, I use the commandline to clone a repository >>> and >>> add it to iceberg. Cloning from iceberg directly does not work (long file >>> names). >>> >>> >>> that should not be anymore an issue (since we migrated to tonel). >>> but cloning in disk is faster :) >>> >>> Ok, >>> now I see some uncommitted changes, the guide says: "you may need to >>> invoke >>> synchronize" >>> >>> But how? >>> There is a "synchronize repository... " and "Synchronize full repository >>> ..." >>> menu entry. >>> >>> Which one? >>> The first synchronize does not show me how to actually do anything >>> and the second one shows a intimidating warning :) >>> FInally I removed my fork (it was pretty old), did a new fork and >>> sstarted >>> with >>> a fresh image. >>> >>> >>> I fixed thatâ¦ it should be the first synchronize. But you do not have to >>> do anything other than execute it ;) >>> anyway, what I need to do is to put a note of what happens if (as you) >>> your fork is too old: in that case you can go to Pharo/Synchronize >>> repositories (but anyway, you do not need itâ¦ creating a branch from fogbugz >>> issue will do a fetch and put you in the right place). >>> >>> >>> >>> Finally, the initial setup up is done, I now try to do some work with it >>> and report back >>> >>> >>> thanks! >>> I hope everything goes smooth :) >> >> >> Not that smooth. The view for pull requests is still problematic, it seems >> to do alot in the background on >> resizing the window (it is slow, does it do some lgit-calls on every >> window change ?) . >> And it crashes often. > > > yes, we are working on a revamp of UI that will hopefully fix all this (the > crashes still should not happen :). > > cheers! > Esteban > >> >> <grafik.png> >> >>> >>> >>> cheers! >>> Esteban >>> >>> >>> >>> nicolai >>> >>> >>> >> > >

Feb. 6, 2018

[Pharo 7.0-dev] Build #499: 21237-Remove-UndefinedObjectsuspend

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

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

Feb. 6, 2018

Re: [Pharo-dev] Reviewing Changes ?

by Sven Van Caekenberghe

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. 5, 2018

Re: [Pharo-dev] Reviewing Changes ?

by Esteban Lorenzano

the PR tool will create a branch for you and will to a pull of the changes. yes, PR tool will work on the remote destination of your PR (which is pharo-project/development for Pharo), but this is reasonable. So, *if* your origin remote is not âpharo-projectâ, you need to go to remotes tab and select âReview pull requestsâ on the appropriate remote. Esteban > 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. 5, 2018

Re: [Pharo-dev] Reviewing Changes ?

by Esteban Lorenzano

yes, thatâs a way. anther way is to use âPR toolâ : in menu, choose âGitHubâ, then âReview pull requestsâ¦â. You will need your github user/pass since this is using the github api. â¦ and of course, this can be loadable/testable or not, depending on the part of the system you will be loading (it is usually ok). But in general, it should work (I do not think many people has used this tool so it can fail). Esteban > On 5 Feb 2018, at 14:52, tesonep(a)gmail.com wrote: > > Hello Sven, > the easy way I found to review an image of the change in a PR is to use the image from the CI server. > > In https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> > you can see all the jobs of the PR (every PR is run in the CI as soon as it is created or updated). > > There you can find the PR by its number, for example: > > https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> > > And then later you can check the results of the tests or downloading an image with the changes in Last Successful Artifacts: > > https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> > > The images are inside the folder "bootstrap-cache" and you should take the Pharo-32bits-****.zip or Pharo-64bits-****.zip. > > Cheers. > > On Mon, Feb 5, 2018 at 1:54 PM, Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> wrote: > 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 <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 ? > Has someone written a guide on how to do this best/most-easily ? > How is/can this be related to contributing ? > > Sven > > > > > -- > Pablo Tesone. > tesonep(a)gmail.com <mailto:tesonep@gmail.com>

Feb. 5, 2018

Re: [Pharo-dev] Reviewing Changes ?

by Pavel Krivanek

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. 5, 2018

Re: [Pharo-dev] Reviewing Changes ?

by tesonep＠gmail.com

Hello Sven, the easy way I found to review an image of the change in a PR is to use the image from the CI server. In https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… you can see all the jobs of the PR (every PR is run in the CI as soon as it is created or updated). There you can find the PR by its number, for example: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… And then later you can check the results of the tests or downloading an image with the changes in Last Successful Artifacts: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… The images are inside the folder "bootstrap-cache" and you should take the Pharo-32bits-****.zip or Pharo-64bits-****.zip. Cheers. On Mon, Feb 5, 2018 at 1:54 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > 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 ? > Has someone written a guide on how to do this best/most-easily ? > How is/can this be related to contributing ? > > Sven > > -- Pablo Tesone. tesonep(a)gmail.com

Feb. 5, 2018

Reviewing Changes ?

by Sven Van Caekenberghe

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 ? Has someone written a guide on how to do this best/most-easily ? How is/can this be related to contributing ? Sven

Feb. 5, 2018

[Bug] Sometimes the debugger opens with the context one off

by Marcus Denker

Hi, This one was annoying me for a while: sometimes, when you put a halt the debugger opens but with exactly the method you put the halt in not selected and hidden (you need to scroll up!). I analysed a bit the situation and the case were this happens is when you put a halt and then run a test to trigger the halt. Normal halts are ok. https://pharo.manuscript.com/f/cases/21236/Sometimes-the-debugger-opens-wit… fix to review: https://github.com/pharo-project/pharo/pull/797

Feb. 5, 2018