- Pharo-dev - lists.pharo.org

[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

Do you think that we can do that with bloc?

by Stephane Ducasse

http://www.extentofthejam.com/pseudo/ Stef

Oct. 15, 2017

Re: [Pharo-dev] PharoMinimal ?

by Hilaire

Le 14/10/2017 Ã 23:24, Pavel Krivanek a Ã©critÂ : > Reduction of image size is only a side effect, not our main goal. It > can probably be cleaned more and with conversion to Spur all images > are bigger now. Do you know that there was a version of Cuis that had > working Morphic in image of size only 2MB? > No I did not. Thanks I will take a look. -- Dr. Geo http://drgeo.eu

Oct. 14, 2017

Re: [Pharo-dev] PharoMinimal ?

by Pavel Krivanek

2017-10-14 22:58 GMT+02:00 Hilaire <hilaire(a)drgeo.eu>: > Ok. > > Earlier DrGeo image based on pharo (around 2010 time) shrinked around > 8MB[1], Morph included. > Reduction of image size is only a side effect, not our main goal. It can probably be cleaned more and with conversion to Spur all images are bigger now. Do you know that there was a version of Cuis that had working Morphic in image of size only 2MB? http://www.jvuletich.org/Cuis/Cuis3.1r3.zip use sources from: http://www.jvuletich.org/Cuis/Cuis3.1-0850.zip -- Pavel > > [1] https://gforge.inria.fr/frs/download.php/file/27318/DrGeo.ap > p-10.08.zip > > > Le 14/10/2017 Ã 22:26, Pavel Krivanek a Ã©crit : > >> >> 2017-10-14 22:04 GMT+02:00 Hilaire <hilaire(a)drgeo.eu <mailto: >> hilaire(a)drgeo.eu>>: >> >> At this image size, does it come with Morph? >> >> >> No, Morphic is not included. >> >> -- Pavel >> > > -- > Dr. Geo > http://drgeo.eu > > > >

Oct. 14, 2017

Re: [Pharo-dev] PharoMinimal ?

by Hilaire

Ok. Earlier DrGeo image based on pharo (around 2010 time) shrinked around 8MB[1], Morph included. [1] https://gforge.inria.fr/frs/download.php/file/27318/DrGeo.app-10.08.zip Le 14/10/2017 Ã 22:26, Pavel Krivanek a Ã©critÂ : > > 2017-10-14 22:04 GMT+02:00 Hilaire > <hilaire(a)drgeo.eu > <mailto:hilaire@drgeo.eu>>: > > At this image size, does it come with Morph? > > > No, Morphic is not included. > > -- Pavel -- Dr. Geo http://drgeo.eu

Oct. 14, 2017