- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #648: 4306-Add-comment-why-name-cache-in-SystemDictionary-is-sorted

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

There is a new Pharo build available! The status of the build #648 was: SUCCESS. The Pull Request #4359 was integrated: "4306-Add-comment-why-name-cache-in-SystemDictionary-is-sorted" Pull request url: https://github.com/pharo-project/pharo/pull/4359 Issue Url: https://github.com/pharo-project/pharo/issues/4306 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 19, 2019

[Pharo 8.0] Build #647: Fixing change detection of traits

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

There is a new Pharo build available! The status of the build #647 was: SUCCESS. The Pull Request #4360 was integrated: "Fixing change detection of traits" Pull request url: https://github.com/pharo-project/pharo/pull/4360 Issue Url: https://github.com/pharo-project/pharo/issues/fixing Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 19, 2019

[Pharo 8.0] Build #646: code-completion-context-tests

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

There is a new Pharo build available! The status of the build #646 was: FAILURE. The Pull Request #4332 was integrated: "code-completion-context-tests" Pull request url: https://github.com/pharo-project/pharo/pull/4332 Issue Url: https://github.com/pharo-project/pharo/issues/code Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 19, 2019

[Pharo 8.0] Build #645: 4355-ProfStef-has-some-dead-class-comments-and-needs-more-love-

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

There is a new Pharo build available! The status of the build #645 was: FAILURE. The Pull Request #4356 was integrated: "4355-ProfStef-has-some-dead-class-comments-and-needs-more-love-" Pull request url: https://github.com/pharo-project/pharo/pull/4356 Issue Url: https://github.com/pharo-project/pharo/issues/4355 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 19, 2019

[Pharo 8.0] Build #644: Fix asDate executable comments

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

There is a new Pharo build available! The status of the build #644 was: FAILURE. The Pull Request #4358 was integrated: "Fix asDate executable comments" Pull request url: https://github.com/pharo-project/pharo/pull/4358 Issue Url: https://github.com/pharo-project/pharo/issues/bottomWithSeb Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 19, 2019

Re: [Pharo-dev] Epicea Feedback

by Sean P. DeNigris

In case it helps anyone in the future, here is the "poor man's" browser I hacked together to find all Magritte changes that needed to be rescued from an image where those changes got out-of-sync so I couldn't use Iceberg: nodes := EpFileLogNode fromAllLogsIn: EpMonitor current sessionStore baseLocator. relevantNodes := nodes reject: [ :n | (n globalName endsWith: 'g3') or: [ n globalName endsWith: 'ng' ] ]. relevantNodes do: [ :node | node populateReferencedNodesWith: relevantNodes ]. entries := relevantNodes flatCollect: [ :n | n log entries ]. filter := EpAndFilter withAll: { EpImpactCodeChangeFilter new environment: self class environment; yourself. EpPluggableFilter new condition: [ :e | e content isCodeChange and: [ e content affectedPackageName beginsWith: 'Magritte' ] ]. EpPluggableFilter noTriggerFilter }. filteredEntries := entries select: [ :e | filter accepts: e ]. filteredEntries sort: [ :a :b | (a tagAt: #time) > (b tagAt: #time) ]. groups := filteredEntries groupedBy: [ :e | (e content respondsTo: #methodAffected) ifFalse: [ '?' ] ifTrue: [ e content methodAffected ] ]. events := groups collect: [ :col | col first content ] as: OrderedCollection. events collect: [ :e | "{ e." DiffModel new showOptions: true; leftText: (e accept: EpOldStateVisitor new); rightText: (e accept: EpNewStateVisitor new); contextClass: e class; buildWithSpec "}" ]. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Aug. 18, 2019

Epicea Feedback

by Sean P. DeNigris

Not complaining at all and appreciate everyone's hard (mostly-unpaid) work, but providing raw feedback in case it's helpful... - Browser awkward: filters disappear whenever left selection changed; no multi-select of sessions, which led to a host of difficulties described below. - What is the heuristic to find API access points? Epicea package has no comment, 'Browser' tag doesn't seem to have an XyzBrowser class, no particular class in the 'Model' tag jumps out at me as an access point; as above Browser about text not set. I finally bring up Morphic halos on the browser and after flopping around, find subclasses of EpLogNode; I browse it and find EpLogNodeGraphModel, which sounds interesting and turns out to be a spec. I figure out how to list the log files, but not how to get the entries - I was expecting a term like that and the relevant method (#log it turns out) has no comment to indicate it's what I'm looking for. Now that I'm starting to understand the project organization, back to the browser to explore EpUnifiedBrowserModel. After a bit of poking around, I suspect (correctly) that #log is what I'm after. Based on code I extract from the browsers and a bit of experimenting in GT, I come up with the following seemingly very complex script: nodes := EpFileLogNode fromAllLogsIn: EpMonitor current sessionStore baseLocator. nodes do: [ :node | node populateReferencedNodesWith: nodes ]. nodes flatCollect: [ :n | n log events select: [ :e | e affectedPackageName beginsWith: 'Magritte' ] ] I now run into a series of problems because, although EpCodeChange declares #affectedPackageName as an abstract method, not all events are EpCodeChanges. I exclude EpUndos. Easy enough. Now I come to an EpGenericRefactoring. This one is harder because p.s. <rant>Code names for internal projects seem extremely counterproductive. Hiedra tells me absolutely nothing about functionality. It might as well be called XyzWidgetThing</rant> ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Aug. 18, 2019

[Pharo 8.0] Build #643: Remove-dependency-between-FileSystem-Core-and-Deprecated-file-package

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

There is a new Pharo build available! The status of the build #643 was: SUCCESS. The Pull Request #4340 was integrated: "Remove-dependency-between-FileSystem-Core-and-Deprecated-file-package" Pull request url: https://github.com/pharo-project/pharo/pull/4340 Issue Url: https://github.com/pharo-project/pharo/issues/Remove Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 18, 2019

[Pharo 8.0] Build #642: Remove-PNGReader-test-missing-resources

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

There is a new Pharo build available! The status of the build #642 was: FAILURE. The Pull Request #4345 was integrated: "Remove-PNGReader-test-missing-resources" Pull request url: https://github.com/pharo-project/pharo/pull/4345 Issue Url: https://github.com/pharo-project/pharo/issues/Remove Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 18, 2019

[Pharo 8.0] Build #641: Calypso-should-not-depend-on-deprecated-streams

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

There is a new Pharo build available! The status of the build #641 was: FAILURE. The Pull Request #4342 was integrated: "Calypso-should-not-depend-on-deprecated-streams" Pull request url: https://github.com/pharo-project/pharo/pull/4342 Issue Url: https://github.com/pharo-project/pharo/issues/Calypso Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 18, 2019