October 2017 - Pharo-dev - lists.pharo.org

VM specific mailing list

by Raffaello Giulietti

Hi, is there a specific mailing list to discuss about Pharo's VM? Greetings Raffaello

Oct. 17, 2017

Re: [Pharo-dev] Writeup: how to contribute to Pharo

by Esteban Lorenzano

which Pharo version (and Iceberg version) do you have? Esteban > On 17 Oct 2017, at 04:36, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > Hi Guille, > > In https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to… <https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to…> > > This part is not working for me: "Go back to iceberg, right click on the pharo repository and go to the Pharo entry. You'll see the option Create new branch from Fogbugz issue." > > Because there is no such "Pharo" option in the menu. See the attached screenshot. > > Did I miss something? > Any suggestion? > > > 2017-08-10 12:17 GMT-03:00 Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>>: > Hi, > > I've made some write up for the pharo part (not metacello or external projects) > > https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to… <https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to…> > > Of course, expect bugs on it :) Not everything is smooth. If you have comments, they are welcome. > > Guille > > -- > > Guille Polito > > Research Engineer > French National Center for Scientific Research - http://www.cnrs.fr <http://www.cnrs.fr/> > > > Web: http://guillep.github.io <http://guillep.github.io/> > Phone: +33 06 52 70 66 13 > > <Clipboard01.png>

Oct. 17, 2017

Re: [Pharo-dev] Writeup: how to contribute to Pharo

by HernÃ¡n Morales Durand

Hi Guille, In https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to… This part is not working for me: "Go back to iceberg, right click on the pharo repository and go to the *Pharo* entry. You'll see the option *Create new branch from Fogbugz issue*." Because there is no such "Pharo" option in the menu. See the attached screenshot. Did I miss something? Any suggestion? 2017-08-10 12:17 GMT-03:00 Guillermo Polito <guillermopolito(a)gmail.com>: > Hi, > > I've made some write up for the pharo part (not metacello or external > projects) > > https://github.com/guillep/PharoIntegrationProcess/wiki/Cont > ribute-a-fix-to-Pharo > > Of course, expect bugs on it :) Not everything is smooth. If you have > comments, they are welcome. > > Guille > > -- > > > > Guille Polito > > > Research Engineer > > French National Center for Scientific Research - *http://www.cnrs.fr* > <http://www.cnrs.fr> > > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 >

Oct. 17, 2017

Re: [Pharo-dev] Writeup: how to contribute to Pharo

by HernÃ¡n Morales Durand

2017-08-10 18:20 GMT-03:00 Guillermo Polito <guillermopolito(a)gmail.com>: > > > On Thu, Aug 10, 2017 at 9:39 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > >> Hi Guille, >> >> nice writeup and definitely needed. Thanks a lot! >> >> If possible you should complete it with: >> - how Windows users could contribute >> > > Hard topic. I'm taking benefit of my gf's windows computer right now to > test. Basically, windows has problems with long paths but there are > workarounds. Icerberg works by default without any changes (same bugs as in > linux and osx at least :)). Here are my notes to make it work: > > * Download latest pharo: > - http://files.pharo.org/image/70/latest-32.zip > - http://files.pharo.org/vm/pharo-spur32/win/stable-20170720.zip > > * Clone using sourcetree > This is very slow and failed to checkout (not clone) because of the > "Filename too long errors" > > I found for this the following workaround: http://pingec.si/blog/ > articles/msysgit-longpath/ > > Once I did that, sourcetree worked nicely, and I could commit and change > branches using iceberg. > > Warning: I did not test making changes on the "long files" to see what > happens... > I tested it on Windows with msysgit. First you have to make the git clone $ git clone https://github.com/hernanmd/pharo.git You have to ***let it fail*** ... "fatal: unable to checkout working tree" ... Then $ cd pharo/ $ git config core.longpaths true $ git checkout -f HEAD Checking out files: 100% (107983/107983), done. Your branch is up-to-date with 'origin/development'.

Oct. 17, 2017

[Pharo 7.0-dev] Build #203: 05723-Default-Working-Directory

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

There is a new Pharo build available! The status of the build #203 was: SUCCESS. The Pull Request #92 was integrated: "05723-Default-Working-Directory" Pull request url: https://github.com/pharo-project/pharo/pull/92 Issue Url: https://pharo.fogbugz.com/f/cases/05723 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 16, 2017

Re: [Pharo-dev] Test Runner: Walkback when storing result as progress reference

by Marcus Denker

Hello, That feature is implemented in a way that it compiles code. Now if the amount of information it wants to store is large, it tries to compile code that is beyond the limits of the current byte code set (too many literals). Two things to try: -> enable the new bytecode set, it has larger limits. -> rewrite the feature to store the information differently (e.g. in nested arrays) -> maybe we should even remove the feature as it is not used a lot. Marcus > On 14 Oct 2017, at 19:55, Bernhard Pieber <bernhard(a)pieber.com> wrote: > > I just tripped over a walkback when clicking on the menu item âStore result as progress referenceâ in the Test Runner after having run all tests in a Pharo 6.1 (stable) image created by PharoLauncher 1.0.1 on macOS Sierra 10.12.6. Has anyone seen this before? > > Cheers, > Bernhard > > OpalEncoderForV3PlusClosures(Object)>>error: > OpalEncoderForV3PlusClosures(OpalBytecodeEncoder)>>outOfRangeError:index:range:to: > OpalEncoderForV3PlusClosures(OpalEncoderForV3)>>genPushLiteral: > IRBytecodeGenerator>>pushLiteral: > IRTranslatorV2>>visitPushLiteral: > IRPushLiteral>>accept: > IRTranslatorV2(IRVisitor)>>visitNode: > IRTranslatorV2>>visitInstruction: > [ :instr | self visitInstruction: instr ] in IRTranslatorV2(IRVisitor)>>visitSequence: in Block: [ :instr | self visitInstruction: instr ] > OrderedCollection>>do: > IRSequence>>do: > IRTranslatorV2(IRVisitor)>>visitSequence: > IRTranslatorV2>>visitSequence: > IRSequence>>accept: > IRTranslatorV2(IRVisitor)>>visitNode: > [ :each | self visitNode: each ] in IRTranslatorV2(IRVisitor)>>visitNodes: in Block: [ :each | self visitNode: each ] > SortedCollection(OrderedCollection)>>do: > IRTranslatorV2(IRVisitor)>>visitNodes: > IRTranslatorV2>>visitSequences: > IRTranslatorV2>>visitMethod: > IRMethod>>accept: > IRTranslatorV2(IRVisitor)>>visitNode: > IRMethod>>generate: > IRMethod>>compiledMethodWith: > RBMethodNode>>generate: > [ [ ast := self parse. > self doSemanticAnalysis. > self callPlugins ] > on: OCSourceCodeChanged > do: [ :notification | > self source: notification newSourceCode. > notification retry ]. > cm := ast generate: self compilationContext compiledMethodTrailer ] in OpalCompiler>>compile in Block: [ [ ast := self parse.... > BlockClosure>>on:do: > OpalCompiler>>compile > Metaclass(ClassDescription)>>compile:classified:withStamp:notifying:logSource: > Metaclass(ClassDescription)>>compile:classified:withStamp:notifying: > >

Oct. 16, 2017

Re: [Pharo-dev] Pharo 6.1 CompiledMethod(Object)>>doesNotUnderstand: #isMetaSide when running all tests

by Marcus Denker

Hi, We have a new bug that got introduced by some changed done in between 6.0 and 6.1. https://pharo.fogbugz.com/f/cases/20339/ <https://pharo.fogbugz.com/f/cases/20339/> I have not yet found the cause. It would be nice to fix it as it for now makes very CI test run fail. Marcus > On 14 Oct 2017, at 17:08, Bernhard Pieber <bernhard(a)pieber.com> wrote: > > Dear Pharoers, > > I encountered a DNU when I ran all tests in a new Pharo 6.1 image created with PharoLauncher 1.0.1 on macOS Sierra 10.12.6. > > Should this work or is it a known issue? What is the Pharoâs policy concerning SUnit tests for stable releases? > > Cheers, > Bernhard > > CompiledMethod(Object)>>doesNotUnderstand: #isMetaSide > [ :rgMethod | > | interestedClassName interestedClass | > interestedClassName := anAnnouncement oldName. > interestedClass := anAnnouncement classRenamed. > rgMethod isMetaSide > ifTrue: [ interestedClassName := interestedClassName , ' class'. > interestedClass := interestedClass theMetaClass ]. > rgMethod parentName = interestedClassName > ifTrue: > [ (interestedClass >> rgMethod selector) asFullRingDefinition ] > ifFalse: [ rgMethod ] ] in MessageBrowser>>handleClassRenamed: in Block: [ :rgMethod | ... > OrderedCollection>>collect: > MessageBrowser>>handleClassRenamed: > [ self handleClassRenamed: anAnnouncement ] in MessageBrowser>>classRenamed: in Block: [ self handleClassRenamed: anAnnouncement ] > WorldState>>runStepMethodsIn: > WorldMorph>>runStepMethods > WorldState>>doOneCycleNowFor: > WorldMorph>>doOneCycleNow > SystemProgressMorph>>refresh > SystemProgressMorph>>update: > MorphChanged>>deliverTo: > SystemProgressMorph(Morph)>>handleUpdate: > MessageSend>>value: > MessageSend>>cull: > MessageSend>>cull:cull: > [ action cull: anAnnouncement cull: announcer ] in AnnouncementSubscription>>deliver: in Block: [ action cull: anAnnouncement cull: announcer ] > BlockClosure>>on:do: > BlockClosure>>on:fork: > AnnouncementSubscription>>deliver: > [ "Ensure delivery to remaining announcements" subscription deliver: anAnnouncement ] in SubscriptionRegistry>>deliver:to:startingAt: in Block: [ "Ensure delivery to remaining announcements" sub...etc... > BlockClosure>>ifCurtailed: > SubscriptionRegistry>>deliver:to:startingAt: > SubscriptionRegistry>>deliver:to: > SubscriptionRegistry>>deliver: > Announcer>>announce: > JobProgressMorph(Morph)>>doAnnounce: > JobProgressMorph(Morph)>>changed: > JobProgressMorph>>label: > SystemProgressMorph class>>updateJob: > >

Oct. 16, 2017

Esteban's ChangeLog week of 9 October 2017

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 9 October 2017 to 15 October 2017. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=9/10/2017&to=15/10/2017 ChangeLog ========= 11 October 2017: ---------------- * I just integrated [case: 20492](https://pharo.fogbugz.com/f/cases/20492) (backport EPICEA changes) to Pharo6.1. This was seriously needed because the bugs were breaking some production code. 9 October 2017: --------------- * ... and after days of trying, I'm finally able to close [case: 18849](https://pharo.fogbugz.com/f/cases/18849) ! So we have an update Metacello in Pharo 7.0... and I can integrate Iceberg 0.6... tomorrow :) * I released a new version of [Iceberg (0.6.1)](https://github.com/pharo-vcs/iceberg/releases/tag/v0.6.1) This is just a bugfix release to allow install Iceberg 0.6 on Pharo 6.0. * And now I made [case: 20372](https://pharo.fogbugz.com/f/cases/20372) * Well, I started week by working a bit on Pharo 6.0 :) I just integrated [case: 20503](https://pharo.fogbugz.com/f/cases/20503) cheers! Esteban

Oct. 16, 2017

Re: [Pharo-dev] Do you think that we can do that with bloc?

by phil＠highoctane.be

There is no need for real 3D for these pages, just polygons. Phil On Sun, Oct 15, 2017 at 10:51 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > Hi Stef, > > For what you will see below, there is no official API yet, but we will > have it soon :) > > There is a way to apply a 3D transformation defined by 4x4 homogeneous > matrix on any visual element. > On the first screenshot we create a vertical 2D road which is later > rotated by 60 degrees around X-axis in 3D space on the second screenshot. > > [image: Inline images 1] > > [image: Inline images 2] > > > Cheers, > Alex > > On 15 October 2017 at 22:06, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > >> http://www.extentofthejam.com/pseudo/ >> >> Stef >> >> >

Oct. 15, 2017

Re: [Pharo-dev] Do you think that we can do that with bloc?

by Aliaksei Syrel

Hi Stef, For what you will see below, there is no official API yet, but we will have it soon :) There is a way to apply a 3D transformation defined by 4x4 homogeneous matrix on any visual element. On the first screenshot we create a vertical 2D road which is later rotated by 60 degrees around X-axis in 3D space on the second screenshot. [image: Inline images 1] [image: Inline images 2] Cheers, Alex On 15 October 2017 at 22:06, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > http://www.extentofthejam.com/pseudo/ > > Stef > >

Oct. 15, 2017