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

Re: [Pharo-dev] Recent Pharo does not work (to me) with "El Capitan"

by Tim Mackinnon

Hmm - itâs an older MacOS but I recall it working back then. The msg about âheadless looks a bit suspicious. Are you running what you think you are running? Try following the command line instructions for a zero conf install in a terminal in a fresh directory, that might give you better feedback (and may just work). Tim Sent from my iPhone > On 13 Jun 2018, at 19:07, Jordi Delgado <jdelgado(a)cs.upc.edu> wrote: > > 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 >

June 13, 2018

Recent Pharo does not work (to me) with "El Capitan"

by Jordi Delgado

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

June 13, 2018

[Pharo 7.0-dev] Build #1053: 22133-Rename-Epiceas-test-packages-to-follow-convention

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

There is a new Pharo build available! The status of the build #1053 was: SUCCESS. The Pull Request #1536 was integrated: "22133-Rename-Epiceas-test-packages-to-follow-convention" Pull request url: https://github.com/pharo-project/pharo/pull/1536 Issue Url: https://pharo.fogbugz.com/f/cases/22133 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 13, 2018

Re: [Pharo-dev] problem debugging <Over> - correctly sequencing debug of multi-threaded code per process priorities

by Ben Coman

On 13 June 2018 at 11:46, Ben Coman <btc(a)openinworld.com> wrote: > I'm not sure if I'm doing the wrong thing, or if I've bumped into a > problem with step <Over>. > I'm trying to add some debugging support into multi-threaded code to help > properly sequence debugging different priority processes. I've extracted a > little demo... > > TestCase subclass: #Example > instanceVariableNames: 'doCycle debug highPriorityProcess' > classVariableNames: '' > package: 'KernelX-DelayScheduler' > > > Example >> highPriorityCycle > debug ifTrue: [ self halt ]. > Transcript show: 'H'. > > > Example >> highPriorityRunLoop > doCycle := Semaphore new. > ^[ [ doCycle wait. > self highPriorityCycle ] repeat. > ] forkAt: 45 named: 'Example high side' > > > Process >> isWaiting > ^myList isKindOf: Semaphore > > > Example >> wakeHighPriorityLoop > doCycle signal. > debug ifTrue: [ "wait until high priority process is sleeping" > [ highPriorityProcess isWaiting & highPriorityProcess isTerminated not] > whileFalse: [ > Transcript show: '.'. > 100 milliSeconds wait ]. > self halt > ]. > To make this example simpler, I changed this method to... Example >> wakeHighPriorityLoop |count| count := 0. [ Transcript show: '.'. count := count + 1. count > 10 ifTrue: [^self]. 200 milliSeconds wait. ] repeat. > Example >> testUserPriority > debug := true. > highPriorityProcess := self highPriorityRunLoop. > Transcript cr. > debug ifTrue: [self halt]. > 3 timesRepeat: [ > Transcript crShow: 'U'. > self wakeHighPriorityLoop.]. > highPriorityProcess terminate. > and this method to... Example >> testUserPriority [ 3 timesRepeat: [ Transcript crShow: 'U'. self halt. self wakeHighPriorityLoop.]. ] forkAt: 39 named: 'testUserPriority'. self halt. highPriorityProcess terminate. So there should be no way that the 39-priority thread should block the 40-priority UI thread. But when I run #testUserPriority and step <Over> #wakeHighPriorityLoop the UI blocks for two seconds and then all of a sudden "U..........." appears in full on the Transcript shows. I'd expect to see the dots slowly appearing one-by-one. I really don't understand the behaviour I'm seeing. cheers -ben

June 13, 2018

Re: [Pharo-dev] FileAttributesPlugin: request for comment and testing

by Alistair Grant

Hi Guille, On Wed, 13 Jun 2018 at 11:14, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Hi Alistair, > > This is great! > > I've overlooked the changes, I don't have much of a remark. > Just a question: what would be the semantics of symlinks and character/block files in windows? Thanks for taking a look! On Windows: - #isSymlink will always return false. - The character and block mode bits will never be set. - If you attempt to retrieve symbolic link attributes (despite #isSymlink being false) you'll get a FileSystemError. I've finally got the file times correct on Windows, the 536 file related automated tests pass. I've just got to update the Unix code to match. Cheers, Alistair

June 13, 2018

[Pharo 7.0-dev] Build #1052: 22130-parseFaultyExpression-deserves-a-nice-comment

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

There is a new Pharo build available! The status of the build #1052 was: SUCCESS. The Pull Request #1534 was integrated: "22130-parseFaultyExpression-deserves-a-nice-comment" Pull request url: https://github.com/pharo-project/pharo/pull/1534 Issue Url: https://pharo.fogbugz.com/f/cases/22130 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 13, 2018

[Pharo 7.0-dev] Build #1051: 22132-Semantic-Analyser-do-not-pop-scope-in-methodNode

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

There is a new Pharo build available! The status of the build #1051 was: FAILURE. The Pull Request #1535 was integrated: "22132-Semantic-Analyser-do-not-pop-scope-in-methodNode" Pull request url: https://github.com/pharo-project/pharo/pull/1535 Issue Url: https://pharo.fogbugz.com/f/cases/22132 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 13, 2018

Re: [Pharo-dev] hard to debug multi-threaded tests

by Ben Coman

On 13 June 2018 at 20:29, Ben Coman <btc(a)openinworld.com> wrote: > In Pharo 5, it was possible to do... > > TestCase subclass: #Example > ....etc > > Example >> test1 > [ Transcript > crShow: Processor activeProcess priority printString; > tab; > show: Processor activeProcess name. > self halt. > Transcript > crShow: Processor activeProcess effectiveProcess priority printString; > tab; > show: Processor activeProcess effectiveProcess name > ] forkAt: 39 named: 'TEST'. > > ...and when this was run, a debugger would show for the forked code > and stepping through it would produce the following output... > 39 TEST > 39 TEST > > > In Pharo 71047, no debugger shows up, > and you only get one... > 39 TEST > > > I guess this because more cleanup of tests is being done, > but it makes it harder to debug multi-threaded tests when > debugger can't replicate the way the code normally runs. > Ahhh, but it works to add a halt at the end of the test.... Example >> test1 [ Transcript crShow: Processor activeProcess priority printString; tab; show: Processor activeProcess name. self halt. Transcript crShow: Processor activeProcess effectiveProcess priority printString; tab; show: Processor activeProcess effectiveProcess name ] forkAt: 39 named: 'TEST'. self halt. Sorry for the noise. cheers -ben

June 13, 2018

Re: [Pharo-dev] [Ann] Iceberg v1.1.0

by Esteban Lorenzano

hi, > On 13 Jun 2018, at 14:23, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Guillermo Polito wrote >>> I also wonder if we are trying to be too clever with how you specify a >>> Gitlab/Github project >> >> Maybe... but for that you have the last option "Clone remote repository" >> that allows you to just paste a url. > > This issue has come up a few times already. Does anyone have a use case for > the custom Gitlab/Github forms? If not, maybe it would be simpler for > everyone to remove them and use the generic oneâ¦ - before this, people complained in the other way - you do not always go to github and copy the url, sometimes you want to clone without putting the url (and you *know* the user and project you want to clone) So, I will not remove them. But, we could order differently (for example, offering first the generic git url). cheers! Esteban > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

June 13, 2018

hard to debug multi-threaded tests

by Ben Coman

In Pharo 5, it was possible to do... TestCase subclass: #Example ....etc Example >> test1 [ Transcript crShow: Processor activeProcess priority printString; tab; show: Processor activeProcess name. self halt. Transcript crShow: Processor activeProcess effectiveProcess priority printString; tab; show: Processor activeProcess effectiveProcess name ] forkAt: 39 named: 'TEST'. ...and when this was run, a debugger would show for the forked code and stepping through it would produce the following output... 39 TEST 39 TEST In Pharo 71047, no debugger shows up, and you only get one... 39 TEST I guess this because more cleanup of tests is being done, but it makes it harder to debug multi-threaded tests when debugger can't replicate the way the code normally runs. cheers -ben

June 13, 2018