October 2013 - Pharo-dev - lists.pharo.org

My talk today at Smalltalks 2013
by Esteban Lorenzano Oct. 31, 2013

Oct. 31, 2013

Here are the slides: http://www.slideshare.net/pharoproject/smalltalks13-pharo-techoverview I think it didn't went so bad... :) Esteban

3 3

Jenkins Down
by Camillo Bruni Oct. 31, 2013

Oct. 31, 2013

With a one day grace period [1] all our Jenkins instances are now down, the only slaves that remains is our mac slave. [1] https://wiki.inria.fr/ciportal/Event_20131030_cs best regards, camillo

1 0

[pharo-project/pharo-core] e70397: 30533
by GitHub Oct. 31, 2013

Oct. 31, 2013

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: e70397c31a642d5caeda5d9182cd4915022950c2 https://github.com/pharo-project/pharo-core/commit/e70397c31a642d5caeda5d91… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-10-31 (Thu, 31 Oct 2013) Changed paths: A Collections-Abstract.package/HashedCollection.class/instance/private/noCheckAdd_.st M Kernel.package/ContextPart.class/instance/controlling/restart.st M Kernel.package/ContextPart.class/instance/controlling/resume_.st M Kernel.package/ContextPart.class/instance/controlling/resume_through_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script188.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30533.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30533 3455 HashedCollection missed abstract method noCheckAdd: https://pharo.fogbugz.com/f/cases/3455 12035 Slot and Protocol should be compact https://pharo.fogbugz.com/f/cases/12035 12034 Accessor to temporaries of context in case of unwinding not explicit https://pharo.fogbugz.com/f/cases/12034 http://files.pharo.org/image/30/30533.zip

1 0

[pharo-project/pharo-core]
by GitHub Oct. 31, 2013

Oct. 31, 2013

Branch: refs/tags/30533 Home: https://github.com/pharo-project/pharo-core

1 0

About SqNumberParser
by StÃ©phane Ducasse Oct. 30, 2013

Oct. 30, 2013

Hi nicolas We would really like to have only one number parser in Pharo as well as handling the 1.0s syntax marcus raised a question that I could not answer. Do you habve nfrmation to share with us so that we can take a decision? Stef so the strange thing is that this is *explicitly* implemented in SqNumberParser to not allow 2.0s - do not allow single s without following digits as ScaledDecimal It is not explained why this is a good idea. In general, we need to merge the whole NumberParser hierarchy into one class, i don't understand why we have three classes now.

5 10

missing updates: 30503 30504
by Camillo Bruni Oct. 30, 2013

Oct. 30, 2013

What happened with those updates? Why are there no images? If something like this happens, the git exporter needs to be properly reset, otherwise we don't have consecutive numbers :/ We really need to invest a couple of sprints in creating an integration UI, ben and I started this 2 years ago and it lies dormant since then. The current way is just too brittle...

8 34

smalltalkhub down
by Sebastian Sastre Oct. 30, 2013

Oct. 30, 2013

heads up o.O

5 6

Oct. 30, 2013

http://www.slideshare.net/pharoproject/2013smalltalksconference-pharo-is-yo… Stef

4 3

Changing non-copying selectors to #...InPlace
by Max Leske Oct. 30, 2013

Oct. 30, 2013

To continue the discussion on this topic (stemming from issue 11635) Iâm starting a new thread. Please share your thoughts. Form the other thread: > Personally I'm for more intention revealing selectors; I quite like #shuffled and #shuffleInPlace. If we can agree on a different naming scheme we should then apply it to other methods aswell of course (e.g. #sorted, #sortInPlace). My proposition is to keep the selectors named #â¦d (#shuffled, #sorted, etc.), which operate on a copy, and rename the others (#shuffle, #sort, etcâ¦) to #â¦InPlace (#shuffleInPlace, #sortInPlace, etc.). The rational behind this is that (to my mind) the current scheme is not intention revealing (e.g. #shuffle vs. #shuffled). Which is especially problematic for newcomers. Max

3 2

Image Stability
by Camillo Bruni Oct. 30, 2013

Oct. 30, 2013

Failing Tests ------------- Seems like our test splitup did not work properly: https://ci.inria.fr/pharo/job/Pharo-3.0/ The tests starting with A-L did not run since a while! >From what I get quite a bunch of tests are failing. Pending Processes + Default Username ------------------------------------ There is a strange amount of processes hanging around in the image. Plus there was a report that a default user name was set in the image (Not sure if that still persists, since I directly set mine with startup preferences). Was a new image version ben uploaded manually? Unstable Image + VM ------------------- Additionally since a while the image became much more unstable after running the tests twice (I know not a common case, but it should NEVER provoke a VM crash), see here: https://ci.inria.fr/pharo/view/3.0-Analysis/job/Pharo-3.0-Test-Twice/buildT… >From what I get, ReleaseTest>>testObsoleteBehaviors provokes a VM crash.

2 2