- Pharo-dev - lists.pharo.org

Now issues which are hanging on Monkey checking resumes automatically

by Denis Kudriashov

Hi. We added little job to automatically resume issues which are stuck on monkey checking more than one hour. Such issues will be returned to previous status "Fix review needed"

Feb. 2, 2016

Re: [Pharo-dev] CI is down?

by Christophe Demarey

yes, good idea Le 2 fÃ©vr. 2016 Ã 14:08, Ben Coman a Ã©crit : > Perhaps pharo-dev can be subscribed to the annoucements? > cheers -ben > > On Tue, Feb 2, 2016 at 8:34 PM, Christophe Demarey > <Christophe.Demarey(a)inria.fr> wrote: >> Yes, there is a maintenance. >> You should have received this message (if you did not unregister from >> communication lists): >> >> Dear users, >> >> A maintenance is planned tomorrow (2/2) to upgrade the storage of the CI >> servers. Thus, the service will be stopped between 1pm and 2pm. >> >> Thank you for your understanding, >> Emmanuel >> >> >> Le 2 fÃ©vr. 2016 Ã 13:14, Aliaksei Syrel a Ã©crit : >> >> Hi >> >> https://ci.inria.fr/pharo is not responding >> Has any one the same problem? >> >> Cheers, >> Alex >> >> >

Feb. 2, 2016

[pharo-project/pharo-core]

by GitHub

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

Feb. 2, 2016

[pharo-project/pharo-core] d5f211: 50563

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: d5f211e9bbe8bcaa74f087bebae421e0c7a84a41 https://github.com/pharo-project/pharo-core/commit/d5f211e9bbe8bcaa74f087be… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-02-02 (Tue, 02 Feb 2016) Changed paths: A Deprecated50.package/extension/Morph/instance/submorphNamed_.st A Deprecated50.package/extension/Morph/instance/submorphNamed_ifNone_.st M Flashback-Decompiler.package/FBDDecompiler.class/instance/private/interpretMethod_.st A Flashback-Decompiler.package/FBDDecompiler.class/instance/private/maybeSkipCallPrimitiveBytecode_.st R Morphic-Core.package/Morph.class/instance/submorphs-accessing/submorphNamed_.st R Morphic-Core.package/Morph.class/instance/submorphs-accessing/submorphNamed_ifNone_.st A OpalCompiler-Core.package/OCClassScope.class/instance/accessing/class_.st A OpalCompiler-Core.package/OCClassScope.class/instance/accessing/getClass.st R OpalCompiler-Core.package/OCClassScope.class/instance/initializing/class_.st A OpalCompiler-Core.package/OCLiteralVariable.class/instance/testing/isFromSharedPool.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50562.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50563.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50562.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50563.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50563 17516 add #isFromSharedPool to OCLItteralVariable https://pharo.fogbugz.com/f/cases/17516 17495 Decompiler cant decompile Object>>#instVarAt: due to error code https://pharo.fogbugz.com/f/cases/17495 17508 Deprecate Unused Morph methods: submorphNamed: and submorphNamed: aName ifNone: aBlock https://pharo.fogbugz.com/f/cases/17508 http://files.pharo.org/image/50/50563.zip

Feb. 2, 2016

Re: [Pharo-dev] GTInspector and PointerExplorer

by Ben Coman

On Tue, Feb 2, 2016 at 10:38 PM, Ben Coman <btc(a)openinworld.com> wrote: > On Tue, Feb 2, 2016 at 4:24 PM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: >> Anyone working with GTInspector and inspecting "pointers to" (menu Item >> "Open pointers to"). >> Either I make something wrong or it just does not work. The only references >> I can >> see in this pointer inspector are the references *from* the inspector >> itself. >> >> I put an EllipseMorph in a Morph and choosed "Open Pointers to" in the >> inspector of >> the EllipseMorph. >> I would expect something like >> EllipseMorph <- array (submorphs) <- Morph >> >> But instead I only see this: >> > > I agree it seems really hard to chase pointersTo. > > Doing "EllipseMorph new openInWorld. World inspect." > I can see the EllipseMorph in the "submorphs" ivar at (for me) array > item 4. In the raw tab, right-clicking on item 4 > Open Pointers To, > I would hope to see the WorldMorph its not there. > > Now in the WorldMorph, right-clicking on "submorphs" > Open Pointers To > at item 3 (for me) shows... "an Array [40 items] ( > nil > nil > nil > nil > nil > nil > nil > nil > nil > nil > nil > nil > nil > nil > nil > nil > nil > nil > nil > 'self'->a WorldMorph(562956288) [world] > #backgroundMorph->nil > #borderColor->(Color r: 0.861 g: 1.0 b: 0.722 alpha: 1.0) > #borderWidth->0 > #bounds->(0@0) corner: (1920@1172) > #color->(Color r: 0.937 g: 0.937 b: 0.937 alpha: 1.0) > #extension->a MorphExtension (287899392) [other: (dragEnabled -> > true) (dropEnabled -> true) (lastKeystroke -> '<down>') (kmDispatcher > -> a KMDispatcher)] > #fullBounds->(0@0) corner: (1920@1172) > #griddingOn->nil > #osWindow->nil > #owner->nil > #session->nil > #submorphs->an Array(a TaskbarMorph(804941056) a > GLMSystemWindow(9541632) a GLMSystemWindow(614298112) an > EllipseMorph(763635712) an ImageMorph(342771456)) > #worldState->a WorldState > nil > nil > nil > nil > nil > nil > nil)" > > ...so WorldMorph's ivars start at item 21, with its self at item 20. Strange? > > > Another thing, World > Tools > Finder > Source > "Open pointers to" > lists only two locations. Inserting a "self halt" at both locations like this > selectionAct: [:list | self halt. > ((list selection pointersToExcept: { list selection }) > reject: [ :each | each pointsOnlyWeaklyTo: list selection > ]) inspect ] > on: $t > entitled: 'Open pointers to' > > would I expect trigger a debugger when I invoke the menu item, but it > doesn't, wtf??? > > cheers -ben >> I would expect something like >> EllipseMorph <- array (submorphs) <- Morph Trying to avoid the fluff added by the UI inspectors, trying this I would expect(?) the following would display the WorldMorph twice... morph := EllipseMorph new openInWorld. refs := morph pointersTo. refs do: [ :ref | ref pointersTo inspect ]. refs inspect. World inspect. but it doesn't. I'm lost. cheers -ben

Feb. 2, 2016

Re: [Pharo-dev] GTInspector and PointerExplorer

by Ben Coman

On Tue, Feb 2, 2016 at 4:24 PM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > Anyone working with GTInspector and inspecting "pointers to" (menu Item > "Open pointers to"). > Either I make something wrong or it just does not work. The only references > I can > see in this pointer inspector are the references *from* the inspector > itself. > > I put an EllipseMorph in a Morph and choosed "Open Pointers to" in the > inspector of > the EllipseMorph. > I would expect something like > EllipseMorph <- array (submorphs) <- Morph > > But instead I only see this: > I agree it seems really hard to chase pointersTo. Doing "EllipseMorph new openInWorld. World inspect." I can see the EllipseMorph in the "submorphs" ivar at (for me) array item 4. In the raw tab, right-clicking on item 4 > Open Pointers To, I would hope to see the WorldMorph its not there. Now in the WorldMorph, right-clicking on "submorphs" > Open Pointers To at item 3 (for me) shows... "an Array [40 items] ( nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil 'self'->a WorldMorph(562956288) [world] #backgroundMorph->nil #borderColor->(Color r: 0.861 g: 1.0 b: 0.722 alpha: 1.0) #borderWidth->0 #bounds->(0@0) corner: (1920@1172) #color->(Color r: 0.937 g: 0.937 b: 0.937 alpha: 1.0) #extension->a MorphExtension (287899392) [other: (dragEnabled -> true) (dropEnabled -> true) (lastKeystroke -> '<down>') (kmDispatcher -> a KMDispatcher)] #fullBounds->(0@0) corner: (1920@1172) #griddingOn->nil #osWindow->nil #owner->nil #session->nil #submorphs->an Array(a TaskbarMorph(804941056) a GLMSystemWindow(9541632) a GLMSystemWindow(614298112) an EllipseMorph(763635712) an ImageMorph(342771456)) #worldState->a WorldState nil nil nil nil nil nil nil)" ...so WorldMorph's ivars start at item 21, with its self at item 20. Strange? Another thing, World > Tools > Finder > Source > "Open pointers to" lists only two locations. Inserting a "self halt" at both locations like this selectionAct: [:list | self halt. ((list selection pointersToExcept: { list selection }) reject: [ :each | each pointsOnlyWeaklyTo: list selection ]) inspect ] on: $t entitled: 'Open pointers to' would I expect trigger a debugger when I invoke the menu item, but it doesn't, wtf??? cheers -ben

Feb. 2, 2016

Re: [Pharo-dev] QualityAssistant feedback

by Marcus Denker

> On 02 Feb 2016, at 14:55, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > 2016-02-02 14:46 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>>: > Hello, > > Yes. Another side effect is that you do not get all these âtempX is not used should it be removeâ > messages when saving a method. > > Instead, semantic analysis tags the variable as not used and the editor shows an icon/highlight. > > What we need to do is to integrate this more with the code critique. > > It would be good to have an action associated with the highlighted temp var for > removing the unused var. Or does this already work ? > No, but it should be easy to addâ¦ Marcus

Feb. 2, 2016

Re: [Pharo-dev] QualityAssistant feedback

by Nicolai Hess

2016-02-02 14:46 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: > Hello, > > Yes. Another side effect is that you do not get all these âtempX is not > used should it be removeâ > messages when saving a method. > > Instead, semantic analysis tags the variable as not used and the editor > shows an icon/highlight. > > What we need to do is to integrate this more with the code critique. > It would be good to have an action associated with the highlighted temp var for removing the unused var. Or does this already work ? > > > On 30 Jan 2016, at 02:39, Ben Coman <btc(a)openinworld.com> wrote: > > > > I've just noticed for "Temporary variables not read AND written" that > > the offending variable in the temporary variable definition is > > highlighted. Is this new? Its very nice to have this visual > > indication. > > > > cheers -ben > > > > >

Feb. 2, 2016

Re: [Pharo-dev] QualityAssistant feedback

by Marcus Denker

Hello, Yes. Another side effect is that you do not get all these âtempX is not used should it be removeâ messages when saving a method. Instead, semantic analysis tags the variable as not used and the editor shows an icon/highlight. What we need to do is to integrate this more with the code critique. > On 30 Jan 2016, at 02:39, Ben Coman <btc(a)openinworld.com> wrote: > > I've just noticed for "Temporary variables not read AND written" that > the offending variable in the temporary variable definition is > highlighted. Is this new? Its very nice to have this visual > indication. > > cheers -ben >

Feb. 2, 2016

Re: [Pharo-dev] Pharo contribution CI problem

by Norbert Hartl

Christophe, > Am 01.02.2016 um 13:44 schrieb Christophe Demarey <Christophe.Demarey(a)inria.fr>: > > > Le 1 fÃ©vr. 2016 Ã 12:36, Norbert Hartl a Ã©crit : > >> >>> Am 01.02.2016 um 12:31 schrieb Christophe Demarey <Christophe.Demarey(a)inria.fr <mailto:Christophe.Demarey@inria.fr>>: >>> >>> >>> Le 1 fÃ©vr. 2016 Ã 12:25, Norbert Hartl a Ã©crit : >>> >>>> Christophe, >>>> >>>>> Am 01.02.2016 um 12:18 schrieb Christophe Demarey <Christophe.Demarey(a)inria.fr <mailto:Christophe.Demarey@inria.fr>>: >>>>> >>>>> Hi Norbert, >>>>> >>>>> Le 1 fÃ©vr. 2016 Ã 11:09, Norbert Hartl a Ã©crit : >>>>> >>>>>> I created a new build on the pharo contribution CI. But regardless what I enter in the axis for the PHARO variable the build is triggered with "default" as PHARO version. >>>>>> >>>>>> Any hints how to change that? Is this a bug? >>>>> >>>>> It is because you only defined one value for the axis. >>>>> If you define more than one, you will get the expected values. >>>>> By the way, the $PHARO env variable should have the correct value even with only one value for the axis. >>>>> >>>> I defined "20 30 40 50" as PHARO axis. >>> >>> But if you read the comment, you will see that you need to define one value per line ;) >> >> What do you mean "one value per line" there is only one line :) I've just looked at another project I did and it seemed to be the same. > > <Capture dâÃ©cran 2016-02-01 Ã 13.43.19.png> > > Could you point me your job? Maybe you use something else. thanks I try that next time. I've created a job for MongoTalk but then I recognized that all the tests are executed on a real database. So I removed to job again :) Norbert

Feb. 2, 2016