January 2019 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] A problem with latest image (64bit) ? (Please confirm)

by Martin Dias

Hi, I iouldn't reproduce in macos mojave. I downloaded with: curl https://get.pharo.org/64/70+vmLatest | bash And no problem with Stdio stdout << âOKâ Report: --- Pharo7.0.0rc1 Build information: Pharo-7.0.0+rc1.build.122.sha.51ac9cae0485c8cbcf23a1bc54c2291a5890c885 (64 Bit) Unnamed CoInterpreter VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019 StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019 VM: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Sat Jan 5 20:00:11 2019 CommitHash: 7a3c6b6 Plugins: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Mac OS X built on Jan 5 2019 19:11:02 UTC Compiler: 4.2.1 Compatible Apple LLVM 7.3.0 (clang-703.0.31) VMMaker versionString VM: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Sat Jan 5 20:00:11 2019 CommitHash: 7a3c6b6 Plugins: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git CoInterpreter VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019 StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019 --- MartÃn El mar., 15 de ene. de 2019 a la(s) 09:06, Esteban Lorenzano (estebanlm(a)gmail.com) escribiÃ³: > > Thing is, it happens also with an older VM :( > > Esteban > > > On 15 Jan 2019, at 13:00, Max Leske <maxleske(a)gmail.com> wrote: > > > > Actually, I think it's rather a VM problem...? > > > > > > On 15 Jan 2019, at 12:30, Esteban Lorenzano wrote: > > > >> Hello, > >> > >> Iâm experiencing a problem with latest image (and latest vm) in Mac (Mojave). > >> After doing > >> > >> Stdio stdout << âOKâ > >> > >> Iâm having this stack: > >> > >> File class(ProtoObject)>>primitiveFailed: > >> File class(ProtoObject)>>primitiveFailed > >> File class>>fileDescriptorType: > >> File class>>fileDescriptorIsAvailable: > >> Stdio class>>standardIOStreamNamed:forWrite: > >> Stdio class>>stdout > >> UndefinedObject>>DoIt > >> OpalCompiler>>evaluate > >> RubSmalltalkEditor>>evaluate:andDo: > >> RubSmalltalkEditor>>highlightEvaluateAndDo: > >> GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>popupPrint > >> MorphicAlarm(MessageSend)>>value > >> MorphicAlarm>>value: > >> WorldState>>triggerAlarmsBefore: > >> WorldState>>runLocalStepMethodsIn: > >> WorldState>>runStepMethodsIn: > >> WorldMorph>>runStepMethods > >> WorldState>>doOneCycleNowFor: > >> WorldState>>doOneCycleFor: > >> WorldMorph>>doOneCycle > >> WorldMorph class>>doOneCycle > >> [ [ WorldMorph doOneCycle. > >> Processor yield. > >> false ] whileFalse: [ ] ] in MorphicUIManager>>spawnNewProcess in Block: [ [ WorldMorph doOneCycle.... > >> [ self value. > >> Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value.... > >> > >> Con someone confirm or refute this? > >> > >> Thanks! > >> Esteban > > > >

Jan. 15, 2019

[Pharo 7.0] Build #122: 22894-Unecessary-dialogs-during-refactorings

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

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

Jan. 15, 2019

[Pharo 8.0] Build #11: 2242-Sync-Pharo-7-and-8

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

There is a new Pharo build available! The status of the build #11 was: SUCCESS. The Pull Request #2243 was integrated: "2242-Sync-Pharo-7-and-8" Pull request url: https://github.com/pharo-project/pharo/pull/2243 Issue Url: https://pharo.fogbugz.com/f/cases/2242 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 15, 2019

Re: [Pharo-dev] A problem with latest image (64bit) ? (Please confirm)

by Esteban Lorenzano

Thing is, it happens also with an older VM :( Esteban > On 15 Jan 2019, at 13:00, Max Leske <maxleske(a)gmail.com> wrote: > > Actually, I think it's rather a VM problem...? > > > On 15 Jan 2019, at 12:30, Esteban Lorenzano wrote: > >> Hello, >> >> Iâm experiencing a problem with latest image (and latest vm) in Mac (Mojave). >> After doing >> >> Stdio stdout << âOKâ >> >> Iâm having this stack: >> >> File class(ProtoObject)>>primitiveFailed: >> File class(ProtoObject)>>primitiveFailed >> File class>>fileDescriptorType: >> File class>>fileDescriptorIsAvailable: >> Stdio class>>standardIOStreamNamed:forWrite: >> Stdio class>>stdout >> UndefinedObject>>DoIt >> OpalCompiler>>evaluate >> RubSmalltalkEditor>>evaluate:andDo: >> RubSmalltalkEditor>>highlightEvaluateAndDo: >> GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>popupPrint >> MorphicAlarm(MessageSend)>>value >> MorphicAlarm>>value: >> WorldState>>triggerAlarmsBefore: >> WorldState>>runLocalStepMethodsIn: >> WorldState>>runStepMethodsIn: >> WorldMorph>>runStepMethods >> WorldState>>doOneCycleNowFor: >> WorldState>>doOneCycleFor: >> WorldMorph>>doOneCycle >> WorldMorph class>>doOneCycle >> [ [ WorldMorph doOneCycle. >> Processor yield. >> false ] whileFalse: [ ] ] in MorphicUIManager>>spawnNewProcess in Block: [ [ WorldMorph doOneCycle.... >> [ self value. >> Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value.... >> >> Con someone confirm or refute this? >> >> Thanks! >> Esteban >

Jan. 15, 2019

Re: [Pharo-dev] A problem with latest image (64bit) ? (Please confirm)

by Max Leske

Actually, I think it's rather a VM problem...? On 15 Jan 2019, at 12:30, Esteban Lorenzano wrote: > Hello, > > Iâm experiencing a problem with latest image (and latest vm) in Mac > (Mojave). > After doing > > Stdio stdout << âOKâ > > Iâm having this stack: > > File class(ProtoObject)>>primitiveFailed: > File class(ProtoObject)>>primitiveFailed > File class>>fileDescriptorType: > File class>>fileDescriptorIsAvailable: > Stdio class>>standardIOStreamNamed:forWrite: > Stdio class>>stdout > UndefinedObject>>DoIt > OpalCompiler>>evaluate > RubSmalltalkEditor>>evaluate:andDo: > RubSmalltalkEditor>>highlightEvaluateAndDo: > GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>popupPrint > MorphicAlarm(MessageSend)>>value > MorphicAlarm>>value: > WorldState>>triggerAlarmsBefore: > WorldState>>runLocalStepMethodsIn: > WorldState>>runStepMethodsIn: > WorldMorph>>runStepMethods > WorldState>>doOneCycleNowFor: > WorldState>>doOneCycleFor: > WorldMorph>>doOneCycle > WorldMorph class>>doOneCycle > [ [ WorldMorph doOneCycle. > Processor yield. > false ] whileFalse: [ ] ] in MorphicUIManager>>spawnNewProcess in > Block: [ [ WorldMorph doOneCycle.... > [ self value. > Processor terminateActive ] in BlockClosure>>newProcess in Block: [ > self value.... > > Con someone confirm or refute this? > > Thanks! > Esteban

Jan. 15, 2019

Re: [Pharo-dev] A problem with latest image (64bit) ? (Please confirm)

by Max Leske

I've been seeing this in the early Pharo 7 builds. But it didn't occur with latest VM's, only with SmalltalkCI, so I ignored it. On 15 Jan 2019, at 12:30, Esteban Lorenzano wrote: > Hello, > > Iâm experiencing a problem with latest image (and latest vm) in Mac > (Mojave). > After doing > > Stdio stdout << âOKâ > > Iâm having this stack: > > File class(ProtoObject)>>primitiveFailed: > File class(ProtoObject)>>primitiveFailed > File class>>fileDescriptorType: > File class>>fileDescriptorIsAvailable: > Stdio class>>standardIOStreamNamed:forWrite: > Stdio class>>stdout > UndefinedObject>>DoIt > OpalCompiler>>evaluate > RubSmalltalkEditor>>evaluate:andDo: > RubSmalltalkEditor>>highlightEvaluateAndDo: > GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>popupPrint > MorphicAlarm(MessageSend)>>value > MorphicAlarm>>value: > WorldState>>triggerAlarmsBefore: > WorldState>>runLocalStepMethodsIn: > WorldState>>runStepMethodsIn: > WorldMorph>>runStepMethods > WorldState>>doOneCycleNowFor: > WorldState>>doOneCycleFor: > WorldMorph>>doOneCycle > WorldMorph class>>doOneCycle > [ [ WorldMorph doOneCycle. > Processor yield. > false ] whileFalse: [ ] ] in MorphicUIManager>>spawnNewProcess in > Block: [ [ WorldMorph doOneCycle.... > [ self value. > Processor terminateActive ] in BlockClosure>>newProcess in Block: [ > self value.... > > Con someone confirm or refute this? > > Thanks! > Esteban

Jan. 15, 2019

Re: [Pharo-dev] A problem with latest image (64bit) ? (Please confirm)

by Gabriel Cotelli

At least on Linux (with the latest VM and image downloaded for zero conf) it's working fine. Image ----- Pharo7.0.0rc1 Build information: Pharo-7.0.0+rc1.build.121.sha.0640e0d300e69541033fb1c4270c9b0d7d401b01 (64 Bit) Unnamed Virtual Machine --------------- pharo-vm/lib/pharo/5.0-201901100922/pharo CoInterpreter VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 10 2019 StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 10 2019 VM: 201901100922 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Thu Jan 10 10:22:25 2019 CommitHash: 58ffe032 Plugins: 201901100922 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Unix built on Jan 10 2019 09:32:18 Compiler: 4.8.4 VMMaker versionString VM: 201901100922 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Thu Jan 10 10:22:25 2019 CommitHash: 58ffe032 Plugins: 201901100922 https://github.com/OpenSmalltalk/opensmalltalk-vm.git CoInterpreter VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 10 2019 StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 10 2019 Operating System/Hardware ------------------------- unix linux-gnu x86_64 On Tue, Jan 15, 2019 at 8:31 AM Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hello, > > Iâm experiencing a problem with latest image (and latest vm) in Mac > (Mojave). > After doing > > Stdio stdout << âOKâ > > Iâm having this stack: > > File class(ProtoObject)>>primitiveFailed: > File class(ProtoObject)>>primitiveFailed > File class>>fileDescriptorType: > File class>>fileDescriptorIsAvailable: > Stdio class>>standardIOStreamNamed:forWrite: > Stdio class>>stdout > UndefinedObject>>DoIt > OpalCompiler>>evaluate > RubSmalltalkEditor>>evaluate:andDo: > RubSmalltalkEditor>>highlightEvaluateAndDo: > GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>popupPrint > MorphicAlarm(MessageSend)>>value > MorphicAlarm>>value: > WorldState>>triggerAlarmsBefore: > WorldState>>runLocalStepMethodsIn: > WorldState>>runStepMethodsIn: > WorldMorph>>runStepMethods > WorldState>>doOneCycleNowFor: > WorldState>>doOneCycleFor: > WorldMorph>>doOneCycle > WorldMorph class>>doOneCycle > [ [ WorldMorph doOneCycle. > Processor yield. > false ] whileFalse: [ ] ] in MorphicUIManager>>spawnNewProcess in Block: > [ [ WorldMorph doOneCycle.... > [ self value. > Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self > value.... > > Con someone confirm or refute this? > > Thanks! > Esteban >

Jan. 15, 2019

A problem with latest image (64bit) ? (Please confirm)

by Esteban Lorenzano

Hello, Iâm experiencing a problem with latest image (and latest vm) in Mac (Mojave). After doing Stdio stdout << âOKâ Iâm having this stack: File class(ProtoObject)>>primitiveFailed: File class(ProtoObject)>>primitiveFailed File class>>fileDescriptorType: File class>>fileDescriptorIsAvailable: Stdio class>>standardIOStreamNamed:forWrite: Stdio class>>stdout UndefinedObject>>DoIt OpalCompiler>>evaluate RubSmalltalkEditor>>evaluate:andDo: RubSmalltalkEditor>>highlightEvaluateAndDo: GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>popupPrint MorphicAlarm(MessageSend)>>value MorphicAlarm>>value: WorldState>>triggerAlarmsBefore: WorldState>>runLocalStepMethodsIn: WorldState>>runStepMethodsIn: WorldMorph>>runStepMethods WorldState>>doOneCycleNowFor: WorldState>>doOneCycleFor: WorldMorph>>doOneCycle WorldMorph class>>doOneCycle [ [ WorldMorph doOneCycle. Processor yield. false ] whileFalse: [ ] ] in MorphicUIManager>>spawnNewProcess in Block: [ [ WorldMorph doOneCycle.... [ self value. Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value.... Con someone confirm or refute this? Thanks! Esteban

Jan. 15, 2019

Re: [Pharo-dev] Availability of Smallapack in Pharo6.0

by StÃ©phane Ducasse

> > Hi Denis, > OK, but hiding is troubling... > When I came from VW, I found that Squeak categories matching package names was a quick and dirty hack. > Since then, I find it works remarkably well, it is somehow a declarative meta information (method property), and I much prefer that to hidden package classification accessible from an IDE only. I agree :) and I told that several times in the past :) We also lost the inplace edit and the logic sometimes is super confusing. > It still happens to me to loose methods in VW because they are not packaged or wrongly packaged, so I'm not sure that cleaning is winning in that case. > And if you go with multiple classifications, then there's no reason to not keep the hack. For now multiple classifications is not in our priority since our list is already too long. > > But I'll come back to it, tools are generally better in ph7 than ph6. Stay tuned. -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Jan. 14, 2019

About resurrecting the RE package and plugin

by ducasse

Hi I would really like to resurrect the REPlugin and its image side abstraction because I think that this is important to support Perl level regex since it will help people to reuse their knowledge. If you are interested in helping let us know. Stef

Jan. 14, 2019