May 2016 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

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

May 18, 2016

[pharo-project/pharo-core] 2442be: 60013

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 2442bee1a05362dedd99ee51bbb57012f720b65d https://github.com/pharo-project/pharo-core/commit/2442bee1a05362dedd99ee51… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-05-18 (Wed, 18 May 2016) Changed paths: R Network-Url.package/extension/Text/instance/asUrl.st A ScriptLoader60.package/ScriptLoader.class/instance/accessing/inboxRepository50.st A ScriptLoader60.package/ScriptLoader.class/instance/accessing/repository50.st M ScriptLoader60.package/ScriptLoader.class/instance/cleaning/addHomeRepositoryToAllPackagesExcept_.st M ScriptLoader60.package/ScriptLoader.class/instance/mc related utils/addHomeRepositoryToAllPackages.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60012.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60013.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60012.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60013.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60013 18197 Text asUrl makes the package Network-Url dependent on Text https://pharo.fogbugz.com/f/cases/18197 18251 add 50 repo for now so we can merge https://pharo.fogbugz.com/f/cases/18251 http://files.pharo.org/image/60/60013.zip

May 18, 2016

Re: [Pharo-dev] Mocketry names again

by Denis Kudriashov

So at the end of week I will rename "should got" into "should receive" 2016-04-27 23:39 GMT+02:00 Carlos Lombardi <carlombardi(a)gmail.com>: > Hi again, > > ok, just to have coherence between the names for the two possible outcomes > of a method, you could use #beReturnedBy instead of #beReturnedFrom: . You > would have #beReturnedBy: and #beRaisedBy: > > On Wed, Apr 27, 2016 at 10:00 AM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > >> >> 2016-04-27 0:33 GMT+02:00 Carlos Lombardi <carlombardi(a)gmail.com>: >> >>> ... maybe >>> >>> #result should beTheResultOf: [mock someMessage]. >>> #result should not beTheResultOf: [mock anotherMessage]. >>> >> >> It's nice.I think "The" can be omitted: >> >> #result should beResultOf: [mock someMessage]. >> >> >> But anyway I use word #return because there are different types of >> result: value return and error signal. There is no expression for last case >> but it would be like: >> >> anError should beRaisedBy: [mock someMessage] >> >> >

May 18, 2016

[pharo-project/pharo-core]

by GitHub

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

May 18, 2016

[pharo-project/pharo-core] 77a6da: 60012

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 77a6dad0487acc19e18bc5dc5762c7ef68373112 https://github.com/pharo-project/pharo-core/commit/77a6dad0487acc19e18bc5dc… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-05-18 (Wed, 18 May 2016) Changed paths: R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60011.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60012.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60011.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60012.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60012 18228 Remove dependency of FinderUI in WorldState >>#mostUsedToolsOn: https://pharo.fogbugz.com/f/cases/18228 http://files.pharo.org/image/60/60012.zip

May 18, 2016

[pharo-project/pharo-core] 5c0aa4: 60011

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 5c0aa470ffb273f3568936bd3969ab51d3e1aa34 https://github.com/pharo-project/pharo-core/commit/5c0aa470ffb273f3568936bd… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-05-18 (Wed, 18 May 2016) Changed paths: M Morphic-Core.package/WorldState.class/class/world menu items/mostUsedToolsOn_.st M Morphic-Widgets-Taskbar.package/extension/SystemWindow/instance/taskbarButtonMenu_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60010.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60011.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60010.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60011.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Text-Core.package/TextAction.class/instance/evaluating/actOnClick_for_in_editor_.st Log Message: ----------- 60011 18200 TextAction calls unimplemented method #cull:cull:cull:cull:cull: https://pharo.fogbugz.com/f/cases/18200 18199 "close all debuggers" could also be in the taskbar context menu https://pharo.fogbugz.com/f/cases/18199 http://files.pharo.org/image/60/60011.zip

May 18, 2016

[pharo-project/pharo-core]

by GitHub

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

May 18, 2016

Re: [Pharo-dev] about spurious conflicts

by Marcus Denker

The reason is that the merge does not find the âlast commonâ package. There is an issue that solves this (adding temporarily the Pharo5 repo). Marcus > On 17 May 2016, at 22:08, stepharo <stepharo(a)free.fr> wrote: > > Hi > > > while migrating some of the issues from 50 to 60, I noticed that many of the conflicts are > > not conflicts since the code of both methods and the protocols are the same. > > Does anybody experienced the same? > > Here are some examples and I'm puzzled. > > https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/417//artifact/valid… > > https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/418//artifact/valid… > > > Stef > >

May 18, 2016

Re: [Pharo-dev] fogbugz process Check seems to be stuck

by Alistair Grant

Hi Sven, On Wed, May 18, 2016 at 07:33:10AM +0200, Sven Van Caekenberghe wrote: > Hi Alistair, > > Everything is OK. > > Once Issue Validation succeeds, your slice is ready to be integrated (a review by another human would help too). Integration itself is a manual process done by an integrator. > > The reason there was a second check is that every time a new build is done, all open issues are rechecked. > > It got stuck, but also unstuck automatically. Thanks for the clarification, so I'll just wait for the issue to make its way through the system. Cheers, Alistair > > On 18 May 2016, at 07:03, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > > > Hi All, > > > > Would someone mind clarifying the issue process for me. > > > > pharo.org states: > > > > In success, the state will be "Fix Reviewed by the Monkey". This is > > where humans come into the picture: your code needs to be reviewed, if > > possible by 2-3 people. If they accept it, the state moves to "Fix to > > Include", after which it will be committed to the development branch as > > soon as possible. > > > > After I submitted the slice to issue 18248 the monkey successfully > > reviewed it and then assigned it back to me. > > > > Then a little while later the monkey complained that the "Check seems to > > be stuck. I will try again". It looks like the second validation also > > succeeded. > > > > Do I need to do something to initiate the human review, or should I be > > taking some other action? > > > > Thanks, > > Alistair

May 18, 2016

File List -- MNU: RubTextEditor>>doIt

by Martin McClure

So I open Pharo 5, and the *very* *first* thing I do is to open a file list, select a file that contains the Metacello expression to load my project, and select "Do it" from the menu. And get MNU: RubTextEditor>>doIt :-( This was on Linux, in case that makes a difference. I couldn't quickly track down how this is *supposed* to work. Regards, -Martin

May 18, 2016