- Pharo-dev - lists.pharo.org

Pharo and Docker (some steps)
by Torsten Bergmann Sept. 9, 2018

Sept. 9, 2018

For those interested in Docker: I recently played with Pharo and Docker and summarized some of my steps in a small tutorial in my Pharo wiki: http://wiki.astares.com/pharo/613 There is also a page following Mike Filonovs suggestions on the Pharo docker file: http://wiki.astares.com/pharo/615 Maybe this is useful for others too. Bye T.

3 2

Added Pharo8 milestone to issue tracker
by Marcus Denker Sept. 9, 2018

Sept. 9, 2018

Hi, As part of getting ready for the release, we should check all issue tracker entries tagged for pharo7 and decide if they are real show stoppers. I added a Pharo8 Milestone (but when removing the pharo7 milestone, it is in most cases better to just put it on âLaterâ). Marcus

1 0

[Pharo 7.0-dev] Build #1239: 22434 Cleanup FloatTest
by ci-pharo-ci-jenkins2＠inria.fr Sept. 8, 2018

Sept. 8, 2018

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

1 0

[Pharo 7.0-dev] Build #1238: 22404-NECSymbolCache-is-not-needed-anymore
by ci-pharo-ci-jenkins2＠inria.fr Sept. 8, 2018

Sept. 8, 2018

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

1 0

[Pharo 7.0-dev] Build #1237: 22422 Correctly deprecate Ring- Core-Kernel and Ring Tests Kernel
by ci-pharo-ci-jenkins2＠inria.fr Sept. 7, 2018

Sept. 7, 2018

There is a new Pharo build available! The status of the build #1237 was: SUCCESS. The Pull Request #1773 was integrated: "22422 Correctly deprecate Ring- Core-Kernel and Ring Tests Kernel" Pull request url: https://github.com/pharo-project/pharo/pull/1773 Issue Url: https://pharo.fogbugz.com/f/cases/22422 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] [Pharo-users] [Moose-dev] Pharo eye-candy: Domain-Specific Modeling and Simulation
by Nick Papoylias Sept. 7, 2018

Sept. 7, 2018

Thanx Alex :) Looking forward to the Roassal talk on Thursday ! On Fri, Sep 7, 2018 at 5:22 PM Alexandre Bergel via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > Wow!!!!! > You guys rock! > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Sep 6, 2018, at 2:17 PM, Nick Papoylias <npapoylias(a)gmail.com> wrote: > > A nice example of how Pharo can be used for > domain-specific modeling and simulation. Short > session from one of our projects at Rochelle: > > https://www.youtube.com/watch?v=Z7wJNhAIaVQ > > Some additional info here: https://goo.gl/jS4NjB > > Currently investigating how to incorporate the new Bloc based > widgets of @feenkcom into the workflow. > > Cheers, > > Nick > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev > > >

1 0

Release test for unused temps and other
by Torsten Bergmann Sept. 7, 2018

Sept. 7, 2018

Hi, the very nice contribution on GIFReadWriter/animated images (see https://pharo.manuscript.com/f/cases/22137) unfortunately introduced some methods that had no sender, were uncategorized and had unused temporary variables, etc. Something that is meanwhile shown by our tools and easy to fix. I guess it was some overseen leftover. Unfortunately this also slipped through the integration process as it was merged without an approval from a community reviewer. I dont want to lament too much on this specifc case (especially as I now fixed it in https://pharo.fogbugz.com/f/cases/22426) But after I cleaned the P7 image this spring to not have unused temporaries anymore I was suprised to find such glitches again now. So to me it shows that we need to write more tests to detect violations and keep our achieved quality standards up and also should not solely rely on the review process. Otherwise we need to invest our time in cleaning up our own stuff afterwards again and again. To be specific one can evaluate: CompiledMethod allInstances select: [:m | m ast temporaries anySatisfy: [:x | x binding isUnused ]]. to find unused temps - which would be easy to package up into one of the release test to ensure no unused temp vars are left (the tearDown would require an "ASTCache reset"). The problem is that this simple test would take around 20-30 seconds depending on machine and I do not know if it would be a good idea/good solution to integrate. Especially I'm not sure if it is worth the issue or will kill the CI again and again. What do you think about it? Comments appreciated? Thanks T.

5 6

Pharo eye-candy: Domain-Specific Modeling and Simulation
by Nick Papoylias Sept. 7, 2018

Sept. 7, 2018

A nice example of how Pharo can be used for domain-specific modeling and simulation. Short session from one of our projects at Rochelle: https://www.youtube.com/watch?v=Z7wJNhAIaVQ Some additional info here: https://goo.gl/jS4NjB Currently investigating how to incorporate the new Bloc based widgets of @feenkcom into the workflow. Cheers, Nick

6 9

Iceberg > review pull request & repo name clash
by Ben Coman Sept. 7, 2018

Sept. 7, 2018

Two concerns from one flow of events... I was trying out "review a pull request" feature for the first time. This looks very promising, but I got stuck. In Pharo 6.1... Downloaded http://files.pharo.org/platform/Pharo6.1-win.zip Updated Icerberg per https://github.com/pharo-vcs/iceberg#update-iceberg Iceberg > Settings > Use custom keys = Enabled > Add > Clone remote repository Remote URL = git@github.com:exercism/pharo.git ==> "pharo" repo appears, status "Not loaded" > "pharo" repo > Packages ==> BaselineOfExercism, Exercism, etc > "pharo" repo > Github > View pull request > origin > enter github account password ==> shows PR#98 "Move setup to class initialization..." > right-click 98 > Review pull request ==> an empty window titled "Browsing pull request: #98...." appeared (see attached) Trying the same in Pharo 7 gave a different problem... >From Launcher started Pharo-7.0.0-alpha.build.1231.sha.cf8aa48.arch.32bit... Iceberg > Settings > Use custom keys = Enabled > "pharo" repo > Forget Repository > Ticked "Also remove repository from file system" > Add > Clone remote repository Remote URL = git@github.com:exercism/pharo.git ==> "pharo" appears, status = "Fetch required. Unknown cf8aa48" > "pharo" repo > Fetch ==> no change in status, but I do see the the expected files in repo on disk > "pharo" repo > Packages ==> only shows LICENSE and README.md. Why did this "just work" in 6.1 ? It seems the source directory is wrong. From this point is it possible to update the source directory to "dev/src/" ? Maybe its due to the name clash "pharo-project/pharo" versus "exercism/pharo" and something was retained after the "Forget Repository". Such a name clash is unfortunate, but is a corner case that should be handled. This could be a useful test case. Before I log an issue, could someone check I'm not doing something wrong. cheers -ben P.S. A work around might have been giving a custom local name for the exercism/pharo repo, much like you can specify the folder created by command line 'git clone'. Is such a feature planned for Iceberg?

2 1

[Pharo 7.0-dev] Build #1236: 22424 Correctly deprecate Ring-Deprecated-Tests-Containers and Ring-Dâ¦
by ci-pharo-ci-jenkins2＠inria.fr Sept. 7, 2018

Sept. 7, 2018

There is a new Pharo build available! The status of the build #1236 was: SUCCESS. The Pull Request #1775 was integrated: "22424 Correctly deprecate Ring-Deprecated-Tests-Containers and Ring-Dâ¦" Pull request url: https://github.com/pharo-project/pharo/pull/1775 Issue Url: https://pharo.fogbugz.com/f/cases/22424 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0