- Pharo-dev - lists.pharo.org

Metacello locking system
by Cyril Ferlicot D. March 8, 2018

March 8, 2018

> Cyril, > > For development I tend to use Metacello locking instead of hard-wired > dependencies in the BaselineOf and that works very well --- it > completely avoids the need to edit a baseline for development purposes > and this approach works really well for me ... perhaps we can discuss > this in more detail in a separate thread or even private email? This all > seems to be more complicated for you guys than has been my experience > and of course you guys _appear_ to be completely ignoring the Metacello > locking feature so I'm curious why ... > > Dale > Hi Dale, As asked I start a new thread. I can see some possible reasons I do not use Metacello locking feature. 1) I did not understand well enough what it was 2) We have a way to work different and mine might be incompatible with the lock feature 3) I just did not see how it could help me To know which one is the reason I'll present you a little what I understood of the lock feature and how I usually work and you'll be able to advise me. For the lock feature: If I understood correctly it is a feature allowing to lock a certain version of a project in the Metacello registry. For example if I load Seaside 3.1, lock it and then install a project having Seaside 3.2 as dependency, the lock will block the update of Seaside. Now how do I usually work: Let's take the example of MaterialDesignLite that I maintain. The master branch is a branch that should only contains stable MDL versions. Ideally I would like for each commit of this branch to be tagged with a semantic versionning tag. The development happen in the development branch and new features are merged into this branch before making it to master. In general I prefer to have stricter dependencies in master than in development. So the baseline in the development branch can be different than in master. For all my projects I try to have a Jenkins building Pharo images for at least master and development, and potentially big feature branches before they are merged. The Jenkins also test the images. Then when I need to work on something, I download the Jenkins archive of the corresponding branch, double click on the image (some setting are then loaded) and I'm ready to develop because Jenkins and my settings have done all the setup. I try to keep my Jenkins script as simple as possible for the loading. Ideally I like to have something like this: ./pharo $PROJECT_NAME.image eval --save " Metacello new baseline: #MaterialDesignLite; githubUser: 'DuneSt' project: 'MaterialDesignLite' commitish: '$VERSION' path: 'src'; onWarningLog; load. ". With this way to work, I do not really see how locks can help me. Because I don't want to have to manage possible versions I accept from all the dependencies in **development**. I want to accept the maximum of update and when it breaks either I edit the code to work with the new version of the dependency or I fix the dependency version because it will be too much work. Just to explain why I don't want to manage by hand all the dependencies version in development: I work on a project that at one time had more than 70 dependencies (transitively). Now that you know what I understood of the lock feature and that you know my way to work: Did I miss something on the lock mechanism? Do you think it can help me during my development? If yes, how would you include it in my development workflow? Thank you for the time you spend to help us improve our way to work! -- Cyril Ferlicot https://ferlicot.fr

2 1

[Pharo 7.0-dev] Build #669: 21517-New-traits-copy-all-class-side-methods-of-TraitedClass-to-all-subclasses-of-trait-users
by ci-pharo-ci-jenkins2＠inria.fr March 8, 2018

March 8, 2018

There is a new Pharo build available! The status of the build #669 was: SUCCESS. The Pull Request #1047 was integrated: "21517-New-traits-copy-all-class-side-methods-of-TraitedClass-to-all-subclasses-of-trait-users" Pull request url: https://github.com/pharo-project/pharo/pull/1047 Issue Url: https://pharo.fogbugz.com/f/cases/21517 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

new pharo cheatsheet
by stepharo March 8, 2018

March 8, 2018

new cheatsheet for Pharo syntax. Any feedback is welcome Stef

18 33

[Pharo 7.0-dev] Build #668: 21513-Slots-should-distinguish-between-slot-owner-and-defining-class-
by ci-pharo-ci-jenkins2＠inria.fr March 8, 2018

March 8, 2018

There is a new Pharo build available! The status of the build #668 was: SUCCESS. The Pull Request #1041 was integrated: "21513-Slots-should-distinguish-between-slot-owner-and-defining-class-" Pull request url: https://github.com/pharo-project/pharo/pull/1041 Issue Url: https://pharo.fogbugz.com/f/cases/21513 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #667: 21515 Update bootstrap to bootstrapImage 1.4 and 7.0 VM
by ci-pharo-ci-jenkins2＠inria.fr March 8, 2018

March 8, 2018

There is a new Pharo build available! The status of the build #667 was: SUCCESS. The Pull Request #1043 was integrated: "21515 Update bootstrap to bootstrapImage 1.4 and 7.0 VM" Pull request url: https://github.com/pharo-project/pharo/pull/1043 Issue Url: https://pharo.fogbugz.com/f/cases/21515 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #666: 21512-Remove-Multilingual-support-from-the-bootstrap-image-and-load-it-later
by ci-pharo-ci-jenkins2＠inria.fr March 8, 2018

March 8, 2018

There is a new Pharo build available! The status of the build #666 was: SUCCESS. The Pull Request #1042 was integrated: "21512-Remove-Multilingual-support-from-the-bootstrap-image-and-load-it-later" Pull request url: https://github.com/pharo-project/pharo/pull/1042 Issue Url: https://pharo.fogbugz.com/f/cases/21512 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Pharo6 with Ubuntu and OSSubprocess/threaded heartbeat crashes and problems
by Sabine Manaa March 8, 2018

March 8, 2018

We want to run Pharo6 with Ubuntu 16.04 Linux (in a Docker Image) and use OSSubprocess. For this, we use this vm: https://get.pharo.org/61+vmT [1] tells me: "If you are installing under Linux, then you must use a threaded heartbeat VM" We also created a file /etc/security/limits.d/pharo.conf and put the parameters in like described in the message [2] when startup. Also we log out and in. Question 1: the message (pthread_setschedparam failed: Operation not permitted) comes again to the console each time we use OSSubprocess. As far as I understand, it should disappear. Does this mean, that we did not edit the pharo.conf correctly? Question 2: after several uses of OSSubprocess within our application, Pharo crashes (no PharoDebug.log) with the following messages [3]. How can we avoid this, what are we doing wrong? Question 3: sometimes (!) when we load (exactly the same code loaded with a script), we also get a crash, see [4]. Bug? wrong vm? I am unhappy with this and it takes a lot of time. What are we doing wrong? We want to run Pharo6 with OSSubprocess in Linux within a docker image for our staging environment. Help very welcome :-) Sabine [1]https://github.com/marianopeck/OSSubprocess [2](https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/tag/r3732#lin… [3]crash message *** buffer overflow detected ***: /spf/build/pharo-vm/lib/pharo/5.0-201707201942/pharo terminated ======= Backtrace: ========= /lib/i386-linux-gnu/libc.so.6(+0x67377)[0xf75f3377] /lib/i386-linux-gnu/libc.so.6(__fortify_fail+0x68)[0xf7683708] /lib/i386-linux-gnu/libc.so.6(+0xf58f8)[0xf76818f8] /lib/i386-linux-gnu/libc.so.6(+0xf75fa)[0xf76835fa] /spf/build/pharo-vm/lib/pharo/5.0-201707201942/pharo(aioEnable+0x31)[0x80c9811] /spf/build/pharo-vm/lib/pharo/5.0-201707201942/pharo[0x81215ee] [0xa1010e0] [0xa1c2bb8] [0xa15f50c] ....a lot more [4] PharoDebug.log HERE_BE_DRAGONS_HERE KeyNotFound: key #arg1 not found in Dictionary 5 March 2018 11:31:51.792142 am VM: unix - i686 - linux-gnu - CoInterpreter VMMaker.oscog-eem.2254 uuid: 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017 StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017 VM: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Thu Jul 20 12:42:21 2017 -0700 $ Plugins: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Image: Pharo6.0 [Latest update: #60536] Dictionary>>errorKeyNotFound: Receiver: a Dictionary(#arg3->1 #tmp2->2 ) Arguments and temporary variables: aKey: #arg1 Receiver's instance variables: tally: 2 array: {nil. nil. #arg3->1. #tmp2->2. nil} [ self errorKeyNotFound: key ] in Dictionary>>at: Receiver: a Dictionary(#arg3->1 #tmp2->2 ) Arguments and temporary variables: key: #arg1 Receiver's instance variables: tally: 2 array: {nil. nil. #arg3->1. #tmp2->2. nil} Dictionary>>at:ifAbsent: Receiver: a Dictionary(#arg3->1 #tmp2->2 ) Arguments and temporary variables: arg1: #arg1 arg2: [ self errorKeyNotFound: key ] tmp1: nil Receiver's instance variables: tally: 2 array: {nil. nil. #arg3->1. #tmp2->2. nil} Dictionary>>at: Receiver: a Dictionary(#arg3->1 #tmp2->2 ) Arguments and temporary variables: key: #arg1 Receiver's instance variables: tally: 2 array: {nil. nil. #arg3->1. #tmp2->2. nil} IRPushClosureCopy>>indexForVarNamed: Receiver: pushClosureCopyCopiedValues: #() args: #(#arg3) Arguments and temporary variables: aName: #arg1 Receiver's instance variables: sourceNode: RBBlockNode([ :arg3 | | tmp2 | tmp2 := arg3. tmp2 nextPutAll: arg...etc... bytecodeIndex: nil sequence: an IRSequence (1) destination: an IRSequence (3) successor: nil numArgs: nil blockSequence: an IRSequence (2) tempMap: a Dictionary(#arg3->1 #tmp2->2 ) copiedValues: #() lastBlockSequence: an IRSequence (2) arguments: #(#arg3) IRTranslatorV2>>visitPushTemp: Receiver: an IRTranslatorV2 Arguments and temporary variables: tmp: pushTemp: #arg1 Receiver's instance variables: gen: an IRBytecodeGenerator currentScope: a Stack(pushClosureCopyCopiedValues: #() args: #(#arg3) an IRMeth...etc... trailer: a CompiledMethodTrailer tempVectorStack: a Stack() compilationContext: a CompilationContext IRPushTemp>>accept: Receiver: pushTemp: #arg1 Arguments and temporary variables: aVisitor: an IRTranslatorV2 Receiver's instance variables: sourceNode: RBArgumentNode(arg1) bytecodeIndex: nil sequence: an IRSequence (2) name: #arg1 IRTranslatorV2(IRVisitor)>>visitNode: Receiver: an IRTranslatorV2 Arguments and temporary variables: elem: pushTemp: #arg1 Receiver's instance variables: gen: an IRBytecodeGenerator currentScope: a Stack(pushClosureCopyCopiedValues: #() args: #(#arg3) an IRMeth...etc... trailer: a CompiledMethodTrailer tempVectorStack: a Stack() compilationContext: a CompilationContext IRTranslatorV2>>visitInstruction: Receiver: an IRTranslatorV2 Arguments and temporary variables: instr: pushTemp: #arg1 Receiver's instance variables: gen: an IRBytecodeGenerator currentScope: a Stack(pushClosureCopyCopiedValues: #() args: #(#arg3) an IRMeth...etc... trailer: a CompiledMethodTrailer tempVectorStack: a Stack() compilationContext: a CompilationContext [ :arg2 | self visitInstruction: arg2 ] in IRTranslatorV2(IRVisitor)>>visitSequence: Receiver: an IRTranslatorV2 Arguments and temporary variables: arg1: an IRSequence (2) arg2: pushTemp: #arg1 Receiver's instance variables: gen: an IRBytecodeGenerator currentScope: a Stack(pushClosureCopyCopiedValues: #() args: #(#arg3) an IRMeth...etc... trailer: a CompiledMethodTrailer tempVectorStack: a Stack() compilationContext: a CompilationContext OrderedCollection>>do: Receiver: an OrderedCollection(pushTemp: #arg3 popIntoTemp: #tmp2 pushTemp: #tmp2 pushDup pushTemp: ...etc... Arguments and temporary variables: <<error during printing> Receiver's instance variables: array: an Array(pushTemp: #arg3 popIntoTemp: #tmp2 pushTemp: #tmp2 pushDup push...etc... firstIndex: 1 lastIndex: 25 IRSequence>>do: Receiver: an IRSequence (2) Arguments and temporary variables: aBlock: [ :arg2 | self visitInstruction: arg2 ] Receiver's instance variables: sequence: an OrderedCollection(pushTemp: #arg3 popIntoTemp: #tmp2 pushTemp: #tm...etc... orderNumber: 2 method: an IRMethod IRTranslatorV2(IRVisitor)>>visitSequence: Receiver: an IRTranslatorV2 Arguments and temporary variables: arg1: an IRSequence (2) Receiver's instance variables: gen: an IRBytecodeGenerator currentScope: a Stack(pushClosureCopyCopiedValues: #() args: #(#arg3) an IRMeth...etc... trailer: a CompiledMethodTrailer tempVectorStack: a Stack() compilationContext: a CompilationContext IRTranslatorV2>>visitSequence: Receiver: an IRTranslatorV2 Arguments and temporary variables: instructionSequence: an IRSequence (2) Receiver's instance variables: gen: an IRBytecodeGenerator currentScope: a Stack(pushClosureCopyCopiedValues: #() args: #(#arg3) an IRMeth...etc... trailer: a CompiledMethodTrailer tempVectorStack: a Stack() compilationContext: a CompilationContext IRSequence>>accept: Receiver: an IRSequence (2) Arguments and temporary variables: aVisitor: an IRTranslatorV2 Receiver's instance variables: sequence: an OrderedCollection(pushTemp: #arg3 popIntoTemp: #tmp2 pushTemp: #tm...etc... orderNumber: 2 method: an IRMethod IRTranslatorV2(IRVisitor)>>visitNode: Receiver: an IRTranslatorV2 Arguments and temporary variables: elem: an IRSequence (2) Receiver's instance variables: gen: an IRBytecodeGenerator currentScope: a Stack(pushClosureCopyCopiedValues: #() args: #(#arg3) an IRMeth...etc... trailer: a CompiledMethodTrailer tempVectorStack: a Stack() compilationContext: a CompilationContext [ :arg2 | self visitNode: arg2 ] in IRTranslatorV2(IRVisitor)>>visitNodes: Receiver: an IRTranslatorV2 Arguments and temporary variables: arg1: a SortedCollection(an IRSequence (1) an IRSequence (2) an IRSequence (3) ...etc... arg2: an IRSequence (2) Receiver's instance variables: gen: an IRBytecodeGenerator currentScope: a Stack(pushClosureCopyCopiedValues: #() args: #(#arg3) an IRMeth...etc... trailer: a CompiledMethodTrailer tempVectorStack: a Stack() compilationContext: a CompilationContext SortedCollection(OrderedCollection)>>do: Receiver: a SortedCollection(an IRSequence (1) an IRSequence (2) an IRSequence (3) an IRSequence (4)...etc... Arguments and temporary variables: <<error during printing> Receiver's instance variables: array: an Array(an IRSequence (1) an IRSequence (2) an IRSequence (3) an IRSequ...etc... firstIndex: 1 lastIndex: 7 sortBlock: [ :arg2 :arg3 | arg2 orderNumber <= arg3 orderNumber ] IRTranslatorV2(IRVisitor)>>visitNodes: Receiver: an IRTranslatorV2 Arguments and temporary variables: arg1: a SortedCollection(an IRSequence (1) an IRSequence (2) an IRSequence (3) ...etc... Receiver's instance variables: gen: an IRBytecodeGenerator currentScope: a Stack(pushClosureCopyCopiedValues: #() args: #(#arg3) an IRMeth...etc... trailer: a CompiledMethodTrailer tempVectorStack: a Stack() compilationContext: a CompilationContext IRTranslatorV2>>visitSequences: Receiver: an IRTranslatorV2 Arguments and temporary variables: arg1: a SortedCollection(an IRSequence (1) an IRSequence (2) an IRSequence (3) ...etc... Receiver's instance variables: gen: an IRBytecodeGenerator currentScope: a Stack(pushClosureCopyCopiedValues: #() args: #(#arg3) an IRMeth...etc... trailer: a CompiledMethodTrailer tempVectorStack: a Stack() compilationContext: a CompilationContext IRTranslatorV2>>visitMethod: Receiver: an IRTranslatorV2 Arguments and temporary variables: anIr: an IRMethod Receiver's instance variables: gen: an IRBytecodeGenerator currentScope: a Stack(pushClosureCopyCopiedValues: #() args: #(#arg3) an IRMeth...etc... trailer: a CompiledMethodTrailer tempVectorStack: a Stack() compilationContext: a CompilationContext IRMethod>>accept: Receiver: an IRMethod Arguments and temporary variables: aVisitor: an IRTranslatorV2 Receiver's instance variables: sourceNode: logError: arg1 inContext: arg2 self logStdErrorDuring: [ :arg3 |...etc... startSequence: an IRSequence (1) numArgs: 2 properties: nil tempMap: a Dictionary(#arg1->1 #arg2->2 ) pragmas: an OrderedCollection() additionalLiterals: an OCLiteralSet(#ifNotNil:) compiledMethod: nil compilationContext: a CompilationContext irPrimitive: primitive 0 -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

6 11

Problems with Epicea on Pharo 7
by Cyril Ferlicot D. March 7, 2018

March 7, 2018

Hi, I have a little problem with Epicea and there is some things I would like to discuss. My problem is that I have a Jenkins job downloading a Pharo 7 image, loading inside a little project via an eval command launching a Metacello script. Then I launch tests. And then I archive the image. When I get this image and try to open it with the --no-default-preferences option, I get a window saying that I lost changes and asking if I want to recover them. The only two commands I launched on Jenkins where: ./pharo Pharo.image eval --save ' Metacello new blabla...' and ./pharo Pharo.image test --junit-xml-output '(bla).*' So here my first problem: I don't see why I would have lost changes. Second problem: I did not include pharo-local/ in the archive. So there is no ombu log next to the image. Even if I had a crash on the Jenkins, I would not expect to get this recovery message since I have no epicea log and cannot recover anything. At most I would just expect an #inform: saying "A crash was detected but cannot be recovered" Third problem: This is the case where I have the --no-default-preferences option. If I don't have this option, the image open, the epicea message open and I can do nothing because my Pharo froze. I cannot close the message. I cannot interrupt (ctrl + .). I can just force close the image and the loading of my settings never ends. If I am right on the problems I'll open bug entries about them. Thank you in advance. -- Cyril Ferlicot https://ferlicot.fr

1 0

[Pharo 7.0-dev] Build #665: 21511-add-baseTrait-on-the-instance-side-of-the-trait-and-deprecate-it
by ci-pharo-ci-jenkins2＠inria.fr March 7, 2018

March 7, 2018

There is a new Pharo build available! The status of the build #665 was: SUCCESS. The Pull Request #1040 was integrated: "21511-add-baseTrait-on-the-instance-side-of-the-trait-and-deprecate-it" Pull request url: https://github.com/pharo-project/pharo/pull/1040 Issue Url: https://pharo.fogbugz.com/f/cases/21511 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

generated webdoc?
by Guillermo Polito March 7, 2018

March 7, 2018

Hi all, I know that we had before the generated webdoc from pharo releases in the file server (files.pharo.org) But I cannot see it anymore. Do we still have it hosted somewhere? We were planning to use it as online material for a course. I know that it is mostly not needed, but newby students need somehow to bootstrap themselves :). Thanks, Guille -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 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

1 0