Pharo-dev

By thread

pharo-dev@lists.pharo.org

3 participants
144616 messages

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

by Tim Mackinnon

Thanks Pavel - as Iâm downloading: curl -L -o min.zip https://ci.inria.fr/pharo/job/70-Bootstrap-32bit-Conversion/lastSuccessfulB… <https://ci.inria.fr/pharo/job/70-Bootstrap-32bit-Conversion/lastSuccessfulB…> I noted that the last successful build of that asset was: Last stable build (#29), 2 days 23 hr ago <https://ci.inria.fr/pharo/job/70-Bootstrap-32bit-Conversion/lastStableBuild/> Should I peg myself to a specific version that is more or less compatible with Pharo 6.1? I can see builds 28 (Aug 4 11am) or 27 (July 31?) - or should I go earlier? Can I rely on those builds sticking around - or should I cache one somewhere? Tim > On 7 Aug 2017, at 12:03, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > > > 2017-08-07 12:56 GMT+02:00 Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>>: > Iâve just switched branches and diffed - and yep, those methods were the difference. Sorry about the extra noise on that - I should have read your instructions a bit better - still Iâve learned a lot doing this, and am really chuffed that Iâve managed to get something working. > > Iâm looking at how to get my image size down a bit more - and have another thread on how to properly remove packages. > > How stable do you think the minimal image will be? Should I try and snapshot it as a baseline - or do you think I can keep pulling safely from Jenkins for a while? > > Pharo 7 is not stable in principle. You should not depend on the latest version but of course you can take a particular build that is supposed to be quite solid. Now you should rather take builds before Hermes integration and related refactorings. > > -- Pavel > > > > Tim > >> On 4 Aug 2017, at 21:19, Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>> wrote: >> >> yes, because master branch contains code of Pharo 6. For Pharo 7 we have flattened the traits in the kernel, but this is probably the only difference that affects Fuel packages >> >> -- Pavel >> >> 2017-08-04 20:32 GMT+02:00 Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>>: >> Ah - I checked out master. So should I have checked out dev? Would this explain it? >> >> I've appreciated the help a lot by the way. >> >> Tim >> >> Sent from my iPhone >> >> On 4 Aug 2017, at 17:28, Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>> wrote: >> >>> 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 <mailto:tim@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 <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. 7, 2017

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

by Guillermo Polito

On Mon, Aug 7, 2017 at 3:17 AM, Ben Coman <btc(a)openinworld.com> wrote: > > > On Mon, Aug 7, 2017 at 12:25 AM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> >> On Sun, Aug 6, 2017 at 5:46 PM, Ben Coman <btc(a)openinworld.com> wrote: >> >>> On Sun, Aug 6, 2017 at 3:45 PM, Guillermo Polito < >>> guillermopolito(a)gmail.com> wrote: >>> >>>> About tagging... It looks super ackward to me to tag EVERY commit with >>>> "build information". >>>> >>> >>> I'm not sure which comment your responding to, >>> >> >> yours :P. Yes, too early, I did not want to properly quote... >> >> >>> and not sure what you mean by "build information", >>> >> >> In this particular case I mean build number. >> >> but obviously someone may do several commits before doing a pull request, >>> as they work through developing and testing a fix for an Issue. Its only >>> the successful builds that are uploaded to files.pharo.org that are >>> important to tag. >>> >> >> But then, why not just going through the files in files.pharo.org and >> get the corresponding hash from there (since they have the hash they >> correspond to)? I do not see the practical usecase. It's just redundance, >> no? >> >> >>> Building does not mean releasing... I prefer the other way around: we >>>> tag builds with commit information. Like that we know how to reproduce the >>>> build. >>>> >>>> I'm ok with tagging build artifacts by explicitly saying "this is BUILD >>>> #X", which is ~= from "this is RELEASE #X". >>>> >>> >>> I'd imagine that tagging a commit as BUILD#X would be done as part of >>> the CI immediately before the upload to files.pharo.org. >>> >> >> That's what I wanto to avoid. Why is that required? The generated file >> already has a pointer to the git commit it was generated from. Why do we >> need the backpointer from git to the build? >> > > So should PharoLauncher attach a datestamp to each entity? > There needs to be something visible that a human can sort by. > I guess this is an interim solution until PharoLauncher is made to work > with Iceberg, but we need something working until then. > But PharoLauncher does not access commits. It never did. I think it gets all information from the file server and the naming schema of files... > > >> >> >>> >>> >>>> Moreover, before we needed to store ALL versions of the image because >>>> that was the way we versionned the system. Now, every commit in the >>>> #development branch should be buildable (delta some bugs of course ;)). >>>> This means that we can rebuild all images by just iterating the git history >>>> and building from scratch. >>>> >>> >>> I don't understand why you'd need to iterate git history. >>> Shouldn't you be able to rebuild an image from a single git commit? >>> >> >> Yes you are. I meant in here that "if you want to rebuild all images from >> files.pharo.org" you can walk all commits. >> > > got it. > > >> >> >>> >>> >>>> No need to store all images. >>>> >>> >>> Do you mean on files.pharo.com? >>> That might be a good later goal, but for now these resultant images are >>> useful to work with PharoLauncher without expending effort on redeveloping >>> that to also rebuild images on the fly. >>> >>> >> >> Yeah, I did not mean that we have to change it. But we have to keep in >> mind that before files.pharo.org was used for versioning purposes but in >> a process where we are bootstrapping from sources, the intermediate >> generated images are build artifacts and are just a "cache". >> >> I know the launcher depends on it right now, but does it make sense that >> it provides access to every alpha image >> > > It may make sense when someone wants to bisect an Issue to determine when > a defect was introduced. > How does the time downloading ten images compare to bootstrapping ten > images? > True true. That's why I say it's a cache :). While this is cheap enough to have all builds stored, I'm ok with it. > > > >> >> >>> Pharo${IMAGE_KIND}-7.0.0-arch.32bit.sha.${HASH}.build.${BUIL >>>>> D_NUMBER}.zip >>>>> >>>> >>> +1 to Torsten's suggestion to put the BUILD_NUMBER first, since it is >>> more sortable than HASH. >>> >> >> Ok, that's easily doable :) >> >> https://github.com/pharo-project/pharo/pull/185/files#diff-b >> f8112f4242808a7d70517e28088f72b >> >> >>> By "arch", do you mean Win/Linux/Mac? Or were labelling the bit-ness >>> field? >>> >> >> bitness. Images are portable between operating systems but not between >> 32&64 bit vms. >> >> >>> Also, is it important to prepend these with the numbers with "build." >>> and "sha." fieldname strings? This bulks out the name increases the chance >>> some interface needs to mangle the name to fit into a thin column. >>> >> >> I like that they make the metadata more explicit. Otherwise we will start >> having strange scripts that have magic numbers here and there. At least >> like this we can read the file name and identify what is each field. I >> prefer to pay some extra bytes in filenames... >> >> About column names in UIs.... That's a UI problem. I'd not design the >> filename of our build artifacts because of a UI... >> > > fair enough. > > >> >> >>> >>> >>> While we are discussion version naming (and I ask this from a position >>> of ignorance) >>> could you discuss with your team, without insider knowledge, how do we >>> distinguish between the released 7.0.0 and all the 7.0.0 development builds >>> heading towards that release? >>> Can we add something to distinguish the development phase >>> i.e. alpha/beta/rc/release (which coincidentally sort well with build >>> numbers.) >>> >>> Pharo-${IMAGE_KIND}${BITNESS}-7.0.0-alpha.${BUILD_NUMBER}.${HASH}.zip >>> Pharo-${IMAGE_KIND}${BITNESS}-7.0.0-beta.${BUILD_NUMBER}.${HASH}.zip >>> Pharo-${IMAGE_KIND}${BITNESS}-7.0.0-rc.${BUILD_NUMBER}.${HASH}.zip >>> Pharo-${IMAGE_KIND}${BITNESS}-7.0.0-release.${BUILD_NUMBER}.${HASH}. >>> zip >>> >>> beta might be the defined point to ask applications to test-port to the >>> new version, this perhaps being the optimum point to get fixes into the the >>> next release. >>> >> >>> or if you don't want to be that sophisticated, maybe just phases dev/rel >>> >> >> I like that. The only thing is that right now what is "alpha" version is >> managed in the file server as "latest". That will otherwise break zeroconf >> scripts that depend on that. >> >> I'd say every build in development is alpha so far. At some point we will >> move to beta. Releases and release candidates should be managed explicitly >> (like there is someone that will decide "this is a release and I'll tag it >> explicitly like it"). >> >> >>> >>> or for a more continuous release process, maybe '#' for the patch >>> number... >>> Pharo-${IMAGE_KIND}${BITNESS}-7.0.#-${BUILD_NUMBER}.${HASH}.zip >>> (since '#' sorts before '0') >>> >> >> I did not get this one. >> > > I was thinking something like below, but perhaps it gets too awkward after > 7.0.0. > > Pharo-${IMAGE_KIND}${BITNESS}-7.0.#-.build.70001.sha.${HASH}.zip > Pharo-${IMAGE_KIND}${BITNESS}-7.0.#-.build.70002.sha.${HASH}.zip > ... > Pharo-${IMAGE_KIND}${BITNESS}-7.0.#-.build.70639.sha.${HASH}.zip > Pharo-${IMAGE_KIND}${BITNESS}-7.0.0-.build.70640.sha.${HASH}.zip > Pharo-${IMAGE_KIND}${BITNESS}-7.0.1-.build.70641.sha.${HASH}.zip > Pharo-${IMAGE_KIND}${BITNESS}-7.0.2-.build.70642.sha.${HASH}.zip > Ah! I understand now. You want to tag with a # the latest build. > > > cheers -ben > -- 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

Aug. 7, 2017

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

by Pavel Krivanek

2017-08-07 12:56 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: > Iâve just switched branches and diffed - and yep, those methods were the > difference. Sorry about the extra noise on that - I should have read your > instructions a bit better - still Iâve learned a lot doing this, and am > really chuffed that Iâve managed to get something working. > > Iâm looking at how to get my image size down a bit more - and have another > thread on how to properly remove packages. > > How stable do you think the minimal image will be? Should I try and > snapshot it as a baseline - or do you think I can keep pulling safely from > Jenkins for a while? > Pharo 7 is not stable in principle. You should not depend on the latest version but of course you can take a particular build that is supposed to be quite solid. Now you should rather take builds before Hermes integration and related refactorings. -- Pavel > > Tim > > On 4 Aug 2017, at 21:19, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > yes, because master branch contains code of Pharo 6. For Pharo 7 we have > flattened the traits in the kernel, but this is probably the only > difference that affects Fuel packages > > -- Pavel > > 2017-08-04 20:32 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: > >> Ah - I checked out master. So should I have checked out dev? Would this >> explain it? >> >> I've appreciated the help a lot by the way. >> >> Tim >> >> Sent from my iPhone >> >> On 4 Aug 2017, at 17:28, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: >> >> 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> w >>>>> rote: >>>>> >>>>>> 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> w >>>>>> rote: >>>>>> >>>>>>> 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. 7, 2017

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

by Tim Mackinnon

Iâve just switched branches and diffed - and yep, those methods were the difference. Sorry about the extra noise on that - I should have read your instructions a bit better - still Iâve learned a lot doing this, and am really chuffed that Iâve managed to get something working. Iâm looking at how to get my image size down a bit more - and have another thread on how to properly remove packages. How stable do you think the minimal image will be? Should I try and snapshot it as a baseline - or do you think I can keep pulling safely from Jenkins for a while? Tim > On 4 Aug 2017, at 21:19, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > yes, because master branch contains code of Pharo 6. For Pharo 7 we have flattened the traits in the kernel, but this is probably the only difference that affects Fuel packages > > -- Pavel > > 2017-08-04 20:32 GMT+02:00 Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>>: > Ah - I checked out master. So should I have checked out dev? Would this explain it? > > I've appreciated the help a lot by the way. > > Tim > > Sent from my iPhone > > On 4 Aug 2017, at 17:28, Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>> wrote: > >> 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 <mailto:tim@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 <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. 7, 2017

Re: [Pharo-dev] ZnEasy question

by Max Leske

Hi Milton, >From the URL RFC (http://tools.ietf.org/html/rfc3986, relevant grammar attached below) it seems that 'https://' in indeed a valid path component. ZnUrl seems to remove empty segments (which '//' would be) but that is not correct according to the RFC (empty segments appear to be valid components of a URL path). An empty path segment is valid, as "path-absolute" in your case consists of multiple "'/' segment" sequences, where "segment" is allowed to be empty. Your should open a bug report for this. Max path = path-abempty ; begins with '/' or is empty / path-absolute ; begins with '/' but not '//' / path-noscheme ; begins with a non-colon segment / path-rootless ; begins with a segment / path-empty ; zero characters path-abempty = *( '/' segment ) path-absolute = '/' [ segment-nz *( '/' segment ) ] path-noscheme = segment-nz-nc *( '/' segment ) path-rootless = segment-nz *( '/' segment ) path-empty = 0<pchar> segment = *pchar segment-nz = 1*pchar segment-nz-nc = 1*( unreserved / pct-encoded / sub-delims / '@' ) ; non-zero-length segment without any colon ':' pchar = unreserved / pct-encoded / sub-delims / ':' / '@' unreserved = ALPHA / DIGIT / '-' / '.' / '_' / '~' pct-encoded = '%' HEXDIG HEXDIG sub-delims = '!' / '$' / '&' / ''' / '(' / ')' / '*' / '+' / ',' / ';' / '=' On 5 August 2017 at 03:16:16, milton mamani (akevalion(a)gmail.com) wrote: Hi to all I want to use the next instruction in my code response := ZnEasy get: 'https://archive.softwareheritage.org/api/1/ origin/git/url/https://github.com/hylang/hy'. response. The previous code works from command line or in a webbrowser, but I does not work with ZnEasy Because it takes the previous link as: a ZnRequest(GET /api/1/origin/git/url/https:/github.com/hylang/hy) Could you please tell me what can I do for this situation? Cheers, Milton

Aug. 7, 2017

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

by Ben Coman

On Mon, Aug 7, 2017 at 12:25 AM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > > On Sun, Aug 6, 2017 at 5:46 PM, Ben Coman <btc(a)openinworld.com> wrote: > >> On Sun, Aug 6, 2017 at 3:45 PM, Guillermo Polito < >> guillermopolito(a)gmail.com> wrote: >> >>> About tagging... It looks super ackward to me to tag EVERY commit with >>> "build information". >>> >> >> I'm not sure which comment your responding to, >> > > yours :P. Yes, too early, I did not want to properly quote... > > >> and not sure what you mean by "build information", >> > > In this particular case I mean build number. > > but obviously someone may do several commits before doing a pull request, >> as they work through developing and testing a fix for an Issue. Its only >> the successful builds that are uploaded to files.pharo.org that are >> important to tag. >> > > But then, why not just going through the files in files.pharo.org and get > the corresponding hash from there (since they have the hash they correspond > to)? I do not see the practical usecase. It's just redundance, no? > > >> Building does not mean releasing... I prefer the other way around: we tag >>> builds with commit information. Like that we know how to reproduce the >>> build. >>> >>> I'm ok with tagging build artifacts by explicitly saying "this is BUILD >>> #X", which is ~= from "this is RELEASE #X". >>> >> >> I'd imagine that tagging a commit as BUILD#X would be done as part of the >> CI immediately before the upload to files.pharo.org. >> > > That's what I wanto to avoid. Why is that required? The generated file > already has a pointer to the git commit it was generated from. Why do we > need the backpointer from git to the build? > So should PharoLauncher attach a datestamp to each entity? There needs to be something visible that a human can sort by. I guess this is an interim solution until PharoLauncher is made to work with Iceberg, but we need something working until then. > > >> >> >>> Moreover, before we needed to store ALL versions of the image because >>> that was the way we versionned the system. Now, every commit in the >>> #development branch should be buildable (delta some bugs of course ;)). >>> This means that we can rebuild all images by just iterating the git history >>> and building from scratch. >>> >> >> I don't understand why you'd need to iterate git history. >> Shouldn't you be able to rebuild an image from a single git commit? >> > > Yes you are. I meant in here that "if you want to rebuild all images from > files.pharo.org" you can walk all commits. > got it. > > >> >> >>> No need to store all images. >>> >> >> Do you mean on files.pharo.com? >> That might be a good later goal, but for now these resultant images are >> useful to work with PharoLauncher without expending effort on redeveloping >> that to also rebuild images on the fly. >> >> > > Yeah, I did not mean that we have to change it. But we have to keep in > mind that before files.pharo.org was used for versioning purposes but in > a process where we are bootstrapping from sources, the intermediate > generated images are build artifacts and are just a "cache". > > I know the launcher depends on it right now, but does it make sense that > it provides access to every alpha image > It may make sense when someone wants to bisect an Issue to determine when a defect was introduced. How does the time downloading ten images compare to bootstrapping ten images? > > >> Pharo${IMAGE_KIND}-7.0.0-arch.32bit.sha.${HASH}.build.${BUILD_NUMBER}.zip >>>> >>> >> +1 to Torsten's suggestion to put the BUILD_NUMBER first, since it is >> more sortable than HASH. >> > > Ok, that's easily doable :) > > https://github.com/pharo-project/pharo/pull/185/files#diff- > bf8112f4242808a7d70517e28088f72b > > >> By "arch", do you mean Win/Linux/Mac? Or were labelling the bit-ness >> field? >> > > bitness. Images are portable between operating systems but not between > 32&64 bit vms. > > >> Also, is it important to prepend these with the numbers with "build." and >> "sha." fieldname strings? This bulks out the name increases the chance some >> interface needs to mangle the name to fit into a thin column. >> > > I like that they make the metadata more explicit. Otherwise we will start > having strange scripts that have magic numbers here and there. At least > like this we can read the file name and identify what is each field. I > prefer to pay some extra bytes in filenames... > > About column names in UIs.... That's a UI problem. I'd not design the > filename of our build artifacts because of a UI... > fair enough. > > >> >> >> While we are discussion version naming (and I ask this from a position of >> ignorance) >> could you discuss with your team, without insider knowledge, how do we >> distinguish between the released 7.0.0 and all the 7.0.0 development builds >> heading towards that release? >> Can we add something to distinguish the development phase >> i.e. alpha/beta/rc/release (which coincidentally sort well with build >> numbers.) >> >> Pharo-${IMAGE_KIND}${BITNESS}-7.0.0-alpha.${BUILD_NUMBER}.${HASH}.zip >> Pharo-${IMAGE_KIND}${BITNESS}-7.0.0-beta.${BUILD_NUMBER}.${HASH}.zip >> Pharo-${IMAGE_KIND}${BITNESS}-7.0.0-rc.${BUILD_NUMBER}.${HASH}.zip >> Pharo-${IMAGE_KIND}${BITNESS}-7.0.0-release.${BUILD_NUMBER}.${HASH}.zip >> >> beta might be the defined point to ask applications to test-port to the >> new version, this perhaps being the optimum point to get fixes into the the >> next release. >> > >> or if you don't want to be that sophisticated, maybe just phases dev/rel >> > > I like that. The only thing is that right now what is "alpha" version is > managed in the file server as "latest". That will otherwise break zeroconf > scripts that depend on that. > > I'd say every build in development is alpha so far. At some point we will > move to beta. Releases and release candidates should be managed explicitly > (like there is someone that will decide "this is a release and I'll tag it > explicitly like it"). > > >> >> or for a more continuous release process, maybe '#' for the patch >> number... >> Pharo-${IMAGE_KIND}${BITNESS}-7.0.#-${BUILD_NUMBER}.${HASH}.zip >> (since '#' sorts before '0') >> > > I did not get this one. > I was thinking something like below, but perhaps it gets too awkward after 7.0.0. Pharo-${IMAGE_KIND}${BITNESS}-7.0.#-.build.70001.sha.${HASH}.zip Pharo-${IMAGE_KIND}${BITNESS}-7.0.#-.build.70002.sha.${HASH}.zip ... Pharo-${IMAGE_KIND}${BITNESS}-7.0.#-.build.70639.sha.${HASH}.zip Pharo-${IMAGE_KIND}${BITNESS}-7.0.0-.build.70640.sha.${HASH}.zip Pharo-${IMAGE_KIND}${BITNESS}-7.0.1-.build.70641.sha.${HASH}.zip Pharo-${IMAGE_KIND}${BITNESS}-7.0.2-.build.70642.sha.${HASH}.zip cheers -ben

Aug. 7, 2017

Re: [Pharo-dev] About cr and lf

by Stephan Eggermont

On 06/08/17 15:25, Peter Uhnak wrote: > Hi, > > that's why one of the proposals was to configure the stream to either use always specific line endings > > stream beForWindows. > stream newLine. "outputs CRLF irrespective of where the image is currently running" > > and > > stream beForCurrentPlatform. > stream newLine. "returns whatever it is currently running on" Hmm. I'm pretty sure it should not be a stream responsibility. What about the encoder? Stephan

Aug. 6, 2017

Re: [Pharo-dev] About cr and lf

by Stephane Ducasse

Hi Guille I agree with you :). Stef On Sun, Aug 6, 2017 at 11:05 AM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > > > On Sun, Aug 6, 2017 at 10:54 AM, Stephane Ducasse <stepharo.self(a)gmail.com > > wrote: > >> Agreed :) >> >> But so far what do we do? >> >> >> - #cr and #lf just put this character in the stream. >> > yes. I would even be a bit more agressive. Streams work on any collection, > not only on strings (that's why I think this is buggy!). We should move cr > and lf to the character write streams. People that want to write characters > should use a character write stream not a general purpose stream (on e.g., > a Set). > > >> - #newLine put the underlying OS line ending. >> > > this could just exist in a decorator, used in "text writing streams". This > implies files, transcript, stdio. But not sockets, collections > >> >> Then we should revisit all the cr inside the system and use newline. >> > yes > > >> Then we should think about the internal usage of cr by default in >> Pharo (We should change it). >> > > Yes, and we should teach people (this means documenting :P) the correct > usage of streams :). > > >> Does it make sense? >> Stef >> >> Stef >> >> On Sun, Aug 6, 2017 at 10:36 AM, Sven Van Caekenberghe <sven(a)stfx.eu> >> wrote: >> > >> >> On 6 Aug 2017, at 08:59, Guillermo Polito <guillermopolito(a)gmail.com> >> wrote: >> >> >> >> Can somebody propose an implementation besides on top of this >> discussion? I propose such an implementation should take the form of a >> stream decorator instead of changing the base implementation. >> > >> > YES, a decorator ! >> > >> > We want simpler streams, not the old complex ones. Less API, less >> functionality. >> > >> >> Guille >> >> >> >> On Sun, Aug 6, 2017 at 12:01 AM, Peter Uhnak <i.uhnak(a)gmail.com> >> wrote: >> >> Hi, >> >> >> >> just to (hopefully) clarify my intention, maybe pseudocode would >> describe my thoughts better. >> >> >> >> Stream>>beForWindows >> >> "Use consistenly Windows line endings (CRLF) in the stream" >> >> self convertLineEndings: true >> >> lineEnding := String crlf >> >> >> >> Stream>>convertLineEndings: aBoolean >> >> "automatically convert line endings to the predefined one" >> >> convertLineEndings := aBoolean >> >> >> >> Stream>>nl >> >> self nextPutAll: lineEnding >> >> >> >> Stream>>cr >> >> convertLineEndings ifTrue: [ >> >> self deprected: 'Using #cr/#lf for generic newlines is >> deprected, use #nl instead". >> >> self nl. >> >> ] ifFalse: [ >> >> self nextPutAll: String cr. >> >> ] >> >> >> >> >> >> So when "convertLineEndings = true", then using anything else than #nl >> would warn the user that they should use #nl instead (as they explicitly >> requested to have the line endings consistend). >> >> >> >> And when "convertLineEndings = false", it would behave pretty much the >> same way as now, #cr would write #cr, etc. >> >> >> >> >> >> With such approach imho >> >> >> >> * output of existing code wouldn't be broken >> >> * when switching to new scheme (#nl) the programmer would be warned >> where the missed a change >> >> * it will be easier to keep the newlines consistent >> >> >> >> Peter >> >> >> >> On Sat, Aug 05, 2017 at 11:30:58AM +0200, Esteban Lorenzano wrote: >> >> > >> >> > > On 5 Aug 2017, at 11:17, Peter Uhnak <i.uhnak(a)gmail.com> wrote: >> >> > > >> >> > >> I think there is a consensus we need to keep #cr and #lf as >> intended >> >> > > >> >> > > Is there? >> >> > > >> >> > > My argument was that there's no (obvious) reason to combine >> different line endings in the same document. Therefore if you were to use >> #cr, #lf, #crlf, you would actually mean that you just want to enter >> newline. >> >> > >> >> > no, sometimes you want to enforce a specific line ending. You will >> not mix, but you will not use the one from platform. Also, sometimes you >> actually can use #cr and #lf different as their immediate, common use (Iâve >> seen some weird exporting formats). >> >> > >> >> > > >> >> > > Similar problem arises when you would write a multiline string: >> >> > > >> >> > > stream nextPutAll: 'first line with enter >> >> > > second line'. >> >> > > >> >> > > Stored in method this will most likely contain Pharo's internal >> representation (#cr), even though you just want a new line, and not >> specifically #cr. (I've lost count how many times tests on CI failed >> because of this.) >> >> > > >> >> > > Considering the above, my opinion is: >> >> > > >> >> > > 1) by default #cr, #lf, #crLf, #nl (#newLine) will write whatever >> is globally configured for the stream (#beFor*) >> >> > >> >> > No, I strongly disagree. >> >> > #cr and #lf are ascii characters and should not be redefined. >> >> > >> >> > > 2) if one wanted to combine different line endings in the same >> stream, there should be an option to disable autoconversion. >> (Stream>>noNewLineAutoconversion) >> >> > > >> >> > > If (1) is much more common than (2), then imho autoconversion >> should cause no issues. >> >> > > If (1) is NOT that much more common than (2), then autoconversion >> wouldn't be beneficial. >> >> > > >> >> > > Autoconversion could also make transition easier because existing >> code will suddenly work as intended here without breaking anything >> (hopefully). >> >> > >> >> > Sorry, I do not see what this approach solves than the other one >> does not (and as I see, this one is a lot more complicated and prone to >> confusion). >> >> > >> >> > cheers, >> >> > Esteban >> >> > >> >> > > >> >> > > Peter >> >> > > >> >> > > >> >> > > On Sat, Aug 05, 2017 at 10:49:02AM +0200, Esteban Lorenzano wrote: >> >> > >> I think there is a consensus we need to keep #cr and #lf as >> intended, yet to add some kind of #newLine (which btw is different to EOL >> :P) vocabulary, isnât? >> >> > >> >> >> > >> In this, I favour Peter approach for define line ending >> convention (the way #newLine will work)â¦ and of course by default it should >> use the one from the current platform. >> >> > >> >> >> > >> anything agains this approach? >> >> > >> >> >> > >> Esteban >> >> > >> >> >> > >> >> >> > >>> On 4 Aug 2017, at 23:48, Tudor Girba <tudor(a)tudorgirba.com> >> wrote: >> >> > >>> >> >> > >>> +1. >> >> > >>> >> >> > >>> We need a basic representation of those characters. Logical ones >> should be derived from the simple ones. >> >> > >>> >> >> > >>> Doru >> >> > >>> >> >> > >>> >> >> > >>>> On Aug 4, 2017, at 3:44 PM, Esteban Lorenzano < >> estebanlm(a)gmail.com> wrote: >> >> > >>>> >> >> > >>>> >> >> > >>>>> 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 < >> 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/dami >> en.pollet >> >> > >>>> >> >> > >>> >> >> > >>> -- >> >> > >>> www.tudorgirba.com >> >> > >>> www.feenk.com >> >> > >>> >> >> > >>> "Presenting is storytelling." >> >> > >>> >> >> > >>> >> >> > >> >> >> > >> >> >> > > >> >> > >> >> > >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> Guille Polito >> >> >> >> Research Engineer >> >> French National Center for Scientific Research - http://www.cnrs.fr >> >> >> >> >> >> Web: http://guillep.github.io >> >> Phone: +33 06 52 70 66 13 >> > >> > >> >> > > > -- > > > > 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> >

Aug. 6, 2017

Re: [Pharo-dev] [Pharo-users] [ann] moldable brick editor - alpha

by Aliaksei Syrel

Hi Denis, Thanks a lot for looking into it :) See my answers for every point below: 1) Loading in Pharo 7 signal dependency error: That is true, but I can not do anything about it now :( OSWindow-SDL depends on Athens (while it should not). In Bloc we don't use / need Athens but because of OSWindow's dependency Athens tries to update itself. Additionally the classes you mentioned were removed from the system, while Athens adds extension methods to them => error during installation. In Pharo 6 there is no error, though. 2) Text cursor up/down is not working correctly when text is wrapped. Indeed, up/down movement is a bit tricky :) But its implementation is in fact very interesting. Take a look at this video: â Bloc-FocusNavigationLong.mov <https://drive.google.com/file/d/0B-bMBVDOi3oTVEFlemwzeTNibEk/view?usp=drive…> â Bloc has support of element-independent *visual* focus navigation. In the editor we reuse it for the cursor (one cursor for a moment but we target to support multiple). However, because of text's special nature it is not super smooth but will be improved :) 3) I look a bit at text commands (TextEditorCommand) and found that current > KeyMapping package ($a asShortcut) is not used. Instead there is new > hierarchy of BlKeyCombination. It is a special bloc feature that requires its own announcement. As a teaser I can say that we rely on *Key* and not on *Character + modifiers* while defining shortcuts. It allows us to build any *key* combinations possible. For example we distinguish left and right shift, left and right meta, etc. Shortcuts can consist only of one Key or be just only right shift :) It is super flexible but we will come to it later ;) P.S. arrows are also treated at shortcuts and not as keystroke: meaning that there is no need to do this: [image: Inline images 1] 4) I thing we should try to use Commander for new UI widgets. For example > It is very naturally applied to TextEditorCommand hierarchy. And it will > automatically remove hardcoded shortcuts defined in method > BrTextEditor>>onAttached: Commander didn't yet made it into release :) Just as prove of concept I hardcoded shortcuts in onAttached: tin order to show that *they all* are in one single place. There is no other place where we check if any modifier keys pressed! It is beautiful and will allow us to ship editor with fully customisable shortcuts (nothing should stop us from having vim bindings). Cheers, Alex On 6 August 2017 at 19:17, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Good job guys. > > Here is my feedback: > > 1) Loading in Pharo 7 signal dependency error: > > This package depends on the following classes: > NewList > NewListRenderer > TabActionButton > Tab > TabBar > > Then I proceed and it was loaded fine. And editor works like in demo. > > 2) Text cursor up/down is not working correctly when text is wrapped. > > - it jumps between real text line instead of visual wrapped lines. > > - it skips empty lines > > - sometimes it is just not moved (not found concrete case) > > > 3) I look a bit at text commands (TextEditorCommand) and found that > current KeyMapping package ($a asShortcut) is not used. Instead there is > new hierarchy of BlKeyCombination. > What the reason for this? > > 4) I thing we should try to use Commander for new UI widgets. For example > It is very naturally applied to TextEditorCommand hierarchy. And it will > automatically remove hardcoded shortcuts defined in method > BrTextEditor>>onAttached: > > > > > 2017-08-05 0:19 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > >> Hi, >> >> We are very happy to announce the alpha version of a moldable editor >> built in Brick (https://github.com/pharo-graphics/Brick) which is based >> on Bloc (https://github.com/pharo-graphics/Bloc) This is primarily the >> work of Alex Syrel. The project was initially financially sponsored by ESUG >> and it is currently supported by feenk. And of course, the project is based >> on the tremendous work that went into Bloc and Brick by all contributors. >> >> Take a look at this 2 min video: >> https://www.youtube.com/watch?v=2vy6VMJM9W4&feature=youtu.be >> >> The basic editor works and it is both flexible and scalable. For example, >> the last example shown in the video is an editor opened on 1M >> characters, which is reasonably large, and as can be seen see one can >> interact with it as smoothly as with the one screen text. It actually works >> just as fine with 100M characters. >> >> The functionality of the editor includes: rendering, line wrapping, >> keypress and shortcut handling, navigation, selection and text styling. >> Currently, the editor is 1260 lines of code including method and class >> comments. This is not large for a text editor and this is possible because >> most of the work is done by generic concepts that already exist in Bloc >> such as layouts and text measurements. Beside the small maintenance cost, >> the benefit is that we have the option to build all sorts of variations >> with little effort. That is why we call this a moldable text editor. >> >> Another benefit of using elements and layouts is that we can also embed >> other kinds of non-text elements with little effort (such as pictures), >> and obtain a rich and live text editor. We already have basic examples for >> this behavior, and we will focus more in the next period on this area. >> >> The next immediate step is to add syntax highlighting. Beside the text >> attributes problem, this issue will also exercise the thread-safety >> the implementation is. The underlying structure ( >> https://en.wikipedia.org/wiki/Rope_(data_structure)) is theoretically >> thread-safe, but it still needs to be proven in practice. >> >> We think this is a significant step because the editor was the main piece >> missing in Brick and it will finally allow us to build value that can be >> directly perceived by regular users on top of Brick and this, in turn, will >> generate more traction. Please also note that because now Bloc is directly >> embeddable in Morphic it means that we can actually start using it right >> away. For example, the picture below shows the text element being shown >> through a live preview in the GTInspector. >> >> [image: Playground @ â¢ a8rEditorE1ement x Page â BrRopedText string: >> Emphasizing everything text : nothing' text attributes: { >> BrFontSizeAttribute size: 66 } . text attributes: { BrTextForegroundAttri >> bute paint: ( BILinearGradientPaint new stops: 9 â> Color red . start: end: >> from: 1 to: 11; Color blue} ; attributes: { BrFontWeightAttribute bold } >> from: 12 attributes: { BrFontEmphasisAttribute italic from: emphasi zi ng >> to: 17; 18 to: 22; Raw Preview Live User data Metrics Meta Em hasizing ever >> thin is emphasizing nothing attributes: { BrTextBackgroundAttribute paint: >> Color yellow from: 27 to: 37; attributes: { BrFontWeightAttribute thin. >> BrTextForegroundAttribute paint: Color gray. BrFontSizeAttribute size: 40 >> from: 39 to: 45. element : BrEditorElement new size: 400 @ 600; edi tor: >> (BrTextEdi tor new text: text) .] >> >> This is another puzzle piece towards the final goal of engineering the >> future of the Pharo user interface. There is still a long way to go to >> reach that goal, but considering the work that is behind us, that goal that >> looked so illusive when Alain and Stef initiated the Bloc project is now >> palpable. >> >> We will continue the work on this over the next period and we expect to >> announce new developments soon. >> >> If you want to play with it, you can load the code like this (works in >> both Pharo 6 and 7): >> Iceberg enableMetacelloIntegration: true. >> Metacello new >> baseline: 'Brick'; >> repository: 'github://pharo-graphics/Brick/src'; >> load: #development >> >> Please let us know what you think. >> >> Cheers, >> Alex and Doru >> >> >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "What is more important: To be happy, or to make happy?" >> >> >

Aug. 6, 2017

Re: [Pharo-dev] [Pharo-users] [ann] moldable brick editor - alpha

by Denis Kudriashov

Good job guys. Here is my feedback: 1) Loading in Pharo 7 signal dependency error: This package depends on the following classes: NewList NewListRenderer TabActionButton Tab TabBar Then I proceed and it was loaded fine. And editor works like in demo. 2) Text cursor up/down is not working correctly when text is wrapped. - it jumps between real text line instead of visual wrapped lines. - it skips empty lines - sometimes it is just not moved (not found concrete case) 3) I look a bit at text commands (TextEditorCommand) and found that current KeyMapping package ($a asShortcut) is not used. Instead there is new hierarchy of BlKeyCombination. What the reason for this? 4) I thing we should try to use Commander for new UI widgets. For example It is very naturally applied to TextEditorCommand hierarchy. And it will automatically remove hardcoded shortcuts defined in method BrTextEditor>>onAttached: 2017-08-05 0:19 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > We are very happy to announce the alpha version of a moldable editor built > in Brick (https://github.com/pharo-graphics/Brick) which is based on > Bloc (https://github.com/pharo-graphics/Bloc) This is primarily the work > of Alex Syrel. The project was initially financially sponsored by ESUG and > it is currently supported by feenk. And of course, the project is based on > the tremendous work that went into Bloc and Brick by all contributors. > > Take a look at this 2 min video: > https://www.youtube.com/watch?v=2vy6VMJM9W4&feature=youtu.be > > The basic editor works and it is both flexible and scalable. For example, > the last example shown in the video is an editor opened on 1M > characters, which is reasonably large, and as can be seen see one can > interact with it as smoothly as with the one screen text. It actually works > just as fine with 100M characters. > > The functionality of the editor includes: rendering, line wrapping, > keypress and shortcut handling, navigation, selection and text styling. > Currently, the editor is 1260 lines of code including method and class > comments. This is not large for a text editor and this is possible because > most of the work is done by generic concepts that already exist in Bloc > such as layouts and text measurements. Beside the small maintenance cost, > the benefit is that we have the option to build all sorts of variations > with little effort. That is why we call this a moldable text editor. > > Another benefit of using elements and layouts is that we can also embed > other kinds of non-text elements with little effort (such as pictures), > and obtain a rich and live text editor. We already have basic examples for > this behavior, and we will focus more in the next period on this area. > > The next immediate step is to add syntax highlighting. Beside the text > attributes problem, this issue will also exercise the thread-safety > the implementation is. The underlying structure (https://en.wikipedia.org/ > wiki/Rope_(data_structure)) is theoretically thread-safe, but it still > needs to be proven in practice. > > We think this is a significant step because the editor was the main piece > missing in Brick and it will finally allow us to build value that can be > directly perceived by regular users on top of Brick and this, in turn, will > generate more traction. Please also note that because now Bloc is directly > embeddable in Morphic it means that we can actually start using it right > away. For example, the picture below shows the text element being shown > through a live preview in the GTInspector. > > [image: Playground @ â¢ a8rEditorE1ement x Page â BrRopedText string: > Emphasizing everything text : nothing' text attributes: { > BrFontSizeAttribute size: 66 } . text attributes: { BrTextForegroundAttri > bute paint: ( BILinearGradientPaint new stops: 9 â> Color red . start: end: > from: 1 to: 11; Color blue} ; attributes: { BrFontWeightAttribute bold } > from: 12 attributes: { BrFontEmphasisAttribute italic from: emphasi zi ng > to: 17; 18 to: 22; Raw Preview Live User data Metrics Meta Em hasizing ever > thin is emphasizing nothing attributes: { BrTextBackgroundAttribute paint: > Color yellow from: 27 to: 37; attributes: { BrFontWeightAttribute thin. > BrTextForegroundAttribute paint: Color gray. BrFontSizeAttribute size: 40 > from: 39 to: 45. element : BrEditorElement new size: 400 @ 600; edi tor: > (BrTextEdi tor new text: text) .] > > This is another puzzle piece towards the final goal of engineering the > future of the Pharo user interface. There is still a long way to go to > reach that goal, but considering the work that is behind us, that goal that > looked so illusive when Alain and Stef initiated the Bloc project is now > palpable. > > We will continue the work on this over the next period and we expect to > announce new developments soon. > > If you want to play with it, you can load the code like this (works in > both Pharo 6 and 7): > Iceberg enableMetacelloIntegration: true. > Metacello new > baseline: 'Brick'; > repository: 'github://pharo-graphics/Brick/src'; > load: #development > > Please let us know what you think. > > Cheers, > Alex and Doru > > > > -- > www.tudorgirba.com > www.feenk.com > > "What is more important: To be happy, or to make happy?" > >

Aug. 6, 2017

Jump to page: