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

Re: [Pharo-dev] Creating the smallest server runtime footprint

by Pavel Krivanek

It it were packages from the development branch then you do not need to flatten them. -- Pavel 2017-08-04 15:52 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: > Hi Pavel - When you say âpackages from the Pharo repoâ - I think Iâm doing > that - yesterday I cloned the Pharo repo and then I copied the Fuel > packages you guys suggested over into my branch (not elegant, but simple). > > So I should have the flattened versions then? > > (I have now managed to get the P7 image working - so thanks for all your > help, but Iâm curious about this part) > > Tim > > On 4 Aug 2017, at 12:49, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > Hmm, Pharo 7 has flattened traits in the kernel, but it still supports > them. So probably because you are using vanilla Fuel packages, they extend > traits that are not used for real. You should use packages from the Pharo > repository. > > -- Pavel > > 2017-08-04 13:42 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: > >> Sadly - false call, that was my logging message - so Iâm stumped why >> these traits arenât being compiled when I load in Fuel? >> >> However I have figured out why I get the BigEndian error - this is >> because the platform is now 7 and so the FlPharo06Platform is not being >> identified and the more generic FlPharoPlatform is then the default and it >> doesnât implement #isBigEndian. >> >> Tim >> >> >> >> On 4 Aug 2017, at 12:20, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Iâve spotted something interesting in my logs - when I added one of the >> missing methods to ClassDescription - I see in the log the message: >> >> Loaded -> Fuel-cypress.1 --- filetree:///builds/macta/Pharo >> Lambda/bootstrap --- cache >> ...finished baseline >> Compiling missing traits... >> Evaluating post load initialization... >> Finished Script. >> >> However when I remove all the compiles I donât see this message: >> >> Loaded -> Fuel-cypress.1 --- filetree:///builds/macta/Pharo >> Lambda/bootstrap --- cache >> ...finished baseline >> Evaluating post load initialization... >> Finished Script. >> >> >> So I wonder if this is similar to the problem I had in the previous 6.0 >> image - where some things didnât seem to compile properly (in that case, it >> was loading a missing class that didnât seem to cause recompilation). >> >> Tim >> >> On 4 Aug 2017, at 11:10, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Actually there is something weird going on - as now Iâm getting a >> complaint about "FLPharoPlatform had the subclass responsibility to >> implement #isBigEndianâ, and thatâs in the FuelPlatform-Pharo-06 which you >> said to include (and it looks like I am). >> >> I need to double check this - as I must be making some trivial mistake. >> >> Tim >> >> On 4 Aug 2017, at 11:01, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Hi Mariano - Iâve looked at this again, and it was my fault - I was >> compiling in : >> >> fuelAccept: aGeneralMapper >> ^self explicitRequirement. >> >> Because when I looked at the Traits for fuel - this is what it had for >> TClass? - as Iâm not so clear on traits, what does this mean - as I had >> just assumed that I should flatten the Fuel methods for TCLass, TBehaviour >> and TClassDescription - but I think Iâve misunderstood what I should do >> (and I guess from Pavelâs comment - I should really look at why that >> initial method was missing as it sounds like it should have worked - so >> maybe its an order loading thing?). >> >> Thanks, for helping by the way - this is proving very instructional. >> >> Tim >> >> On 3 Aug 2017, at 18:26, Mariano Martinez Peck <marianopeck(a)gmail.com> >> wrote: >> >> >> On Thu, Aug 3, 2017 at 2:14 PM, Tim Mackinnon <tim(a)testit.works> wrote: >> >>> Hi Mariano - I compiled in the trait methods manually and it got further >>> - but now Iâm seeing another error - Error: Explicitly required method", >>> "\u001b[0mLambda class(Object)>>error:", >>> "explicitRequirementâ, >>> >>> >> mmmm the stack is weird... it looks like if Class >> fuelAccept: would >> have the wrong implementation, that is, having the one from TClass: >> >> fuelAccept: aGeneralMapper >> ^self explicitRequirement. >> >> Rather than the correct one: >> >> fuelAccept: aGeneralMapper >> >> ^aGeneralMapper visitClass: self >> >> >> *Maybe the solution is to compile all those methods from traits BUT NOT >> those that are "^self explicitRequirement." because those will override the >> good methods.* >> >> If that doesn't work, then maybe can you print to console the each impl >> (source) of each implementor of #fuelAccept: ? >> >> Thoughts? >> >> >> >> >> >>> Any ideas? >>> >>> Tim >>> >>> "--- RUNNING ERROR HANDLER ---", >>> "Error: Explicitly required method", >>> "", >>> "\u001b[0m\u001b[31mError: Explicitly required method", >>> "\u001b[0mLambda class(Object)>>error:", >>> "explicitRequirement", >>> " self error: 'No decompiler available' in Lambda class(Object)>>explicitRequirement in Block: explicitRequirement...", >>> "False>>ifFalse:", >>> "Lambda class(Object)>>explicitRequirement", >>> "Lambda class(Class)>>fuelAccept:", >>> "FLLightGeneralMapper>>mapAndTrace:", >>> "FLLightGlobalMapper>>mapAndTrace:", >>> "FLPluggableSubstitutionMapper>>mapAndTrace:", >>> "FLAnalysis>>mapAndTrace:", >>> "FLAnalysis>>run", >>> "setDefaultAnalysis", >>> " self error: 'No decompiler available' in FLAnalyzer>>setDefaultAnalysis in Block: setDefaultAnalysis...", >>> "FLAnalyzer>>analysisFor:", >>> "FLSerialization>>analysisStep", >>> "FLSerialization>>run", >>> "setDefaultSerialization", >>> " self error: 'No decompiler available' in FLSerializer>>setDefaultSerialization in Block: setDefaultSerialization...", >>> "serialize: t1 on: t2", >>> " self error: 'No decompiler available' in FLSerializer>>serialize:on: in Block: serialize: t1 on: t2...", >>> "on: t1 globalEnvironment: t2 do: t3", >>> " self error: 'No decompiler available' in FLEncoder class>>on:globalEnvironment:do: in Block: on: t1 globalEnvironment: t2 do: t3...", >>> "BlockClosure>>ensure:", >>> "FLEncoder class>>on:globalEnvironment:do:", >>> "FLSerializer>>serialize:on:", >>> "NonInteractiveUIManager>>writeFuelContext:", >>> "Lambda class>>processDebug:", >>> "Lambda class>>processJSON:", >>> "Lambda class>>process:", >>> "activate", >>> >>> >>> On 3 Aug 2017, at 17:26, Mariano Martinez Peck <marianopeck(a)gmail.com> >>> wrote: >>> >>> >>> >>> On Thu, Aug 3, 2017 at 1:17 PM, Tim Mackinnon <tim(a)testit.works> wrote: >>> >>>> Hi guys - I think Iâm getting close - Iâm able to load remote packages, >>>> and Iâve added fuel to my repo and its loading - however I am getting an >>>> error when I run and test writing out a context - *MessageNotUnderstood: >>>> Context class>>fuelIgnoredInstanceVariableNames* >>>> >>>> I can see that this is a trait - is trait support missing in the >>>> minimal image? >>>> >>>> >>> Uff...that's a good question hahahhah >>> I don't know if the minimal image supports traits, but what I am almost >>> sure, is the Behavior DOES need the methods defined in TBehavior. So maybe >>> the minimal image flattens the traits. In this case you could do the same >>> for Fuel (flattenDownAllTraits) >>> >>> >>>> (I also seemed to get this far just loading the Fuel package - but just >>>> to be sure I added the other platform ones like you suggested and still get >>>> the same error). Given how simple that method is, I could just compile it >>>> in - but maybe there are many more? >>>> >>>> >>> >>> TBehavior, TClass and TClassDescription are the only one that comes to >>> my mind right now... there are only a few methods from Fuel. So could >>> compile those directly at least on a first step...at least you keep you >>> going. >>> >>> >>> >>> >>> >>>> Tim >>>> >>>> >>>> "errorMessage": "Command failed: ./pharo Pharo.image >>>> --no-default-preferences process Lambda '{\"debug\":true,\"data\":5}'\n >>>> "errorType": "Error", >>>> "stackTrace": [ >>>> "Writing fuel context to S3...", >>>> "Using S3 bucket morethan-technology-projects", >>>> "\u001b[31m", >>>> "--- RUNNING ERROR HANDLER ---", >>>> "*MessageNotUnderstood: Context >>>> class>>fuelIgnoredInstanceVariableNames*", >>>> "", >>>> "\u001b[0m\u001b[31mMessageNotUnderstood: Context >>>> class>>fuelIgnoredInstanceVariableNames", >>>> "\u001b[0mContext class(Object)>>doesNotUnderstand: >>>> #fuelIgnoredInstanceVariableNames", >>>> "FLVariablesMapping>>instanceVariableNamesToSerialize", >>>> "FLVariablesMapping>>initializeAnalyzing", >>>> "FLVariablesMapping class>>newAnalyzing:references:", >>>> "FLContextCluster(FLPointerObjectCluster)>>initializeAnalyzing:", >>>> "FLContextCluster class(FLObjectCluster class)>>newAnalyzing:", >>>> "clusterKeyedByObjectClass: t1 class: t2", >>>> " self error: 'No decompiler available' in >>>> FLLightGeneralMapper(FLMapper)>>clusterKeyedByObjectClass:class: in >>>> Block: clusterKeyedByObjectClass: t1 class: t2...", >>>> "clusterInstanceOf: t1 keyInBucket: t2 factory: t3", >>>> " self error: 'No decompiler available' in >>>> FLLightGeneralMapper(FLMapper)>>clusterInstanceOf:keyInBucket:factory: >>>> in Block: clusterInstanceOf: t1 keyInBucket: t2 factory: t3...", >>>> "at: t1 ifAbsentPut: t2", >>>> " self error: 'No decompiler available' in >>>> IdentityDictionary(Dictionary)>>at:ifAbsentPut: in Block: at: t1 >>>> ifAbsentPut: t2...", >>>> "IdentityDictionary(Dictionary)>>at:ifAbsent:", >>>> "IdentityDictionary(Dictionary)>>at:ifAbsentPut:", >>>> "FLLightGeneralMapper(FLMapper)>>clusterInstanceOf:keyInBu >>>> cket:factory:", >>>> "FLLightGeneralMapper(FLMapper)>>clusterKeyedByObjectClass:class:", >>>> "FLLightGeneralMapper(FLMapper)>>mapAndTraceByObjectClass:to:", >>>> "FLLightGeneralMapper>>visitMethodContext:", >>>> "Context>>fuelAccept:", >>>> "FLLightGeneralMapper>>mapAndTrace:", >>>> "FLLightGlobalMapper>>mapAndTrace:", >>>> "FLPluggableSubstitutionMapper>>mapAndTrace:", >>>> "FLAnalysis>>mapAndTrace:", >>>> "FLAnalysis>>run", >>>> "setDefaultAnalysis", >>>> " self error: 'No decompiler available' in >>>> FLAnalyzer>>setDefaultAnalysis in Block: setDefaultAnalysis...", >>>> "FLAnalyzer>>analysisFor:", >>>> "FLSerialization>>analysisStep", >>>> "FLSerialization>>run", >>>> "setDefaultSerialization", >>>> " self error: 'No decompiler available' in >>>> FLSerializer>>setDefaultSerialization in Block: >>>> setDefaultSerialization...", >>>> "serialize: t1 on: t2", >>>> " self error: 'No decompiler available' in >>>> FLSerializer>>serialize:on: in Block: serialize: t1 on: t2...", >>>> "on: t1 globalEnvironment: t2 do: t3", >>>> " self error: 'No decompiler available' in FLEncoder >>>> class>>on:globalEnvironment:do: in Block: on: t1 globalEnvironment: t2 >>>> do: t3...", >>>> "BlockClosure>>ensure:", >>>> "FLEncoder class>>on:globalEnvironment:do:", >>>> "\u001b[0m" >>>> >>>> On 3 Aug 2017, at 13:16, Mariano Martinez Peck <marianopeck(a)gmail.com> >>>> wrote: >>>> >>>> >>>> >>>> On Thu, Aug 3, 2017 at 8:58 AM, Tim Mackinnon <tim(a)testit.works> wrote: >>>> >>>>> Iâm so close now (bit of a diversion with gitlab yml not liking the >>>>> eval string) - that did load and it got me really close - Iâm just missing >>>>> FlSerializer now (I have progressed my work to fuel out the context for >>>>> debugging to S3)â¦ so looking at the repo, there are quite a few fuel >>>>> packages - but in a big image I can see that FLSerialiser is in Core - so >>>>> do I just need core? But then there are a few fuel packages with Core? >>>>> >>>>> >>>> The easiest way to understand that is either checking >>>> ConfigurationOfFuel directly or some of the related Metacello tool. >>>> Anyway, for this case, I think you need the packages (in this order): >>>> FuelPlatform and Fuel. Bug again, Metacello allows some postLoad actions >>>> (which we use in Fuel)... so...it's not always easy to load a project >>>> without Metacello. >>>> >>>> Sometimes you can print the result of #record: >>>> >>>> Metacello new >>>> configuration: 'Fuel'; >>>> smalltalkhubUser: 'Pharo' project: 'Fuel'; >>>> version: #stable; >>>> record: #('Core'). >>>> >>>> -> >>>> >>>> "linear load : >>>> linear load : 2.1.10 [ConfigurationOfFuel] >>>> linear load : baseline [ConfigurationOfFuelPlatform] >>>> load : FuelPlatform-Core >>>> load : FuelPlatform-Pharo-Core >>>> load : FuelPlatform-Pharo-06" >>>> >>>> >>>> ------ >>>> >>>> Anyway.... I guess I would try to load these packages (in this order): >>>> >>>> FuelPlatform-Core >>>> FuelPlatform-Pharo-Core >>>> FuelPlatform-Pharo-06 >>>> Fuel >>>> >>>> And when you are down loading, then execute: >>>> >>>> (Smalltalk at: #FLPlatform) current addHacks >>>> >>>> >>>> >>>>> Iâm also not quite clear on how I would load packages without a >>>>> Baseline (would I create my own baseline for the fuel packages I need?) >>>>> >>>>> Tim >>>>> >>>>> On 3 Aug 2017, at 12:07, Pavel Krivanek <pavel.krivanek(a)gmail.com> >>>>> wrote: >>>>> >>>>> >>>>> >>>>> 2017-08-03 13:02 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: >>>>> >>>>>> I really appreciate your patience and help on this - it looks very >>>>>> promising and I am giving it a spin nowâ¦ >>>>>> >>>>>> When you say the pharo repository - are you referring to this: >>>>>> https://github.com/pharo-project/pharo/tree/master/src. ? Just so I >>>>>> know for the future. >>>>>> >>>>> >>>>> yes >>>>> >>>>> -- Pavel >>>>> >>>>>> >>>>>> >>>>>> Tim >>>>>> >>>>>> On 3 Aug 2017, at 09:16, Pavel Krivanek <pavel.krivanek(a)gmail.com> >>>>>> wrote: >>>>>> >>>>>> >>>>>> >>>>>> 2017-08-03 10:14 GMT+02:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: >>>>>> >>>>>>> The easiest think you can do is to copy to your repository (or some >>>>>>> other) related packages from the Pharo repository (to do not have to clone >>>>>>> it all): >>>>>>> >>>>>>> Metacello-GitBasedRepository.package >>>>>>> Metacello-GitHub.package >>>>>>> SUnit-Core.package >>>>>>> >>>>>>> and create baseline to load them. I already tried it so you can test >>>>>>> it: >>>>>>> https://drive.google.com/open?id=0BzSsmZhqtUTeMVJacTZtdW5UQW8 >>>>>>> >>>>>>> Then you will do something like: >>>>>>> >>>>>> >>>>>> (accidental message send ;-) ) >>>>>> >>>>>> BASELINE=MetacelloGitBasedRepository >>>>>> pharo "$IMAGE_NAME.image" --no-default-preferences eval --save \ >>>>>> "Metacello new baseline: '$BASELINE'; repository: ' >>>>>> filetree://./PharoLambda/src'; load." >>>>>> >>>>>> BASELINE=Lambda >>>>>> pharo "$IMAGE_NAME.image" --no-default-preferences eval --save \ >>>>>> "Metacello new baseline: '$BASELINE'; repository: ' >>>>>> filetree://./PharoLambda/src'; load." >>>>>> >>>>>> As I tried that. The baseline of Lambda is then able to be loaded. >>>>>> >>>>>> -- Pavel >>>>>> >>>>>> >>>>>> >>>>>>> >>>>>>> >>>>>>> 2017-08-02 15:18 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: >>>>>>> >>>>>>>> Ah, I think Iâm starting to get closer to what I needâ¦ >>>>>>>> >>>>>>>> So if I want to load in that last piece to enable more general >>>>>>>> remote loading - how do I figure out how to do that? Iâm trying to work out >>>>>>>> where the build steps for building up the image (can I see them in Jenkins? >>>>>>>> It wasnât clear to me if I can look it up? Or the BaselineOfIDE was >>>>>>>> mentioned - looking there I can see a few metacello and gofer packages - >>>>>>>> but then I guess Iâm looking for an easy Mcz I can use with the example >>>>>>>> below? >>>>>>>> >>>>>>>> Or do I just load Metacello as a git submodule and then it will be >>>>>>>> on my local filesystem to then bootstrap up? >>>>>>>> >>>>>>>> I guess Iâm trying to work out the best sustainable approach to >>>>>>>> getting to a good server based image that has minimal tools and the ability >>>>>>>> to easily load remote code for pre-req projects. >>>>>>>> >>>>>>>> Tim >>>>>>>> >>>>>>>> On 2 Aug 2017, at 07:05, Guillermo Polito < >>>>>>>> guillermopolito(a)gmail.com> wrote: >>>>>>>> >>>>>>>> Yes, you should be able to load an mcz in that image by doing: >>>>>>>> >>>>>>>> (MCDirectoryRepository new directory: 'where-your-mcz-is') >>>>>>>> loadVersionFromFileNamed: 'Metacello-GitBasedRepository-Author.1.mcz') >>>>>>>> load. >>>>>>>> >>>>>>>> Guille >>>>>>>> >>>>>>>> On Wed, Aug 2, 2017 at 7:57 AM, Pavel Krivanek < >>>>>>>> pavel.krivanek(a)gmail.com> wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> 2017-08-01 23:13 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: >>>>>>>>> >>>>>>>>>> Hi Pavel - I tried it again and the problem is do with Metacello >>>>>>>>>> dependencies in your baseline. >>>>>>>>>> >>>>>>>>>> The SUnit baseline doesnât specify any additional dependencies to >>>>>>>>>> load (it just loads local packages), whereas my baseline that fails looks >>>>>>>>>> like this: >>>>>>>>>> >>>>>>>>>> baseline: spec >>>>>>>>>> <baseline> >>>>>>>>>> >>>>>>>>>> spec for: #common do: [ >>>>>>>>>> spec configuration: 'ZTimestamp' with: [ >>>>>>>>>> spec >>>>>>>>>> versionString: #stable; >>>>>>>>>> repository: 'http://mc.stfx.eu/Neo' ]. >>>>>>>>>> spec baseline: 'AWS' with: [ >>>>>>>>>> spec repository: 'github://newapplesho/aws-sdk- >>>>>>>>>> smalltalk:v1.10/pharo-repository' ]. >>>>>>>>>> spec >>>>>>>>>> package: 'Lambda' with: [ spec requires: {'ZTimestamp'. 'AWS'}]. >>>>>>>>>> ]. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> The âspec configuration: â¦.â Specifications cause the error: >>>>>>>>>> >>>>>>>>>> 25 UndefinedObject(Object)>>*doesNotUnderstand: #addTo:* >>>>>>>>>> 26 MCRepositoryGroup>>addRepository: >>>>>>>>>> >>>>>>>>>> If I remove those lines from my baseline above (as well the >>>>>>>>>> requires: reference to them) I can then successfully load my packages. >>>>>>>>>> >>>>>>>>>> So is this something the minimal image should support (otherwise >>>>>>>>>> how do you load external packages into your image without checking them in >>>>>>>>>> locally?) OR is there something simple I can checkin and load locally to >>>>>>>>>> return that behaviour? (Personally I think it would make sense to allow >>>>>>>>>> remote loading - Iâm guessing Pharo itself as a core has everything it >>>>>>>>>> needs - but if you want to do any experimentation on the core and need >>>>>>>>>> remote packages, you would hit this too - so it feels a bit limiting). >>>>>>>>>> >>>>>>>>> >>>>>>>>> The dependencies in th baseline are supported but the support for >>>>>>>>> most of external repositories (like package Metacello-GitBasedRepository) >>>>>>>>> is loaded at the end of bootstrapping process in BaselineOfIDE. We should >>>>>>>>> check/solve dependencies and move it into the minimal Pharo. For now you >>>>>>>>> can try to load it by yourself or work with already prepared local clones >>>>>>>>> of required repositories. >>>>>>>>> >>>>>>>>> -- Pavel >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>> Tim >>>>>>>>>> >>>>>>>>>> On 1 Aug 2017, at 10:06, Pavel Krivanek <pavel.krivanek(a)gmail.com> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> 2017-07-31 22:51 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: >>>>>>>>>> >>>>>>>>>>> I wasnât clear on which image to retry - the >>>>>>>>>>> https://ci.inria.fr/pharo/job/Pharo-6.0-Update-Step-3.2- >>>>>>>>>>> Minimal/lastSuccessfulBuild/artifact/Pharo-minimal-64.zip one >>>>>>>>>>> still shows as being last updated 7 days ago. >>>>>>>>>>> >>>>>>>>>>> The https://ci.inria.fr/pharo/view/6.0-SysConf/job/Pharo-6.0 >>>>>>>>>>> -Step-04-01-ConfigurationOfMinimalPharo/ one gives me a >>>>>>>>>>> mismatch error: This interpreter (vers. 68021) cannot read image file >>>>>>>>>>> (vers. 6521). >>>>>>>>>>> >>>>>>>>>>> The https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bi >>>>>>>>>>> t-Conversion/lastSuccessfulBuild/artifact/latest-minimal-64.zip one >>>>>>>>>>> gives me a walkback when trying to run my install script : >>>>>>>>>>> >>>>>>>>>>> 25 UndefinedObject(Object)>>*doesNotUnderstand: #addTo:* >>>>>>>>>>> 26 MCRepositoryGroup>>addRepository: >>>>>>>>>>> 27 createRepository >>>>>>>>>>> | repo | >>>>>>>>>>> repo := self project createRepository: self. >>>>>>>>>>> ^ MCRepositoryGroup default repositories >>>>>>>>>>> detect: [ :each | each = repo ] >>>>>>>>>>> ifNone: [ >>>>>>>>>>> MCRepositoryGroup default addRepository: repo. >>>>>>>>>>> repo ] in MetacelloRepositorySpec>>createRepository >>>>>>>>>>> >>>>>>>>>>> I think this is because the image doesnât support Metacello? As >>>>>>>>>>> in: >>>>>>>>>>> >>>>>>>>>>> Metacello new >>>>>>>>>>> repository: 'filetree://../src'; >>>>>>>>>>> baseline: 'Lambda'; >>>>>>>>>>> load. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> How do you guys load things into the minimal images (I thought >>>>>>>>>>> you used Metacello - but maybe you do it some other way?) >>>>>>>>>>> >>>>>>>>>>> I can use a big 6.1 image fine (as it has Metacello loaded) but >>>>>>>>>>> Iâd really like a minimal solution - that can load in libraries like AWS >>>>>>>>>>> S3, or XML parsing etc. and it seems like I should be a good customer for >>>>>>>>>>> kicking the tires on all of this. >>>>>>>>>>> >>>>>>>>>>> Tim >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> I checked the 64-bit Pharo 7 minimal image and loading of >>>>>>>>>> baseline (of SUnit from pharo-project/pharo) works: >>>>>>>>>> >>>>>>>>>> ./pharo Pharo7.0-minimal-64bit-b1625bf.image eval --save >>>>>>>>>> "Metacello new baseline: 'SUnit'; repository: ' >>>>>>>>>> filetree://./pharo-core/src'; load." >>>>>>>>>> >>>>>>>>>> ./pharo Pharo7.0-minimal-64bit-b1625bf.image eval "TestCase >>>>>>>>>> suite run" >>>>>>>>>> >>>>>>>>>> Can you test it too? >>>>>>>>>> >>>>>>>>>> -- Pavel >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> 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 <+33%206%2052%2070%2066%2013> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Mariano >>>> http://marianopeck.wordpress.com >>>> >>>> >>>> >>> >>> >>> -- >>> Mariano >>> http://marianopeck.wordpress.com >>> >>> >>> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> >> >> >> >> > >

Aug. 4, 2017

Re: [Pharo-dev] PharoLauncher - uninformative Pharo7 template names

by Ben Coman

On Fri, Aug 4, 2017 at 3:22 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi Ben, > > reason is that for Pharo 7 currently an sha git hash is used in the file > name > instead of a (more clear) build number. > > See http://files.pharo.org/image/70/ > > This problem (which has more side effects on different sides, not only the > Launcher now) was discussed > already yesterday on Discord #iceberg channel with Esteban and Pavel. > > The current sha based image file name scheme is not only confusing but has > some downsides. > One can not easily remember the SHA or see which image is the latest, or > sort from recent > images to older in a folder. > > If I understood correctly the reason to (initially) choose sha's in the > image name has something > to do with Travis and a discussion between Pavel, Esteban and Guille. > > I would vote for using Build numbers again. > > We would have several BENEFITS when keeping/returning to build numbers for > Pharo 7: > - we do not change image file names, about box behavior, ... compared to > previous Pharo version < 7 > (as we used image build number already in the past) > - we tag each release as before and see it in Git (we can easily > reproduce) > - the build number easily tells you which image is more recent (as before) > - we can easily sort when we have several images in a directory > - a build number is more readable and recognizable by a human (compared > to the shas) > - Pharo is not an "aliens" compared to the rest of the software world as > often software > follows a MAJOR.MINOR.PATCH/BUILDNUMBER scheme (see semver.org) > - we do not change the order in Launcher (higher numbers at the top to > download more recent) > > According to the discussion with Esteban and Pavel it is technically > possible to have build numbers again - > it means to tag each commit again with a build number (we already did this > for Pharo 6, > see https://github.com/pharo-project/pharo/releases) > Annotating build-commits with tags "seems" the right way to go, but I haven't played with them much. There does seem to some potential confusion in how tags operate to pay attention to... https://stackoverflow.com/questions/16678072/fetching-all-tags-from-a-remot… The example here by joshtkling that has two fetch lines might be useful (but I'm not sure if thats relevant to libgit or just to command-line git)... https://eddiemoya.com/2013/02/21/better-git-git-fetch-not-getting-tags/ cheers -ben > > The outcome from yesterday was that Pavel will discuss again with Guile on > that topic. It would be good if others > could comment on that topic too. Maybe we can return to the known build > number scheme > or (if there are problems with that) at least know the arguments why we > need to be exotic/different on > this corner in the future. > > Thanks > T. > > *Gesendet:* Donnerstag, 03. August 2017 um 15:41 Uhr > *Von:* "Ben Coman" <btc(a)openinworld.com> > *An:* "Pharo Development List" <pharo-dev(a)lists.pharo.org> > *Betreff:* [Pharo-dev] PharoLauncher - uninformative Pharo7 template names > > Attached is what I see for Pharo 7 images in PharoLauncher. > I presume the top one is the latest, but Its a bit hard to tell :P > Anyone else seeing this? > > Loading ConfigurationOfPharoLauncher-ChristopheDemarey.53 (latest) > and doing "ConfigurationOfPharoLauncher loadDevelopment" > which loads PharoLauncher-Core-ChristopheDemarey.116 (latest) > > This is with Pharo builds 60486 and 60510, and same VM for both... > Win32 built on May 31 2017 03:09:04 GMT Compiler: 5.4.0 VMMaker > versionString VM: 201705310241 > CoInterpreter VMMaker.oscog-eem.2231 uuid: de62947a-7f40-4977-a232-e06a3a80c939 > May 31 2017 > > (but btw, does that look strange? The 60510 image was lauched from the > original 60486-PharoLauncher which said it was downloading the matching VM, > so I kind of expect each image to have a different VM ?? ) > > cheers -ben >

Aug. 4, 2017

Re: [Pharo-dev] About cr and lf

by Stephane Ducasse

Yes :) On Fri, Aug 4, 2017 at 2:25 PM, tesonep(a)gmail.com <tesonep(a)gmail.com> wrote: > To me it is clear that cr and lf should be in streams. But they should put > the 'cr' or 'lf' character only. And of course the platform independent > newline should be also. > > The first (cr, lf) should be used by the code wanting to have absolute > control of what is in the stream. The later (newline) when you just want a > new line. > > The two have completely different behaviour, ones are really low level, the > other is higher level. > > On 4 Aug 2017 14:20, "Esteban Lorenzano" <estebanlm(a)gmail.com> wrote: >> >> >> > On 4 Aug 2017, at 14:06, Stephane Ducasse <stepharo.self(a)gmail.com> >> > wrote: >> > >> > Well. This is not implemented like that in Pharo. >> > >> > cr is bad because it does not mean that it is independent of the >> > platform. >> > So cr can be redefined as newLine and keep but not used inside the >> > system. >> >> sometimes you actually want to write a cr (or a lf). So it needs to remain >> in the system, of course. >> now, including #newLine can be cool (most of the times you want the >> âplatform compatibleâ new line). Also I would consider including #nl, >> abbreviatedâ¦ just for convenience :P >> >> Esteban >> >> > >> > Stef >> > >> > On Fri, Aug 4, 2017 at 12:50 PM, Jan Vrany <jan.vrany(a)fit.cvut.cz> >> > wrote: >> >> On Fri, 2017-08-04 at 12:03 +0200, Stephane Ducasse wrote: >> >>> Hi guys >> >>> >> >>> While writing pillar code, I ended up using "stream cr" and it >> >>> worries >> >>> me to still expand usage >> >>> of a pattern I would like to remove. >> >>> >> >>> Let us imagine that we would like to prepare the migration from cr. >> >>> I was thinking that we could replace cr invocation by newLine so that >> >>> after newLine >> >>> could be redefined as >> >>> >> >>> Stream >> newLine >> >>> self nextPutAll: OSPlatform current lineEnding >> >>> >> >>> >> >>> what do you think about this approach? >> >> >> >> Why not? But please keep #cr. >> >> >> >> Section 5.9.4.1 of ANSI reads: >> >> >> >> Message: cr >> >> >> >> Synopsis >> >> Writes an end-of-line sequence to the receiver. >> >> >> >> Definition: <puttableStream> >> >> A sequence of character objects that constitute the implementation- >> >> defined end-of-line sequence is added to the receiver in the same >> >> manner as if the message #nextPutAll: was sent to the receiver with >> >> an argument string whose elements are the sequence of characters. >> >> >> >> Return Value >> >> UNSPECIFIED >> >> Errors >> >> It is erroneous if any element of the end-of-line sequence is an >> >> object that does not conform to the receiver's sequence value type . >> >> >> >> my 2c, >> >> >> >> Jan >> >> >> >>> >> >>> Stef >> >>> >> >> >> > >> >> >

Aug. 4, 2017

Re: [Pharo-dev] Creating the smallest server runtime footprint

by Tim Mackinnon

Hi Pavel - When you say âpackages from the Pharo repoâ - I think Iâm doing that - yesterday I cloned the Pharo repo and then I copied the Fuel packages you guys suggested over into my branch (not elegant, but simple). So I should have the flattened versions then? (I have now managed to get the P7 image working - so thanks for all your help, but Iâm curious about this part) Tim > On 4 Aug 2017, at 12:49, Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>> wrote: > > Hmm, Pharo 7 has flattened traits in the kernel, but it still supports them. So probably because you are using vanilla Fuel packages, they extend traits that are not used for real. You should use packages from the Pharo repository. > > -- Pavel > > 2017-08-04 13:42 GMT+02:00 Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>>: > Sadly - false call, that was my logging message - so Iâm stumped why these traits arenât being compiled when I load in Fuel? > > However I have figured out why I get the BigEndian error - this is because the platform is now 7 and so the FlPharo06Platform is not being identified and the more generic FlPharoPlatform is then the default and it doesnât implement #isBigEndian. > > Tim > > > >> On 4 Aug 2017, at 12:20, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >> >> Iâve spotted something interesting in my logs - when I added one of the missing methods to ClassDescription - I see in the log the message: >> >> Loaded -> Fuel-cypress.1 --- filetree:///builds/macta/PharoLambda/bootstrap <> --- cache >> ...finished baseline >> Compiling missing traits... >> Evaluating post load initialization... >> Finished Script. >> >> However when I remove all the compiles I donât see this message: >> >> Loaded -> Fuel-cypress.1 --- filetree:///builds/macta/PharoLambda/bootstrap <> --- cache >> ...finished baseline >> Evaluating post load initialization... >> Finished Script. >> >> >> So I wonder if this is similar to the problem I had in the previous 6.0 image - where some things didnât seem to compile properly (in that case, it was loading a missing class that didnât seem to cause recompilation). >> >> Tim >> >>> On 4 Aug 2017, at 11:10, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >>> >>> Actually there is something weird going on - as now Iâm getting a complaint about "FLPharoPlatform had the subclass responsibility to implement #isBigEndianâ, and thatâs in the FuelPlatform-Pharo-06 which you said to include (and it looks like I am). >>> >>> I need to double check this - as I must be making some trivial mistake. >>> >>> Tim >>> >>>> On 4 Aug 2017, at 11:01, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >>>> >>>> Hi Mariano - Iâve looked at this again, and it was my fault - I was compiling in : >>>> >>>> fuelAccept: aGeneralMapper >>>> ^self explicitRequirement. >>>> >>>> Because when I looked at the Traits for fuel - this is what it had for TClass? - as Iâm not so clear on traits, what does this mean - as I had just assumed that I should flatten the Fuel methods for TCLass, TBehaviour and TClassDescription - but I think Iâve misunderstood what I should do (and I guess from Pavelâs comment - I should really look at why that initial method was missing as it sounds like it should have worked - so maybe its an order loading thing?). >>>> >>>> Thanks, for helping by the way - this is proving very instructional. >>>> >>>> Tim >>>> >>>>> On 3 Aug 2017, at 18:26, Mariano Martinez Peck <marianopeck(a)gmail.com <mailto:marianopeck@gmail.com>> wrote: >>>>> >>>>> >>>>> On Thu, Aug 3, 2017 at 2:14 PM, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >>>>> Hi Mariano - I compiled in the trait methods manually and it got further - but now Iâm seeing another error - Error: Explicitly required method", >>>>> "\u001b[0mLambda class(Object)>>error:", >>>>> "explicitRequirementâ, >>>>> >>>>> >>>>> mmmm the stack is weird... it looks like if Class >> fuelAccept: would have the wrong implementation, that is, having the one from TClass: >>>>> >>>>> fuelAccept: aGeneralMapper >>>>> ^self explicitRequirement. >>>>> >>>>> Rather than the correct one: >>>>> >>>>> fuelAccept: aGeneralMapper >>>>> >>>>> ^aGeneralMapper visitClass: self >>>>> >>>>> >>>>> Maybe the solution is to compile all those methods from traits BUT NOT those that are "^self explicitRequirement." because those will override the good methods. >>>>> >>>>> If that doesn't work, then maybe can you print to console the each impl (source) of each implementor of #fuelAccept: ? >>>>> >>>>> Thoughts? >>>>> >>>>> >>>>> >>>>> >>>>> Any ideas? >>>>> >>>>> Tim >>>>> >>>>> "--- RUNNING ERROR HANDLER ---", >>>>> "Error: Explicitly required method", >>>>> "", >>>>> "\u001b[0m\u001b[31mError: Explicitly required method", >>>>> "\u001b[0mLambda class(Object)>>error:", >>>>> "explicitRequirement", >>>>> " self error: 'No decompiler available' in Lambda class(Object)>>explicitRequirement in Block: explicitRequirement...", >>>>> "False>>ifFalse:", >>>>> "Lambda class(Object)>>explicitRequirement", >>>>> "Lambda class(Class)>>fuelAccept:", >>>>> "FLLightGeneralMapper>>mapAndTrace:", >>>>> "FLLightGlobalMapper>>mapAndTrace:", >>>>> "FLPluggableSubstitutionMapper>>mapAndTrace:", >>>>> "FLAnalysis>>mapAndTrace:", >>>>> "FLAnalysis>>run", >>>>> "setDefaultAnalysis", >>>>> " self error: 'No decompiler available' in FLAnalyzer>>setDefaultAnalysis in Block: setDefaultAnalysis...", >>>>> "FLAnalyzer>>analysisFor:", >>>>> "FLSerialization>>analysisStep", >>>>> "FLSerialization>>run", >>>>> "setDefaultSerialization", >>>>> " self error: 'No decompiler available' in FLSerializer>>setDefaultSerialization in Block: setDefaultSerialization...", >>>>> "serialize: t1 on: t2", >>>>> " self error: 'No decompiler available' in FLSerializer>>serialize:on: in Block: serialize: t1 on: t2...", >>>>> "on: t1 globalEnvironment: t2 do: t3", >>>>> " self error: 'No decompiler available' in FLEncoder class>>on:globalEnvironment:do: in Block: on: t1 globalEnvironment: t2 do: t3...", >>>>> "BlockClosure>>ensure:", >>>>> "FLEncoder class>>on:globalEnvironment:do:", >>>>> "FLSerializer>>serialize:on:", >>>>> "NonInteractiveUIManager>>writeFuelContext:", >>>>> "Lambda class>>processDebug:", >>>>> "Lambda class>>processJSON:", >>>>> "Lambda class>>process:", >>>>> "activate", >>>>> >>>>>> On 3 Aug 2017, at 17:26, Mariano Martinez Peck <marianopeck(a)gmail.com <mailto:marianopeck@gmail.com>> wrote: >>>>>> >>>>>> >>>>>> >>>>>> On Thu, Aug 3, 2017 at 1:17 PM, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >>>>>> Hi guys - I think Iâm getting close - Iâm able to load remote packages, and Iâve added fuel to my repo and its loading - however I am getting an error when I run and test writing out a context - MessageNotUnderstood: Context class>>fuelIgnoredInstanceVariableNames >>>>>> >>>>>> I can see that this is a trait - is trait support missing in the minimal image? >>>>>> >>>>>> >>>>>> Uff...that's a good question hahahhah >>>>>> I don't know if the minimal image supports traits, but what I am almost sure, is the Behavior DOES need the methods defined in TBehavior. So maybe the minimal image flattens the traits. In this case you could do the same for Fuel (flattenDownAllTraits) >>>>>> >>>>>> (I also seemed to get this far just loading the Fuel package - but just to be sure I added the other platform ones like you suggested and still get the same error). Given how simple that method is, I could just compile it in - but maybe there are many more? >>>>>> >>>>>> >>>>>> >>>>>> TBehavior, TClass and TClassDescription are the only one that comes to my mind right now... there are only a few methods from Fuel. So could compile those directly at least on a first step...at least you keep you going. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Tim >>>>>> >>>>>> >>>>>> "errorMessage": "Command failed: ./pharo Pharo.image --no-default-preferences process Lambda '{\"debug\":true,\"data\":5}'\n >>>>>> "errorType": "Error", >>>>>> "stackTrace": [ >>>>>> "Writing fuel context to S3...", >>>>>> "Using S3 bucket morethan-technology-projects", >>>>>> "\u001b[31m", >>>>>> "--- RUNNING ERROR HANDLER ---", >>>>>> "MessageNotUnderstood: Context class>>fuelIgnoredInstanceVariableNames", >>>>>> "", >>>>>> "\u001b[0m\u001b[31mMessageNotUnderstood: Context class>>fuelIgnoredInstanceVariableNames", >>>>>> "\u001b[0mContext class(Object)>>doesNotUnderstand: #fuelIgnoredInstanceVariableNames", >>>>>> "FLVariablesMapping>>instanceVariableNamesToSerialize", >>>>>> "FLVariablesMapping>>initializeAnalyzing", >>>>>> "FLVariablesMapping class>>newAnalyzing:references:", >>>>>> "FLContextCluster(FLPointerObjectCluster)>>initializeAnalyzing:", >>>>>> "FLContextCluster class(FLObjectCluster class)>>newAnalyzing:", >>>>>> "clusterKeyedByObjectClass: t1 class: t2", >>>>>> " self error: 'No decompiler available' in FLLightGeneralMapper(FLMapper)>>clusterKeyedByObjectClass:class: in Block: clusterKeyedByObjectClass: t1 class: t2...", >>>>>> "clusterInstanceOf: t1 keyInBucket: t2 factory: t3", >>>>>> " self error: 'No decompiler available' in FLLightGeneralMapper(FLMapper)>>clusterInstanceOf:keyInBucket:factory: in Block: clusterInstanceOf: t1 keyInBucket: t2 factory: t3...", >>>>>> "at: t1 ifAbsentPut: t2", >>>>>> " self error: 'No decompiler available' in IdentityDictionary(Dictionary)>>at:ifAbsentPut: in Block: at: t1 ifAbsentPut: t2...", >>>>>> "IdentityDictionary(Dictionary)>>at:ifAbsent:", >>>>>> "IdentityDictionary(Dictionary)>>at:ifAbsentPut:", >>>>>> "FLLightGeneralMapper(FLMapper)>>clusterInstanceOf:keyInBucket:factory:", >>>>>> "FLLightGeneralMapper(FLMapper)>>clusterKeyedByObjectClass:class:", >>>>>> "FLLightGeneralMapper(FLMapper)>>mapAndTraceByObjectClass:to:", >>>>>> "FLLightGeneralMapper>>visitMethodContext:", >>>>>> "Context>>fuelAccept:", >>>>>> "FLLightGeneralMapper>>mapAndTrace:", >>>>>> "FLLightGlobalMapper>>mapAndTrace:", >>>>>> "FLPluggableSubstitutionMapper>>mapAndTrace:", >>>>>> "FLAnalysis>>mapAndTrace:", >>>>>> "FLAnalysis>>run", >>>>>> "setDefaultAnalysis", >>>>>> " self error: 'No decompiler available' in FLAnalyzer>>setDefaultAnalysis in Block: setDefaultAnalysis...", >>>>>> "FLAnalyzer>>analysisFor:", >>>>>> "FLSerialization>>analysisStep", >>>>>> "FLSerialization>>run", >>>>>> "setDefaultSerialization", >>>>>> " self error: 'No decompiler available' in FLSerializer>>setDefaultSerialization in Block: setDefaultSerialization...", >>>>>> "serialize: t1 on: t2", >>>>>> " self error: 'No decompiler available' in FLSerializer>>serialize:on: in Block: serialize: t1 on: t2...", >>>>>> "on: t1 globalEnvironment: t2 do: t3", >>>>>> " self error: 'No decompiler available' in FLEncoder class>>on:globalEnvironment:do: in Block: on: t1 globalEnvironment: t2 do: t3...", >>>>>> "BlockClosure>>ensure:", >>>>>> "FLEncoder class>>on:globalEnvironment:do:", >>>>>> "\u001b[0m" >>>>>>> On 3 Aug 2017, at 13:16, Mariano Martinez Peck <marianopeck(a)gmail.com <mailto:marianopeck@gmail.com>> wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Thu, Aug 3, 2017 at 8:58 AM, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >>>>>>> Iâm so close now (bit of a diversion with gitlab yml not liking the eval string) - that did load and it got me really close - Iâm just missing FlSerializer now (I have progressed my work to fuel out the context for debugging to S3)â¦ so looking at the repo, there are quite a few fuel packages - but in a big image I can see that FLSerialiser is in Core - so do I just need core? But then there are a few fuel packages with Core? >>>>>>> >>>>>>> >>>>>>> The easiest way to understand that is either checking ConfigurationOfFuel directly or some of the related Metacello tool. >>>>>>> Anyway, for this case, I think you need the packages (in this order): FuelPlatform and Fuel. Bug again, Metacello allows some postLoad actions (which we use in Fuel)... so...it's not always easy to load a project without Metacello. >>>>>>> >>>>>>> Sometimes you can print the result of #record: >>>>>>> >>>>>>> Metacello new >>>>>>> configuration: 'Fuel'; >>>>>>> smalltalkhubUser: 'Pharo' project: 'Fuel'; >>>>>>> version: #stable; >>>>>>> record: #('Core'). >>>>>>> >>>>>>> -> >>>>>>> >>>>>>> "linear load : >>>>>>> linear load : 2.1.10 [ConfigurationOfFuel] >>>>>>> linear load : baseline [ConfigurationOfFuelPlatform] >>>>>>> load : FuelPlatform-Core >>>>>>> load : FuelPlatform-Pharo-Core >>>>>>> load : FuelPlatform-Pharo-06" >>>>>>> >>>>>>> >>>>>>> ------ >>>>>>> >>>>>>> Anyway.... I guess I would try to load these packages (in this order): >>>>>>> >>>>>>> FuelPlatform-Core >>>>>>> FuelPlatform-Pharo-Core >>>>>>> FuelPlatform-Pharo-06 >>>>>>> Fuel >>>>>>> >>>>>>> And when you are down loading, then execute: >>>>>>> >>>>>>> (Smalltalk at: #FLPlatform) current addHacks >>>>>>> >>>>>>> >>>>>>> Iâm also not quite clear on how I would load packages without a Baseline (would I create my own baseline for the fuel packages I need?) >>>>>>> >>>>>>> Tim >>>>>>> >>>>>>>> On 3 Aug 2017, at 12:07, Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>> wrote: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> 2017-08-03 13:02 GMT+02:00 Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>>: >>>>>>>> I really appreciate your patience and help on this - it looks very promising and I am giving it a spin nowâ¦ >>>>>>>> >>>>>>>> When you say the pharo repository - are you referring to this: https://github.com/pharo-project/pharo/tree/master/src <https://github.com/pharo-project/pharo/tree/master/src>. ? Just so I know for the future. >>>>>>>> >>>>>>>> yes >>>>>>>> >>>>>>>> -- Pavel >>>>>>>> >>>>>>>> >>>>>>>> Tim >>>>>>>> >>>>>>>>> On 3 Aug 2017, at 09:16, Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>> wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> 2017-08-03 10:14 GMT+02:00 Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>>: >>>>>>>>> The easiest think you can do is to copy to your repository (or some other) related packages from the Pharo repository (to do not have to clone it all): >>>>>>>>> >>>>>>>>> Metacello-GitBasedRepository.package >>>>>>>>> Metacello-GitHub.package >>>>>>>>> SUnit-Core.package >>>>>>>>> >>>>>>>>> and create baseline to load them. I already tried it so you can test it: >>>>>>>>> https://drive.google.com/open?id=0BzSsmZhqtUTeMVJacTZtdW5UQW8 <https://drive.google.com/open?id=0BzSsmZhqtUTeMVJacTZtdW5UQW8> >>>>>>>>> >>>>>>>>> Then you will do something like: >>>>>>>>> >>>>>>>>> (accidental message send ;-) ) >>>>>>>>> >>>>>>>>> BASELINE=MetacelloGitBasedRepository >>>>>>>>> pharo "$IMAGE_NAME.image" --no-default-preferences eval --save \ >>>>>>>>> "Metacello new baseline: '$BASELINE'; repository: 'filetree://./PharoLambda/src <>'; load." >>>>>>>>> >>>>>>>>> BASELINE=Lambda >>>>>>>>> pharo "$IMAGE_NAME.image" --no-default-preferences eval --save \ >>>>>>>>> "Metacello new baseline: '$BASELINE'; repository: 'filetree://./PharoLambda/src <>'; load." >>>>>>>>> >>>>>>>>> As I tried that. The baseline of Lambda is then able to be loaded. >>>>>>>>> >>>>>>>>> -- Pavel >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> 2017-08-02 15:18 GMT+02:00 Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>>: >>>>>>>>> Ah, I think Iâm starting to get closer to what I needâ¦ >>>>>>>>> >>>>>>>>> So if I want to load in that last piece to enable more general remote loading - how do I figure out how to do that? Iâm trying to work out where the build steps for building up the image (can I see them in Jenkins? It wasnât clear to me if I can look it up? Or the BaselineOfIDE was mentioned - looking there I can see a few metacello and gofer packages - but then I guess Iâm looking for an easy Mcz I can use with the example below? >>>>>>>>> >>>>>>>>> Or do I just load Metacello as a git submodule and then it will be on my local filesystem to then bootstrap up? >>>>>>>>> >>>>>>>>> I guess Iâm trying to work out the best sustainable approach to getting to a good server based image that has minimal tools and the ability to easily load remote code for pre-req projects. >>>>>>>>> >>>>>>>>> Tim >>>>>>>>> >>>>>>>>>> On 2 Aug 2017, at 07:05, Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> wrote: >>>>>>>>>> >>>>>>>>>> Yes, you should be able to load an mcz in that image by doing: >>>>>>>>>> >>>>>>>>>> (MCDirectoryRepository new directory: 'where-your-mcz-is') >>>>>>>>>> loadVersionFromFileNamed: 'Metacello-GitBasedRepository-Author.1.mcz') load. >>>>>>>>>> >>>>>>>>>> Guille >>>>>>>>>> >>>>>>>>>> On Wed, Aug 2, 2017 at 7:57 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>> wrote: >>>>>>>>>> >>>>>>>>>> 2017-08-01 23:13 GMT+02:00 Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>>: >>>>>>>>>> Hi Pavel - I tried it again and the problem is do with Metacello dependencies in your baseline. >>>>>>>>>> >>>>>>>>>> The SUnit baseline doesnât specify any additional dependencies to load (it just loads local packages), whereas my baseline that fails looks like this: >>>>>>>>>> >>>>>>>>>> baseline: spec >>>>>>>>>> <baseline> >>>>>>>>>> >>>>>>>>>> spec for: #common do: [ >>>>>>>>>> spec configuration: 'ZTimestamp' with: [ >>>>>>>>>> spec >>>>>>>>>> versionString: #stable; >>>>>>>>>> repository: 'http://mc.stfx.eu/Neo <http://mc.stfx.eu/Neo>' ]. >>>>>>>>>> >>>>>>>>>> spec baseline: 'AWS' with: [ >>>>>>>>>> spec repository: 'github://newapplesho/aws-sdk-smalltalk:v1.10/pharo-repository <>' ]. >>>>>>>>>> >>>>>>>>>> spec >>>>>>>>>> package: 'Lambda' with: [ spec requires: {'ZTimestamp'. 'AWS'}]. >>>>>>>>>> >>>>>>>>>> ]. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> The âspec configuration: â¦.â Specifications cause the error: >>>>>>>>>> >>>>>>>>>> 25 UndefinedObject(Object)>>doesNotUnderstand: #addTo: >>>>>>>>>> 26 MCRepositoryGroup>>addRepository: >>>>>>>>>> >>>>>>>>>> If I remove those lines from my baseline above (as well the requires: reference to them) I can then successfully load my packages. >>>>>>>>>> >>>>>>>>>> So is this something the minimal image should support (otherwise how do you load external packages into your image without checking them in locally?) OR is there something simple I can checkin and load locally to return that behaviour? (Personally I think it would make sense to allow remote loading - Iâm guessing Pharo itself as a core has everything it needs - but if you want to do any experimentation on the core and need remote packages, you would hit this too - so it feels a bit limiting). >>>>>>>>>> >>>>>>>>>> The dependencies in th baseline are supported but the support for most of external repositories (like package Metacello-GitBasedRepository) is loaded at the end of bootstrapping process in BaselineOfIDE. We should check/solve dependencies and move it into the minimal Pharo. For now you can try to load it by yourself or work with already prepared local clones of required repositories. >>>>>>>>>> >>>>>>>>>> -- Pavel >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Tim >>>>>>>>>> >>>>>>>>>>> On 1 Aug 2017, at 10:06, Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>> wrote: >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> 2017-07-31 22:51 GMT+02:00 Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>>: >>>>>>>>>>> I wasnât clear on which image to retry - the https://ci.inria.fr/pharo/job/Pharo-6.0-Update-Step-3.2-Minimal/lastSuccess… <https://ci.inria.fr/pharo/job/Pharo-6.0-Update-Step-3.2-Minimal/lastSuccess…> one still shows as being last updated 7 days ago. >>>>>>>>>>> >>>>>>>>>>> The https://ci.inria.fr/pharo/view/6.0-SysConf/job/Pharo-6.0-Step-04-01-Configu… <https://ci.inria.fr/pharo/view/6.0-SysConf/job/Pharo-6.0-Step-04-01-Configu…> one gives me a mismatch error: This interpreter (vers. 68021) cannot read image file (vers. 6521). >>>>>>>>>>> >>>>>>>>>>> The https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit-Conversion/lastSu… <https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit-Conversion/lastSu…> one gives me a walkback when trying to run my install script : >>>>>>>>>>> >>>>>>>>>>> 25 UndefinedObject(Object)>>doesNotUnderstand: #addTo: >>>>>>>>>>> 26 MCRepositoryGroup>>addRepository: >>>>>>>>>>> 27 createRepository >>>>>>>>>>> | repo | >>>>>>>>>>> repo := self project createRepository: self. >>>>>>>>>>> ^ MCRepositoryGroup default repositories >>>>>>>>>>> detect: [ :each | each = repo ] >>>>>>>>>>> ifNone: [ >>>>>>>>>>> MCRepositoryGroup default addRepository: repo. >>>>>>>>>>> repo ] in MetacelloRepositorySpec>>createRepository >>>>>>>>>>> >>>>>>>>>>> I think this is because the image doesnât support Metacello? As in: >>>>>>>>>>> Metacello new >>>>>>>>>>> repository: 'filetree://../src <>'; >>>>>>>>>>> baseline: 'Lambda'; >>>>>>>>>>> load. >>>>>>>>>>> >>>>>>>>>>> How do you guys load things into the minimal images (I thought you used Metacello - but maybe you do it some other way?) >>>>>>>>>>> >>>>>>>>>>> I can use a big 6.1 image fine (as it has Metacello loaded) but Iâd really like a minimal solution - that can load in libraries like AWS S3, or XML parsing etc. and it seems like I should be a good customer for kicking the tires on all of this. >>>>>>>>>>> >>>>>>>>>>> Tim >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> I checked the 64-bit Pharo 7 minimal image and loading of baseline (of SUnit from pharo-project/pharo) works: >>>>>>>>>>> >>>>>>>>>>> ./pharo Pharo7.0-minimal-64bit-b1625bf.image eval --save "Metacello new baseline: 'SUnit'; repository: 'filetree://./pharo-core/src <>'; load." >>>>>>>>>>> >>>>>>>>>>> ./pharo Pharo7.0-minimal-64bit-b1625bf.image eval "TestCase suite run" >>>>>>>>>>> >>>>>>>>>>> Can you test it too? >>>>>>>>>>> >>>>>>>>>>> -- Pavel >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> >>>>>>>>>> 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 <tel:+33%206%2052%2070%2066%2013> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Mariano >>>>>>> http://marianopeck.wordpress.com <http://marianopeck.wordpress.com/> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Mariano >>>>>> http://marianopeck.wordpress.com <http://marianopeck.wordpress.com/> >>>>> >>>>> >>>>> >>>>> -- >>>>> Mariano >>>>> http://marianopeck.wordpress.com <http://marianopeck.wordpress.com/> >>>> >>> >> > >

Aug. 4, 2017

Re: [Pharo-dev] Creating the smallest server runtime footprint

by Tim Mackinnon

Hi - I was actually reading those slides the other day, but hadnât fully appreciated the consequencesâ¦ that is very cool - and definitely something for me to put on the stack of things to try out I was going to say I could put the Fuel and S3 access into such a library - but then I would need them to load it from S3 - so catch 22 for that, but Iâll bet I come up with another usage. Thanks to everyone for their help with this. Is there anything I need follow up on from this? I saw you asked Max about the Platform7 piece. I also donât understand why I have problems with those missing fuel trait methods (so Iâll see what Pavel says about that). Tim > On 4 Aug 2017, at 14:24, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > > On Fri, Aug 4, 2017 at 9:51 AM, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: > HURRAH - I got it to work, and Fuel out an error to S3 and read it back into a fat 6.1 image with a debug stack (which is so cool!). > > > > COOOL!!! I want to see your blogpost once you make it!!! > Congratulations, this was a very cool thread to follow :) > > My footprint size is still a bit larger than I would like (31mb - image of 22.7mb - of which 1mb if fuel and 7mb is S3 and XMLParser support) - so I guess I need to find ways to trim down some of the addons (and any additional image size reductions would be helpful - if there are any to be had). > > Is there any easy tools/scripts to explore a headless image and figure out what takes the most size (maybe at a package level?). But definitely this has got me into a good place for experimentation. > > > > I know this is a bit offtopic... but maybe to give you some perspective... For my PhD, one of the things I did (lets say the closest to the PhD topic) was called Marea [1] (I can also send you the slides and the PhD defense video on youtube if you want). In Marea what I did was to modify the VM to implement a very basic (with lots of limitations) object usage tracking...I simply flagged when an object was used and cleared the flag every in a while. Then, at image side, I would find graphs of unused objects, and replaced the boundary objects with proxies using Ghost proxies (note that an anused object is not the same as unreferenced object,...GC does nothing here). The graphs where then serialized with Fuel. Finally, if those graphs happened to be needed, then the proxy would intercept the message, materialize from Fuel, and plug back the original graph. > > Anyway... all of what was to said that I some point I did an experiment. I was able to already proxify and serialize classes, methods, etc. So I took the whole image and I swapped out all classes and their instances (each class with its instances in a different graph) but only a really small core. This image was a Seaside image running DBX Pier website. So I swapped out everything, and then I lazily started to navigate DBX website, causing the needed graphs to be swapped in. I was able to naviagat all webapp and use it perfectly. I even saved the image. And all this email is to say that such an image was 3MB. > > > Cheers, > > > > [1] https://www.slideshare.net/MarianoMartinezPeck/thesis-presentation-14987645 <https://www.slideshare.net/MarianoMartinezPeck/thesis-presentation-14987645> > > > > > > For the record I had to do the following to get things working: > > Define a new baseline: > baseline: spec > <baseline> > > spec for: #common do: [ > spec > package: 'Metacello-GitBasedRepository'; > package: 'Metacello-GitHub'; > package: 'FuelPlatform-Core'; > package: 'FuelPlatform-Pharo-Core'; > package: 'FuelPlatform-Pharo-06'; > package: 'Fuel'. > ]. > > Run the following script: > Metacello new > baseline: 'MetacelloGitBasedRepository'; > repository: 'filetree://../bootstrap <>'; > load. > > âReplace missing traits" > Behavior compiledMethodAt: #fuelIgnoredInstanceVariableNames > ifPresent: [ :m | logger cr; nextPutAll: 'Trait method is present' ] > ifAbsent: [ > logger cr; nextPutAll: 'Recompile missing traits ...'. > > Behavior > compile: 'fuelIgnoredInstanceVariableNames > "Indicates which variables have to be ignored during serialization." > > ^#()'; > compile: 'fuelNew > "Answer an instance of mine in which serialized references will be injected." > > ^ self basicNew'; > compile: 'fuelNew: sizeRequested > "Answer an instance of mine in which serialized references will be injected." > > ^ self basicNew: sizeRequested'. > > "Ignore this one" > "Class > compile: 'fuelAccept: aGeneralMapper > ^self explicitRequirement.'." > > ClassDescription > compile: 'instanceVariableNamesDo: anUnaryBlock > "This is part of the interface between the compiler and a class''s instance or field names. > The class should enumerate anUnaryBlock with the instance variable name strings. The order is important. Names evaluated later will override the > same names occurring earlier." > > | superInstSize | > (superInstSize := self superclass notNil ifTrue: [self superclass instSize] ifFalse: [0]) > 0 ifTrue: > [self superclass instanceVariableNamesDo: anUnaryBlock]. > 1 to: self instSize - superInstSize do: > [:i| anUnaryBlock value: (self instVarNames at: i)]'. > ]. > > âAdd a tacky Pharo7Platform" > Smalltalk at: #FLPharo7Platform ifAbsent: [ > logger cr; nextPutAll: '>Creating FLPharo7Platform'. > (Smalltalk at: #FLPharo6Platform) subclass: #FLPharo7Platform. > (Smalltalk at: #FLPharo6Platform) class compile: 'isResponsibleForCurrentPlatform > ^true'. > ]. > > > logger cr; nextPutAll: 'Evaluating post load initialization...'. > (Smalltalk at: #FLPlatform) current addHacks. > > >> On 4 Aug 2017, at 12:48, Mariano Martinez Peck <marianopeck(a)gmail.com <mailto:marianopeck@gmail.com>> wrote: >> >> >> >> On Fri, Aug 4, 2017 at 8:42 AM, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >> Sadly - false call, that was my logging message - so Iâm stumped why these traits arenât being compiled when I load in Fuel? >> >> However I have figured out why I get the BigEndian error - this is because the platform is now 7 and so the FlPharo06Platform is not being identified and the more generic FlPharoPlatform is then the default and it doesnât implement #isBigEndian. >> >> >> >> Max, should we do something to the Fuel Platform for Pharo 7? >> >> >> >> Tim >> >> >> >>> On 4 Aug 2017, at 12:20, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >>> >>> Iâve spotted something interesting in my logs - when I added one of the missing methods to ClassDescription - I see in the log the message: >>> >>> Loaded -> Fuel-cypress.1 --- filetree:///builds/macta/PharoLambda/bootstrap <> --- cache >>> ...finished baseline >>> Compiling missing traits... >>> Evaluating post load initialization... >>> Finished Script. >>> >>> However when I remove all the compiles I donât see this message: >>> >>> Loaded -> Fuel-cypress.1 --- filetree:///builds/macta/PharoLambda/bootstrap <> --- cache >>> ...finished baseline >>> Evaluating post load initialization... >>> Finished Script. >>> >>> >>> So I wonder if this is similar to the problem I had in the previous 6.0 image - where some things didnât seem to compile properly (in that case, it was loading a missing class that didnât seem to cause recompilation). >>> >>> Tim >>> >>>> On 4 Aug 2017, at 11:10, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >>>> >>>> Actually there is something weird going on - as now Iâm getting a complaint about "FLPharoPlatform had the subclass responsibility to implement #isBigEndianâ, and thatâs in the FuelPlatform-Pharo-06 which you said to include (and it looks like I am). >>>> >>>> I need to double check this - as I must be making some trivial mistake. >>>> >>>> Tim >>>> >>>>> On 4 Aug 2017, at 11:01, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >>>>> >>>>> Hi Mariano - Iâve looked at this again, and it was my fault - I was compiling in : >>>>> >>>>> fuelAccept: aGeneralMapper >>>>> ^self explicitRequirement. >>>>> >>>>> Because when I looked at the Traits for fuel - this is what it had for TClass? - as Iâm not so clear on traits, what does this mean - as I had just assumed that I should flatten the Fuel methods for TCLass, TBehaviour and TClassDescription - but I think Iâve misunderstood what I should do (and I guess from Pavelâs comment - I should really look at why that initial method was missing as it sounds like it should have worked - so maybe its an order loading thing?). >>>>> >>>>> Thanks, for helping by the way - this is proving very instructional. >>>>> >>>>> Tim >>>>> >>>>>> On 3 Aug 2017, at 18:26, Mariano Martinez Peck <marianopeck(a)gmail.com <mailto:marianopeck@gmail.com>> wrote: >>>>>> >>>>>> >>>>>> On Thu, Aug 3, 2017 at 2:14 PM, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >>>>>> Hi Mariano - I compiled in the trait methods manually and it got further - but now Iâm seeing another error - Error: Explicitly required method", >>>>>> "\u001b[0mLambda class(Object)>>error:", >>>>>> "explicitRequirementâ, >>>>>> >>>>>> >>>>>> mmmm the stack is weird... it looks like if Class >> fuelAccept: would have the wrong implementation, that is, having the one from TClass: >>>>>> >>>>>> fuelAccept: aGeneralMapper >>>>>> ^self explicitRequirement. >>>>>> >>>>>> Rather than the correct one: >>>>>> >>>>>> fuelAccept: aGeneralMapper >>>>>> >>>>>> ^aGeneralMapper visitClass: self >>>>>> >>>>>> >>>>>> Maybe the solution is to compile all those methods from traits BUT NOT those that are "^self explicitRequirement." because those will override the good methods. >>>>>> >>>>>> If that doesn't work, then maybe can you print to console the each impl (source) of each implementor of #fuelAccept: ? >>>>>> >>>>>> Thoughts? >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Any ideas? >>>>>> >>>>>> Tim >>>>>> >>>>>> "--- RUNNING ERROR HANDLER ---", >>>>>> "Error: Explicitly required method", >>>>>> "", >>>>>> "\u001b[0m\u001b[31mError: Explicitly required method", >>>>>> "\u001b[0mLambda class(Object)>>error:", >>>>>> "explicitRequirement", >>>>>> " self error: 'No decompiler available' in Lambda class(Object)>>explicitRequirement in Block: explicitRequirement...", >>>>>> "False>>ifFalse:", >>>>>> "Lambda class(Object)>>explicitRequirement", >>>>>> "Lambda class(Class)>>fuelAccept:", >>>>>> "FLLightGeneralMapper>>mapAndTrace:", >>>>>> "FLLightGlobalMapper>>mapAndTrace:", >>>>>> "FLPluggableSubstitutionMapper>>mapAndTrace:", >>>>>> "FLAnalysis>>mapAndTrace:", >>>>>> "FLAnalysis>>run", >>>>>> "setDefaultAnalysis", >>>>>> " self error: 'No decompiler available' in FLAnalyzer>>setDefaultAnalysis in Block: setDefaultAnalysis...", >>>>>> "FLAnalyzer>>analysisFor:", >>>>>> "FLSerialization>>analysisStep", >>>>>> "FLSerialization>>run", >>>>>> "setDefaultSerialization", >>>>>> " self error: 'No decompiler available' in FLSerializer>>setDefaultSerialization in Block: setDefaultSerialization...", >>>>>> "serialize: t1 on: t2", >>>>>> " self error: 'No decompiler available' in FLSerializer>>serialize:on: in Block: serialize: t1 on: t2...", >>>>>> "on: t1 globalEnvironment: t2 do: t3", >>>>>> " self error: 'No decompiler available' in FLEncoder class>>on:globalEnvironment:do: in Block: on: t1 globalEnvironment: t2 do: t3...", >>>>>> "BlockClosure>>ensure:", >>>>>> "FLEncoder class>>on:globalEnvironment:do:", >>>>>> "FLSerializer>>serialize:on:", >>>>>> "NonInteractiveUIManager>>writeFuelContext:", >>>>>> "Lambda class>>processDebug:", >>>>>> "Lambda class>>processJSON:", >>>>>> "Lambda class>>process:", >>>>>> "activate", >>>>>> > > > > > -- > Mariano > http://marianopeck.wordpress.com <http://marianopeck.wordpress.com/>

Aug. 4, 2017

Re: [Pharo-dev] About cr and lf

by Esteban Lorenzano

> On 4 Aug 2017, at 15:41, Damien Pollet <damien.pollet(a)gmail.com> wrote: > > I agree with Pablo, #cr and #lf should not be clever and just be names for the carriage return and linefeed characters/codepoints. +1 > > Making #newLine's behavior dependent on the current platform disturbs me, though. I'd rather have: > > Stream >> newLineFor: platform > self nextPutAll: platform lineEnding > > Stream >> newLineForCurrentPlatform > self newLineFor: OSPlatform current > > Stream >> newLineForWindows "convenience for the most common platforms > Stream >> newLineForUnix > Stream >> newLineForHistoricReasons > > Stream >> newLine > "delegates to one of the above, I'd argue for unix for convenience, but windows is the technically correct combination of cr + lf, and cr only is the historic one" > > > On 4 August 2017 at 14:25, tesonep(a)gmail.com <mailto:tesonep@gmail.com> <tesonep(a)gmail.com <mailto:tesonep@gmail.com>> wrote: > To me it is clear that cr and lf should be in streams. But they should put the 'cr' or 'lf' character only. And of course the platform independent newline should be also. > > The first (cr, lf) should be used by the code wanting to have absolute control of what is in the stream. The later (newline) when you just want a new line. > > The two have completely different behaviour, ones are really low level, the other is higher level. > > On 4 Aug 2017 14:20, "Esteban Lorenzano" <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > > > On 4 Aug 2017, at 14:06, Stephane Ducasse <stepharo.self(a)gmail.com <mailto:stepharo.self@gmail.com>> wrote: > > > > Well. This is not implemented like that in Pharo. > > > > cr is bad because it does not mean that it is independent of the platform. > > So cr can be redefined as newLine and keep but not used inside the system. > > sometimes you actually want to write a cr (or a lf). So it needs to remain in the system, of course. > now, including #newLine can be cool (most of the times you want the âplatform compatibleâ new line). Also I would consider including #nl, abbreviatedâ¦ just for convenience :P > > Esteban > > > > > Stef > > > > On Fri, Aug 4, 2017 at 12:50 PM, Jan Vrany <jan.vrany(a)fit.cvut.cz <mailto:jan.vrany@fit.cvut.cz>> wrote: > >> On Fri, 2017-08-04 at 12:03 +0200, Stephane Ducasse wrote: > >>> Hi guys > >>> > >>> While writing pillar code, I ended up using "stream cr" and it > >>> worries > >>> me to still expand usage > >>> of a pattern I would like to remove. > >>> > >>> Let us imagine that we would like to prepare the migration from cr. > >>> I was thinking that we could replace cr invocation by newLine so that > >>> after newLine > >>> could be redefined as > >>> > >>> Stream >> newLine > >>> self nextPutAll: OSPlatform current lineEnding > >>> > >>> > >>> what do you think about this approach? > >> > >> Why not? But please keep #cr. > >> > >> Section 5.9.4.1 of ANSI reads: > >> > >> Message: cr > >> > >> Synopsis > >> Writes an end-of-line sequence to the receiver. > >> > >> Definition: <puttableStream> > >> A sequence of character objects that constitute the implementation- > >> defined end-of-line sequence is added to the receiver in the same > >> manner as if the message #nextPutAll: was sent to the receiver with > >> an argument string whose elements are the sequence of characters. > >> > >> Return Value > >> UNSPECIFIED > >> Errors > >> It is erroneous if any element of the end-of-line sequence is an > >> object that does not conform to the receiver's sequence value type . > >> > >> my 2c, > >> > >> Jan > >> > >>> > >>> Stef > >>> > >> > > > > > > > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet <http://people.untyped.org/damien.pollet>

Aug. 4, 2017

Re: [Pharo-dev] About cr and lf

by Damien Pollet

I agree with Pablo, #cr and #lf should not be clever and just be names for the carriage return and linefeed characters/codepoints. Making #newLine's behavior dependent on the current platform disturbs me, though. I'd rather have: Stream >> newLineFor: platform self nextPutAll: platform lineEnding Stream >> newLineForCurrentPlatform self newLineFor: OSPlatform current Stream >> newLineForWindows "convenience for the most common platforms Stream >> newLineForUnix Stream >> newLineForHistoricReasons Stream >> newLine "delegates to one of the above, I'd argue for unix for convenience, but windows is the technically correct combination of cr + lf, and cr only is the historic one" On 4 August 2017 at 14:25, tesonep(a)gmail.com <tesonep(a)gmail.com> wrote: > To me it is clear that cr and lf should be in streams. But they should put > the 'cr' or 'lf' character only. And of course the platform independent > newline should be also. > > The first (cr, lf) should be used by the code wanting to have absolute > control of what is in the stream. The later (newline) when you just want a > new line. > > The two have completely different behaviour, ones are really low level, > the other is higher level. > > On 4 Aug 2017 14:20, "Esteban Lorenzano" <estebanlm(a)gmail.com> wrote: > >> >> > On 4 Aug 2017, at 14:06, Stephane Ducasse <stepharo.self(a)gmail.com> >> wrote: >> > >> > Well. This is not implemented like that in Pharo. >> > >> > cr is bad because it does not mean that it is independent of the >> platform. >> > So cr can be redefined as newLine and keep but not used inside the >> system. >> >> sometimes you actually want to write a cr (or a lf). So it needs to >> remain in the system, of course. >> now, including #newLine can be cool (most of the times you want the >> âplatform compatibleâ new line). Also I would consider including #nl, >> abbreviatedâ¦ just for convenience :P >> >> Esteban >> >> > >> > Stef >> > >> > On Fri, Aug 4, 2017 at 12:50 PM, Jan Vrany <jan.vrany(a)fit.cvut.cz> >> wrote: >> >> On Fri, 2017-08-04 at 12:03 +0200, Stephane Ducasse wrote: >> >>> Hi guys >> >>> >> >>> While writing pillar code, I ended up using "stream cr" and it >> >>> worries >> >>> me to still expand usage >> >>> of a pattern I would like to remove. >> >>> >> >>> Let us imagine that we would like to prepare the migration from cr. >> >>> I was thinking that we could replace cr invocation by newLine so that >> >>> after newLine >> >>> could be redefined as >> >>> >> >>> Stream >> newLine >> >>> self nextPutAll: OSPlatform current lineEnding >> >>> >> >>> >> >>> what do you think about this approach? >> >> >> >> Why not? But please keep #cr. >> >> >> >> Section 5.9.4.1 of ANSI reads: >> >> >> >> Message: cr >> >> >> >> Synopsis >> >> Writes an end-of-line sequence to the receiver. >> >> >> >> Definition: <puttableStream> >> >> A sequence of character objects that constitute the implementation- >> >> defined end-of-line sequence is added to the receiver in the same >> >> manner as if the message #nextPutAll: was sent to the receiver with >> >> an argument string whose elements are the sequence of characters. >> >> >> >> Return Value >> >> UNSPECIFIED >> >> Errors >> >> It is erroneous if any element of the end-of-line sequence is an >> >> object that does not conform to the receiver's sequence value type . >> >> >> >> my 2c, >> >> >> >> Jan >> >> >> >>> >> >>> Stef >> >>> >> >> >> > >> >> >> -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Aug. 4, 2017

Re: [Pharo-dev] About cr and lf

by Javier PimÃ¡s

or eol On Fri, Aug 4, 2017 at 9:19 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > On 4 Aug 2017, at 14:06, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > > > > Well. This is not implemented like that in Pharo. > > > > cr is bad because it does not mean that it is independent of the > platform. > > So cr can be redefined as newLine and keep but not used inside the > system. > > sometimes you actually want to write a cr (or a lf). So it needs to remain > in the system, of course. > now, including #newLine can be cool (most of the times you want the > âplatform compatibleâ new line). Also I would consider including #nl, > abbreviatedâ¦ just for convenience :P > > Esteban > > > > > Stef > > > > On Fri, Aug 4, 2017 at 12:50 PM, Jan Vrany <jan.vrany(a)fit.cvut.cz> > wrote: > >> On Fri, 2017-08-04 at 12:03 +0200, Stephane Ducasse wrote: > >>> Hi guys > >>> > >>> While writing pillar code, I ended up using "stream cr" and it > >>> worries > >>> me to still expand usage > >>> of a pattern I would like to remove. > >>> > >>> Let us imagine that we would like to prepare the migration from cr. > >>> I was thinking that we could replace cr invocation by newLine so that > >>> after newLine > >>> could be redefined as > >>> > >>> Stream >> newLine > >>> self nextPutAll: OSPlatform current lineEnding > >>> > >>> > >>> what do you think about this approach? > >> > >> Why not? But please keep #cr. > >> > >> Section 5.9.4.1 of ANSI reads: > >> > >> Message: cr > >> > >> Synopsis > >> Writes an end-of-line sequence to the receiver. > >> > >> Definition: <puttableStream> > >> A sequence of character objects that constitute the implementation- > >> defined end-of-line sequence is added to the receiver in the same > >> manner as if the message #nextPutAll: was sent to the receiver with > >> an argument string whose elements are the sequence of characters. > >> > >> Return Value > >> UNSPECIFIED > >> Errors > >> It is erroneous if any element of the end-of-line sequence is an > >> object that does not conform to the receiver's sequence value type . > >> > >> my 2c, > >> > >> Jan > >> > >>> > >>> Stef > >>> > >> > > > > > -- Javier PimÃ¡s Ciudad de Buenos Aires

Aug. 4, 2017

Re: [Pharo-dev] Creating the smallest server runtime footprint

by Mariano Martinez Peck

On Fri, Aug 4, 2017 at 9:51 AM, Tim Mackinnon <tim(a)testit.works> wrote: > HURRAH - I got it to work, and Fuel out an error to S3 and read it back > into a fat 6.1 image with a debug stack (which is so cool!). > > COOOL!!! I want to see your blogpost once you make it!!! Congratulations, this was a very cool thread to follow :) > My footprint size is still a bit larger than I would like (31mb - image of > 22.7mb - of which 1mb if fuel and 7mb is S3 and XMLParser support) - so I > guess I need to find ways to trim down some of the addons (and any > additional image size reductions would be helpful - if there are any to be > had). > > Is there any easy tools/scripts to explore a headless image and figure out > what takes the most size (maybe at a package level?). But definitely this > has got me into a good place for experimentation. > > I know this is a bit offtopic... but maybe to give you some perspective... For my PhD, one of the things I did (lets say the closest to the PhD topic) was called Marea [1] (I can also send you the slides and the PhD defense video on youtube if you want). In Marea what I did was to modify the VM to implement a very basic (with lots of limitations) object usage tracking...I simply flagged when an object was used and cleared the flag every in a while. Then, at image side, I would find graphs of unused objects, and replaced the boundary objects with proxies using Ghost proxies (note that an anused object is not the same as unreferenced object,...GC does nothing here). The graphs where then serialized with Fuel. Finally, if those graphs happened to be needed, then the proxy would intercept the message, materialize from Fuel, and plug back the original graph. Anyway... all of what was to said that I some point I did an experiment. I was able to already proxify and serialize classes, methods, etc. So I took the whole image and I swapped out all classes and their instances (each class with its instances in a different graph) but only a really small core. This image was a Seaside image running DBX Pier website. So I swapped out everything, and then I lazily started to navigate DBX website, causing the needed graphs to be swapped in. I was able to naviagat all webapp and use it perfectly. I even saved the image. *And all this email is to say that such an image was 3MB. * Cheers, [1] https://www.slideshare.net/MarianoMartinezPeck/thesis-presentation-14987645 > For the record I had to do the following to get things working: > > Define a new baseline: > > baseline: spec > <baseline> > > spec for: #common do: [ > spec > package: 'Metacello-GitBasedRepository'; > package: 'Metacello-GitHub'; > package: 'FuelPlatform-Core'; > package: 'FuelPlatform-Pharo-Core'; > package: 'FuelPlatform-Pharo-06'; > package: 'Fuel'. > ]. > > > Run the following script: > > Metacello new > baseline: 'MetacelloGitBasedRepository'; > repository: 'filetree://../bootstrap'; > load. > > âReplace missing traits" > Behavior compiledMethodAt: #fuelIgnoredInstanceVariableNames > ifPresent: [ :m | logger cr; nextPutAll: 'Trait method is present' ] > ifAbsent: [ > logger cr; nextPutAll: 'Recompile missing traits ...'. > > Behavior > compile: 'fuelIgnoredInstanceVariableNames > "Indicates which variables have to be ignored during serialization." > > ^#()'; > compile: 'fuelNew > "Answer an instance of mine in which serialized references will be injected." > > ^ self basicNew'; > compile: 'fuelNew: sizeRequested > "Answer an instance of mine in which serialized references will be injected." > > ^ self basicNew: sizeRequested'. > > "Ignore this one" > "Class > compile: 'fuelAccept: aGeneralMapper > ^self explicitRequirement.'." > > ClassDescription > compile: 'instanceVariableNamesDo: anUnaryBlock > "This is part of the interface between the compiler and a class''s instance or field names. > The class should enumerate anUnaryBlock with the instance variable name strings. The order is important. Names evaluated later will override the > same names occurring earlier." > > | superInstSize | > (superInstSize := self superclass notNil ifTrue: [self superclass instSize] ifFalse: [0]) > 0 ifTrue: > [self superclass instanceVariableNamesDo: anUnaryBlock]. > 1 to: self instSize - superInstSize do: > [:i| anUnaryBlock value: (self instVarNames at: i)]'. > ]. > > âAdd a tacky Pharo7Platform" > Smalltalk at: #FLPharo7Platform ifAbsent: [ > logger cr; nextPutAll: '>Creating FLPharo7Platform'. > (Smalltalk at: #FLPharo6Platform) subclass: #FLPharo7Platform. > (Smalltalk at: #FLPharo6Platform) class compile: 'isResponsibleForCurrentPlatform > ^true'. > ]. > > > logger cr; nextPutAll: 'Evaluating post load initialization...'. > (Smalltalk at: #FLPlatform) current addHacks. > > > > On 4 Aug 2017, at 12:48, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > > > On Fri, Aug 4, 2017 at 8:42 AM, Tim Mackinnon <tim(a)testit.works> wrote: > >> Sadly - false call, that was my logging message - so Iâm stumped why >> these traits arenât being compiled when I load in Fuel? >> >> However I have figured out why I get the BigEndian error - this is >> because the platform is now 7 and so the FlPharo06Platform is not being >> identified and the more generic FlPharoPlatform is then the default and it >> doesnât implement #isBigEndian. >> >> > > Max, should we do something to the Fuel Platform for Pharo 7? > > > > >> Tim >> >> >> >> On 4 Aug 2017, at 12:20, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Iâve spotted something interesting in my logs - when I added one of the >> missing methods to ClassDescription - I see in the log the message: >> >> Loaded -> Fuel-cypress.1 --- filetree:///builds/macta/P >> haroLambda/bootstrap --- cache >> ...finished baseline >> Compiling missing traits... >> Evaluating post load initialization... >> Finished Script. >> >> However when I remove all the compiles I donât see this message: >> >> Loaded -> Fuel-cypress.1 --- filetree:///builds/macta/P >> haroLambda/bootstrap --- cache >> ...finished baseline >> Evaluating post load initialization... >> Finished Script. >> >> >> So I wonder if this is similar to the problem I had in the previous 6.0 >> image - where some things didnât seem to compile properly (in that case, it >> was loading a missing class that didnât seem to cause recompilation). >> >> Tim >> >> On 4 Aug 2017, at 11:10, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Actually there is something weird going on - as now Iâm getting a >> complaint about "FLPharoPlatform had the subclass responsibility to >> implement #isBigEndianâ, and thatâs in the FuelPlatform-Pharo-06 which you >> said to include (and it looks like I am). >> >> I need to double check this - as I must be making some trivial mistake. >> >> Tim >> >> On 4 Aug 2017, at 11:01, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Hi Mariano - Iâve looked at this again, and it was my fault - I was >> compiling in : >> >> fuelAccept: aGeneralMapper >> ^self explicitRequirement. >> >> Because when I looked at the Traits for fuel - this is what it had for >> TClass? - as Iâm not so clear on traits, what does this mean - as I had >> just assumed that I should flatten the Fuel methods for TCLass, TBehaviour >> and TClassDescription - but I think Iâve misunderstood what I should do >> (and I guess from Pavelâs comment - I should really look at why that >> initial method was missing as it sounds like it should have worked - so >> maybe its an order loading thing?). >> >> Thanks, for helping by the way - this is proving very instructional. >> >> Tim >> >> On 3 Aug 2017, at 18:26, Mariano Martinez Peck <marianopeck(a)gmail.com> >> wrote: >> >> >> On Thu, Aug 3, 2017 at 2:14 PM, Tim Mackinnon <tim(a)testit.works> wrote: >> >>> Hi Mariano - I compiled in the trait methods manually and it got further >>> - but now Iâm seeing another error - Error: Explicitly required method", >>> "\u001b[0mLambda class(Object)>>error:", >>> "explicitRequirementâ, >>> >>> >> mmmm the stack is weird... it looks like if Class >> fuelAccept: would >> have the wrong implementation, that is, having the one from TClass: >> >> fuelAccept: aGeneralMapper >> ^self explicitRequirement. >> >> Rather than the correct one: >> >> fuelAccept: aGeneralMapper >> >> ^aGeneralMapper visitClass: self >> >> >> *Maybe the solution is to compile all those methods from traits BUT NOT >> those that are "^self explicitRequirement." because those will override the >> good methods.* >> >> If that doesn't work, then maybe can you print to console the each impl >> (source) of each implementor of #fuelAccept: ? >> >> Thoughts? >> >> >> >> >> >>> Any ideas? >>> >>> Tim >>> >>> "--- RUNNING ERROR HANDLER ---", >>> "Error: Explicitly required method", >>> "", >>> "\u001b[0m\u001b[31mError: Explicitly required method", >>> "\u001b[0mLambda class(Object)>>error:", >>> "explicitRequirement", >>> " self error: 'No decompiler available' in Lambda class(Object)>>explicitRequirement in Block: explicitRequirement...", >>> "False>>ifFalse:", >>> "Lambda class(Object)>>explicitRequirement", >>> "Lambda class(Class)>>fuelAccept:", >>> "FLLightGeneralMapper>>mapAndTrace:", >>> "FLLightGlobalMapper>>mapAndTrace:", >>> "FLPluggableSubstitutionMapper>>mapAndTrace:", >>> "FLAnalysis>>mapAndTrace:", >>> "FLAnalysis>>run", >>> "setDefaultAnalysis", >>> " self error: 'No decompiler available' in FLAnalyzer>>setDefaultAnalysis in Block: setDefaultAnalysis...", >>> "FLAnalyzer>>analysisFor:", >>> "FLSerialization>>analysisStep", >>> "FLSerialization>>run", >>> "setDefaultSerialization", >>> " self error: 'No decompiler available' in FLSerializer>>setDefaultSerialization in Block: setDefaultSerialization...", >>> "serialize: t1 on: t2", >>> " self error: 'No decompiler available' in FLSerializer>>serialize:on: in Block: serialize: t1 on: t2...", >>> "on: t1 globalEnvironment: t2 do: t3", >>> " self error: 'No decompiler available' in FLEncoder class>>on:globalEnvironment:do: in Block: on: t1 globalEnvironment: t2 do: t3...", >>> "BlockClosure>>ensure:", >>> "FLEncoder class>>on:globalEnvironment:do:", >>> "FLSerializer>>serialize:on:", >>> "NonInteractiveUIManager>>writeFuelContext:", >>> "Lambda class>>processDebug:", >>> "Lambda class>>processJSON:", >>> "Lambda class>>process:", >>> "activate", >>> >>> >>> > -- Mariano http://marianopeck.wordpress.com

Aug. 4, 2017

Re: [Pharo-dev] Creating the smallest server runtime footprint

by Tim Mackinnon

HURRAH - I got it to work, and Fuel out an error to S3 and read it back into a fat 6.1 image with a debug stack (which is so cool!). My footprint size is still a bit larger than I would like (31mb - image of 22.7mb - of which 1mb if fuel and 7mb is S3 and XMLParser support) - so I guess I need to find ways to trim down some of the addons (and any additional image size reductions would be helpful - if there are any to be had). Is there any easy tools/scripts to explore a headless image and figure out what takes the most size (maybe at a package level?). But definitely this has got me into a good place for experimentation. For the record I had to do the following to get things working: Define a new baseline: baseline: spec <baseline> spec for: #common do: [ spec package: 'Metacello-GitBasedRepository'; package: 'Metacello-GitHub'; package: 'FuelPlatform-Core'; package: 'FuelPlatform-Pharo-Core'; package: 'FuelPlatform-Pharo-06'; package: 'Fuel'. ]. Run the following script: Metacello new baseline: 'MetacelloGitBasedRepository'; repository: 'filetree://../bootstrap'; load. âReplace missing traits" Behavior compiledMethodAt: #fuelIgnoredInstanceVariableNames ifPresent: [ :m | logger cr; nextPutAll: 'Trait method is present' ] ifAbsent: [ logger cr; nextPutAll: 'Recompile missing traits ...'. Behavior compile: 'fuelIgnoredInstanceVariableNames "Indicates which variables have to be ignored during serialization." ^#()'; compile: 'fuelNew "Answer an instance of mine in which serialized references will be injected." ^ self basicNew'; compile: 'fuelNew: sizeRequested "Answer an instance of mine in which serialized references will be injected." ^ self basicNew: sizeRequested'. "Ignore this one" "Class compile: 'fuelAccept: aGeneralMapper ^self explicitRequirement.'." ClassDescription compile: 'instanceVariableNamesDo: anUnaryBlock "This is part of the interface between the compiler and a class''s instance or field names. The class should enumerate anUnaryBlock with the instance variable name strings. The order is important. Names evaluated later will override the same names occurring earlier." | superInstSize | (superInstSize := self superclass notNil ifTrue: [self superclass instSize] ifFalse: [0]) > 0 ifTrue: [self superclass instanceVariableNamesDo: anUnaryBlock]. 1 to: self instSize - superInstSize do: [:i| anUnaryBlock value: (self instVarNames at: i)]'. ]. âAdd a tacky Pharo7Platform" Smalltalk at: #FLPharo7Platform ifAbsent: [ logger cr; nextPutAll: '>Creating FLPharo7Platform'. (Smalltalk at: #FLPharo6Platform) subclass: #FLPharo7Platform. (Smalltalk at: #FLPharo6Platform) class compile: 'isResponsibleForCurrentPlatform ^true'. ]. logger cr; nextPutAll: 'Evaluating post load initialization...'. (Smalltalk at: #FLPlatform) current addHacks. > On 4 Aug 2017, at 12:48, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > > On Fri, Aug 4, 2017 at 8:42 AM, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: > Sadly - false call, that was my logging message - so Iâm stumped why these traits arenât being compiled when I load in Fuel? > > However I have figured out why I get the BigEndian error - this is because the platform is now 7 and so the FlPharo06Platform is not being identified and the more generic FlPharoPlatform is then the default and it doesnât implement #isBigEndian. > > > > Max, should we do something to the Fuel Platform for Pharo 7? > > > > Tim > > > >> On 4 Aug 2017, at 12:20, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >> >> Iâve spotted something interesting in my logs - when I added one of the missing methods to ClassDescription - I see in the log the message: >> >> Loaded -> Fuel-cypress.1 --- filetree:///builds/macta/PharoLambda/bootstrap <> --- cache >> ...finished baseline >> Compiling missing traits... >> Evaluating post load initialization... >> Finished Script. >> >> However when I remove all the compiles I donât see this message: >> >> Loaded -> Fuel-cypress.1 --- filetree:///builds/macta/PharoLambda/bootstrap <> --- cache >> ...finished baseline >> Evaluating post load initialization... >> Finished Script. >> >> >> So I wonder if this is similar to the problem I had in the previous 6.0 image - where some things didnât seem to compile properly (in that case, it was loading a missing class that didnât seem to cause recompilation). >> >> Tim >> >>> On 4 Aug 2017, at 11:10, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >>> >>> Actually there is something weird going on - as now Iâm getting a complaint about "FLPharoPlatform had the subclass responsibility to implement #isBigEndianâ, and thatâs in the FuelPlatform-Pharo-06 which you said to include (and it looks like I am). >>> >>> I need to double check this - as I must be making some trivial mistake. >>> >>> Tim >>> >>>> On 4 Aug 2017, at 11:01, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >>>> >>>> Hi Mariano - Iâve looked at this again, and it was my fault - I was compiling in : >>>> >>>> fuelAccept: aGeneralMapper >>>> ^self explicitRequirement. >>>> >>>> Because when I looked at the Traits for fuel - this is what it had for TClass? - as Iâm not so clear on traits, what does this mean - as I had just assumed that I should flatten the Fuel methods for TCLass, TBehaviour and TClassDescription - but I think Iâve misunderstood what I should do (and I guess from Pavelâs comment - I should really look at why that initial method was missing as it sounds like it should have worked - so maybe its an order loading thing?). >>>> >>>> Thanks, for helping by the way - this is proving very instructional. >>>> >>>> Tim >>>> >>>>> On 3 Aug 2017, at 18:26, Mariano Martinez Peck <marianopeck(a)gmail.com <mailto:marianopeck@gmail.com>> wrote: >>>>> >>>>> >>>>> On Thu, Aug 3, 2017 at 2:14 PM, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >>>>> Hi Mariano - I compiled in the trait methods manually and it got further - but now Iâm seeing another error - Error: Explicitly required method", >>>>> "\u001b[0mLambda class(Object)>>error:", >>>>> "explicitRequirementâ, >>>>> >>>>> >>>>> mmmm the stack is weird... it looks like if Class >> fuelAccept: would have the wrong implementation, that is, having the one from TClass: >>>>> >>>>> fuelAccept: aGeneralMapper >>>>> ^self explicitRequirement. >>>>> >>>>> Rather than the correct one: >>>>> >>>>> fuelAccept: aGeneralMapper >>>>> >>>>> ^aGeneralMapper visitClass: self >>>>> >>>>> >>>>> Maybe the solution is to compile all those methods from traits BUT NOT those that are "^self explicitRequirement." because those will override the good methods. >>>>> >>>>> If that doesn't work, then maybe can you print to console the each impl (source) of each implementor of #fuelAccept: ? >>>>> >>>>> Thoughts? >>>>> >>>>> >>>>> >>>>> >>>>> Any ideas? >>>>> >>>>> Tim >>>>> >>>>> "--- RUNNING ERROR HANDLER ---", >>>>> "Error: Explicitly required method", >>>>> "", >>>>> "\u001b[0m\u001b[31mError: Explicitly required method", >>>>> "\u001b[0mLambda class(Object)>>error:", >>>>> "explicitRequirement", >>>>> " self error: 'No decompiler available' in Lambda class(Object)>>explicitRequirement in Block: explicitRequirement...", >>>>> "False>>ifFalse:", >>>>> "Lambda class(Object)>>explicitRequirement", >>>>> "Lambda class(Class)>>fuelAccept:", >>>>> "FLLightGeneralMapper>>mapAndTrace:", >>>>> "FLLightGlobalMapper>>mapAndTrace:", >>>>> "FLPluggableSubstitutionMapper>>mapAndTrace:", >>>>> "FLAnalysis>>mapAndTrace:", >>>>> "FLAnalysis>>run", >>>>> "setDefaultAnalysis", >>>>> " self error: 'No decompiler available' in FLAnalyzer>>setDefaultAnalysis in Block: setDefaultAnalysis...", >>>>> "FLAnalyzer>>analysisFor:", >>>>> "FLSerialization>>analysisStep", >>>>> "FLSerialization>>run", >>>>> "setDefaultSerialization", >>>>> " self error: 'No decompiler available' in FLSerializer>>setDefaultSerialization in Block: setDefaultSerialization...", >>>>> "serialize: t1 on: t2", >>>>> " self error: 'No decompiler available' in FLSerializer>>serialize:on: in Block: serialize: t1 on: t2...", >>>>> "on: t1 globalEnvironment: t2 do: t3", >>>>> " self error: 'No decompiler available' in FLEncoder class>>on:globalEnvironment:do: in Block: on: t1 globalEnvironment: t2 do: t3...", >>>>> "BlockClosure>>ensure:", >>>>> "FLEncoder class>>on:globalEnvironment:do:", >>>>> "FLSerializer>>serialize:on:", >>>>> "NonInteractiveUIManager>>writeFuelContext:", >>>>> "Lambda class>>processDebug:", >>>>> "Lambda class>>processJSON:", >>>>> "Lambda class>>process:", >>>>> "activate", >>>>>

Aug. 4, 2017