June 2018 - Pharo-dev - lists.pharo.org

Recent Pharo does not work (to me) with "El Capitan"
by Jordi Delgado June 14, 2018

June 14, 2018

Hi, First of all, thanks everybody for your effort making Pharo. It's hugely appreciated. But..., I cannot make Pharo 6 or 7 work in os x "El Capitan". I've tried stable and latest for images and vm's, either 6.0, 6.1 and 7.0. Any combination fails to start. Also, no download from Pharo.org works for me (not the launcher, not the standalone). It's always an error that looks like this one: "Illegal instruction Wed Jun 13 19:52:37 2018 VM: 201805090836 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Wed May 9 10:36:12 2018 CommitHash: 334be97 Plugins: 201805090836 https://github.com/OpenSmalltalk/opensmalltalk-vm.git ./pharo: line 11: 2623 Abort trap: 6 "$DIR"/"pharo-vm/Pharo.app/Contents/MacOS/Pharo" --headless "$@"" Is this a known problem (hopefully with some known workaround), or is it me getting old? I am not new to Pharo and everything worked fine up to Pharo 5.0. This problem only appears in os x "El Capitan". I use Pharo, any version, in Ubuntu with no problem at all. Thanks in advance, -- Bests, Jordi Delgado Computer Science Department - Universitat PolitÃ¨cnica de Catalunya Campus Nord, Omega building, Office S115 c/Jordi Girona Salgado, 1-3 08034 Barcelona, Spain. Phone: +34.93.413.40.18 Public Key: https://pgp.mit.edu/pks/lookup?op=get&search=0xB7911543AD9E79A8

4 11

Pharo 7 and Traits ?
by Sven Van Caekenberghe June 14, 2018

June 14, 2018

Hi, So what is the story with Pharo 7 and Traits ? I may be wrong, but were they not removed but flattened ? How are external libraries that want to support multiple Pharo versions supposed to cope when they need to add extension methods to (meta) class ? I have a problem with STON. Sven

2 3

[Pharo 7.0-dev] Build #1057: 22139-fix-the-last-sender-of-asIcon
by ci-pharo-ci-jenkins2＠inria.fr June 14, 2018

June 14, 2018

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

1 0

[Pharo 7.0-dev] Build #1056: 22142 Cleanup Files-Test
by ci-pharo-ci-jenkins2＠inria.fr June 14, 2018

June 14, 2018

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

1 0

Sista & Pharo 7
by Ben Coman June 14, 2018

June 14, 2018

Is Sista operational in the latest Pharo 7 builds? What is the plan for Sista in relation to Pharo 7? cheers -ben

4 3

[Pharo 7.0-dev] Build #1055: 22135-Remove-use-of-Transcript-from-AST-Core
by ci-pharo-ci-jenkins2＠inria.fr June 14, 2018

June 14, 2018

There is a new Pharo build available! The status of the build #1055 was: SUCCESS. The Pull Request #1538 was integrated: "22135-Remove-use-of-Transcript-from-AST-Core" Pull request url: https://github.com/pharo-project/pharo/pull/1538 Issue Url: https://pharo.fogbugz.com/f/cases/22135 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1054: 22138 Comment RBBrowserEnvironmentTest
by ci-pharo-ci-jenkins2＠inria.fr June 14, 2018

June 14, 2018

There is a new Pharo build available! The status of the build #1054 was: FAILURE. The Pull Request #1540 was integrated: "22138 Comment RBBrowserEnvironmentTest" Pull request url: https://github.com/pharo-project/pharo/pull/1540 Issue Url: https://pharo.fogbugz.com/f/cases/22138 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

reinstating original UI thread after debugging
by Ben Coman June 14, 2018

June 14, 2018

I notice... DebugSession >> resumeProcess "Make sure the interrupted process is restored properly and restart the low space handler" interruptedProcess isTerminated ifFalse: [ errorWasInUIProcess ifTrue: [ UIManager default resumeUIProcess: interruptedProcess ] ifFalse: [ interruptedProcess resume ]]. "restart low space handler" Smalltalk installLowSpaceWatcher. and... MorphicUIManager >> resumeUIProcess: aProcess "Adopt aProcess as the project process -- probably because of proceeding from a debugger" UIProcess := aProcess. UIProcess resume This doesn't seem to do anything regarding the second UI process spawned in... MorphicUIManager >> debugProcess:context:label:fullView:notification: With Process Browser running with auto-update on, running the following experiment confirms that the second spawned UI is killed. TestCase subclass: #Example2 Example2 >> test1 Processor activeProcess name: 'ORIGINAL UI'. self halt So I'm curious, where is the code killing the second UI ? Also curious, when the first UI turns into a debuggger, why later reinstate the first UI and kill the second UI? If the second UI started clean and is running happily, why not leave it running and let first UI thread terminate normally? I get some strange behaviour** sometimes , and wonder if the swap back it might be related to this. ** Like today #testUserPriority below not opening a debugger at the first halt statement, or opening a pre-debug window that has a blank pane. testUserPriority debug := true. Processor activeProcess priority: 38. self halt. highPriorityProcess := self highPriorityRunLoop. Transcript cr. debug ifTrue: [self halt]. 3 timesRepeat: [ Transcript crShow: 'U'. self wakeHighPriorityLoop.]. highPriorityProcess terminate. cheers -ben

1 0

Re: [Pharo-dev] ApplicationSecurity Questions
by Sean DeNigris June 13, 2018

June 13, 2018

> Now I've fixed the BaselineOfApplicationSecurity Yes, successfully installed. > I don't have time to try it or support it in Pharo 5 now :( No problem. I only tried because I failed in Pharo 6 :) > Add an adaptor using the Control Panel then go to: Ah, yes! Up and running :) > Please let me know how it is going, Wil do

1 0

[Ann] Iceberg v1.1.0
by Guillermo Polito June 13, 2018

June 13, 2018

Time for the weekly Iceberg update. Thanks to all brave users, issue reporters and contributors :). Key changes: we have introduced some tag support, a new credential manager to manage keys and passwords per host or repository, a new version of tonel, and made a first step towards a simplified contribution to Iceberg by listing it as Pharo's repository. Enjoy, Guille in behalf of all Iceberg contributors Following, the detailed changes log. New Features #842 <https://github.com/pharo-project/pharo/pull/842> Adding Credentials Store #843 <https://github.com/pharo-project/pharo/pull/843> Update Tonel to 1.0.7 #823 <https://github.com/pharo-project/pharo/pull/823> Iceberg repository should be listed as Pharo's one #841 <https://github.com/pharo-project/pharo/pull/841> Basic tag support ( #372 <https://github.com/pharo-project/pharo/pull/372>) Infrastructure #787 <https://github.com/pharo-project/pharo/pull/787> Add Windows ci with Appveyor (not yet green!) Enhancements #827 <https://github.com/pharo-project/pharo/pull/827> Add package dialog has some glitches #833 <https://github.com/pharo-project/pharo/pull/833> replace #asIcon with #iconNamed: #832 <https://github.com/pharo-project/pharo/pull/832> Move Iceberg from MostUsedTools to Tools #830 <https://github.com/pharo-project/pharo/pull/830> Better handling of not github remote urls #825 <https://github.com/pharo-project/pharo/pull/825> Enhance Migrate to tonel commit message #637 <https://github.com/pharo-project/pharo/pull/637> Show tag version instead of "Detached HEAD" #829 <https://github.com/pharo-project/pharo/pull/829> migrate-versions-browser Bug Fixes #835 <https://github.com/pharo-project/pharo/pull/835> Compare file definitions by their binary uninterpreted content #838 <https://github.com/pharo-project/pharo/pull/838> Clone from incorrect github repository fails with DNU #826 <https://github.com/pharo-project/pharo/pull/826> Pushing to virgin repository raises a DNU

7 12