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

Apparently Zodiac plugin can crash VM on Linux

by Max Leske

Hi, I'm writing on behalf of Martin (eMBee) who's experiencing crashes when using SSL. You can find a VM crash stack trace here: http://ws.stfx.eu/AKVNLUPMPGLG. He says he hasn't updated openssl since December 15th but that the crashes started to happen only recently (within the last couple of days). I asked him to try HTTP only connections and those work. The VM crashes immediately when using SSL. To me it looks like the cuplrit is the Zodiac plugin, or at least the library it works with. His system: linux, fedora 29, and from the system reporter i get: Pharo/vms/70-x64/lib/pharo/5.0-201806281256/pharo CoInterpreter VMMaker.oscog-eem.2401 uuid: 29232e0e-c9e3-41d8-ae75-519db862e02c Jun 28 2018 StackToRegisterMappingCogit VMMaker.oscog-eem.2401 uuid: 29232e0e-c9e3-41d8-ae75-519db862e02c Jun 28 2018 VM: 201806281256 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Thu Jun 28 14:56:30 2018 CommitHash: a8a1dc1 Plugins: 201806281256 https://github.com/OpenSmalltalk/opensmalltalk-vm.git cheers, Max

Jan. 15, 2019

Re: [Pharo-dev] wish for p8: parserewriter UI

by ducasse

> On 15 Jan 2019, at 20:34, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > Le 15/01/2019 Ã 20:25, StÃ©phane Ducasse via Pharo-dev a Ã©crit : > > Wasn't it the work of Mark Rizun? First we should have something super simple: Package List Selection or class list selection one expression => a list of method found or a list of method rewrote like in the original RB tools https://refactory.com/tools/refactoring-browser/rewrite-tool Second we can integrate the tool of Yuriy to help us write some patterns. Third we could add the one mark. Stef > > -- > Cyril Ferlicot > https://ferlicot.fr >

Jan. 15, 2019

Re: [Pharo-dev] I am abandoning SqueakSource3, any takers?

by Tobias Pape

Hi, Sorry, I'm again late to reply. > On 05.01.2019, at 22:35, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi Tobi, > > On Sat, Jan 5, 2019 at 1:28 PM Tobias Pape <Das.Linux(a)gmx.de> wrote: > Hi all, > > since there's not a lot interest anymore in SqueakSource3, I'm giving up maintenanceship. > > Here's the project: > http://squeaksource.com/squeaksource3.html > Here's the current bug tracker: > https://github.com/krono/squeaksource3/issues > > It runs on Squeak, GemStone, and Pharo. > > There are a few instances out there, running without any problems. > > What are the instances? If I depend on any I may have to take upon maintainership ;-) The instances are: http://ss3.gemtalksystems.com/ http://www.hpi.uni-potsdam.de/hirschfeld/squeaksource (btw: the only MC repo I know that can serve via https ;)) https://sdk.krestianstvo.org/sdk/ (running the latest version) I already shut down my own instances. Best regards -Tobias > > Any Takers? > -t > > _,,,^..^,,,_ > best, Eliot

Jan. 15, 2019

Re: [Pharo-dev] wish for p8: parserewriter UI

by Cyril Ferlicot D.

Le 15/01/2019 Ã 20:25, StÃ©phane Ducasse via Pharo-dev a Ã©critÂ : Wasn't it the work of Mark Rizun? -- Cyril Ferlicot https://ferlicot.fr

Jan. 15, 2019

wish for p8: parserewriter UI

by StÃ©phane Ducasse

Hi Iâm rewriting around 400 methods following a pattern that the parsetree rewritter could easily transform for me and I would love to have a UI and integrate the tools did by Yuriy to understand patterns as a default tool in the tool ecosystem. stef -------------------------------------------- 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. 15, 2019

Re: [Pharo-dev] Bad baseline practices

by Cyril Ferlicot

On Tue, Jan 15, 2019 at 6:03 PM Stephan Eggermont via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > > Iâm not sure why, but Iâve noticed baselines being changed to refer to > patch versions for releases. Why are the old configuration problems > repeated? Which project are you talking about? > > Stephan > > -- Cyril Ferlicot https://ferlicot.fr

Jan. 15, 2019

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

by Esteban Lorenzano

Ok, it has to be me :) Esteban > On 15 Jan 2019, at 16:36, Martin Dias <tinchodias(a)gmail.com> wrote: > > 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

Bad baseline practices

by Stephan Eggermont

Iâm not sure why, but Iâve noticed baselines being changed to refer to patch versions for releases. Why are the old configuration problems repeated? Stephan

Jan. 15, 2019

Re: [Pharo-dev] Managing of P7/P8

by Cyril Ferlicot

On Tue, Jan 15, 2019 at 4:38 PM Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi, > Hello, > as Pharo 8 development started I wonder: > > 1. When will it be possible to already get a Pharo 8 latest image > from ZeroConf. Because one requires ideally the latest image to contribute > - no? > I guess zeroconf for P8 will be set after Pharo 7 release. For now I get manually a Pharo 8 image from files.pharo.org and I use the Pharo 7 VM to contribute. > Or should one search/download from the CI server for the time being (which > would be cumbersome) > > 2. How will contributions still going to P7 handled regarding P8. > Typically a bugfix for P7 should also go into the P8 image - no? > But from the integration mails floating around I do not see > this is happening. > There is only few fixex that will still be integrated in P7 for the release. While the Pharo 7 development is still active there is often a merge of the P7 branch in the P8 branch to keep them up to date. After P7 I guess backported issues will be integrated in the P7 and P8 branches. > I would expect that a PR for Pharo 7 would also be merged into Pharo 8 branch. > If not the images could easily diverge too much or done fixes for P7 will not be in P8. > > Thanks in advance for clarification! > > Bye > T. > > -- Cyril Ferlicot https://ferlicot.fr

Jan. 15, 2019

Managing of P7/P8

by Torsten Bergmann

Hi, as Pharo 8 development started I wonder: 1. When will it be possible to already get a Pharo 8 latest image from ZeroConf. Because one requires ideally the latest image to contribute - no? Or should one search/download from the CI server for the time being (which would be cumbersome) 2. How will contributions still going to P7 handled regarding P8. Typically a bugfix for P7 should also go into the P8 image - no? But from the integration mails floating around I do not see this is happening. I would expect that a PR for Pharo 7 would also be merged into Pharo 8 branch. If not the images could easily diverge too much or done fixes for P7 will not be in P8. Thanks in advance for clarification! Bye T.

Jan. 15, 2019