- Pharo-dev - lists.pharo.org

Having green builds
by Guillermo Polito Aug. 9, 2017

Aug. 9, 2017

Hi all, As you all know, we are now building from github. Integrations are made through pull requests. And pull requests are validated using jenkins (that is back again, Yay!). In this scenario, pull requests validations in github differentiate only between three states: Pased (green) and not passed (red). This of course conflicts with the three-state jobs of jenkins. By default jenkins transforms failing tests (yellow) to a red state. This means that we lose the extra information provided by the intermediate state. Now, because of this, in order to really differentiate good builds from bad builds, we need to have green builds :). Always. Yesterday we worked with Pablo on that and now we have a PR that fixes all tests and is green :) https://github.com/pharo-project/pharo/pull/184 You can follow up all the things we did in the issue also: https://pharo.fogbugz.com/f/cases/20288/Fix-failing-tests-in-pharo-70 As a summary, we could fix most tests by just touching some code here and there. Some of them were portability issues, some other encoding in the build slaves and so on. The only one we could not fix was a problem cause by a side effect of QualityAssistant-Tests, so we skipped it. Those two tests should be rewritten to not have side effects on other tests (In this case, Epicea). Enjoy, Guille and Pablo -- 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

6 6

fixing the tab morph
by Esteban Lorenzano Aug. 8, 2017

Aug. 8, 2017

Hi, Soâ¦ summer project (to do when there is too much hot to go outside): fix some minor things that are inside the image that annoys me since some time. First issue: the tab morph we have is horrible (and makes horrible anything with it). Iâve been working on it to fix that âchromish-but-badâ style we had and to fix some (a lot) hardcoded colors there. Now, for example, Calypso looks like this: which is IMHO a lot better :) some remarks: 1) I find TabManagerMorph an ugly name. Do you think we should change it? (I tend to think anything called *Manager, *Controller, etc. as a bad naming chose and probably the mark of a smell). 2) much more important: we should deprecate TabGroupMorph and LazyTabGroupMorph familyâ¦ there should not be more than one widget to do the same in the system. So well, as usual with old things: you fix a little thing and you uncover a lot of new problems :) Esteban

6 8

Two tables that share the same data source!?
by Elhamer Aug. 7, 2017

Aug. 7, 2017

Hello everybody, How common is it for multiple tables (FastTables) to have the same datasource ? The FTDataSource has a instance variable to refer a table: ```` Object subclass: #FTDataSource instanceVariableNames: 'table' classVariableNames: '' package: 'Morphic-Widgets-FastTable-DataSource' ``` which makes it impossible for several tables to have the same data source. the code of the data source is also coupled to the ft code which also makes it harder to extend. I've tried to go down the rabbit hole and decouple the data source from the table but things went messy. So i would like to know how common it is for several tables to share the same ds, and does that worth going the extra mile ? Thanks, Elhamer. -- View this message in context: http://forum.world.st/Two-tables-that-share-the-same-data-source-tp4959153.… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

1 0

Segmentation fault Pharo 6.1 64bit vm - Ubuntu Linux - loading Metacello dependency
by Tim Mackinnon Aug. 7, 2017

Aug. 7, 2017

Hi - I just got a seg fault on my Gitlab CI server when trying to load a metacello baseline via the st command line hander. $ ./pharo Pharo.image --no-default-preferences --save --quit st loadLocal.st config.st "{'$AWS_ACCESS_KEY_ID'. '$AWS_SECRET_ACCESS_KEY'. '$AWS_DEFAULT_REGION'. '$S3_BUCKET'}" |& tee LoadLocal.log Fetched -> BaselineOfLambda-cypress.1 --- filetree:///builds/macta/PharoLambda/src [:] --- filetree:///builds/macta/PharoLambda/src Loaded -> BaselineOfLambda-cypress.1 --- filetree:///builds/macta/PharoLambda/src [:] --- filetree:///builds/macta/PharoLambda/src Loading baseline of BaselineOfLambda... Fetched -> BaselineOfAWS-ShoYoshida.12 --- github://newapplesho/aws-sdk-smalltalk:v1.10/pharo-repository [9149805:v1.10] --- github://newapplesho/aws-sdk-smalltalk:v1.10/pharo-repository Loaded -> BaselineOfAWS-ShoYoshida.12 --- github://newapplesho/aws-sdk-smalltalk:v1.10/pharo-repository [9149805:v1.10] --- github://newapplesho/aws-sdk-smalltalk:v1.10/pharo-repository Fetched -> ConfigurationOfZTimestamp-SvenVanCaekenberghe.25 --- http://mc.stfx.eu/Neo --- http://mc.stfx.eu/Neo Loaded -> ConfigurationOfZTimestamp-SvenVanCaekenberghe.25 --- http://mc.stfx.eu/Neo --- http://mc.stfx.eu/Neo Project: ZTimestamp stable [20] Fetched -> ZTimestamp-SvenVanCaekenberghe.57 --- http://mc.stfx.eu/Neo --- http://mc.stfx.eu/Neo Project: AWS baseline Segmentation fault Mon Jul 31 22:18:27 2017 /builds/macta/PharoLambda/build/pharo-vm/lib/pharo/5.0-201707201942/pharo Pharo VM version: 5.0-201707201942 Thu Jul 20 20:42:13 UTC 2017 gcc 4.6.3 [Production Spur 64-bit ITHB VM] Built from: CoInterpreter VMMaker.oscog-eem.2254 uuid: 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017 With: StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017 Revision: 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 $ Build host: Linux testing-gce-2c303f4c-2b90-4f17-b8b9-ec690d977073 3.13.0-115-generic #162~precise1-Ubuntu SMP Fri Mar 24 16:47:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux plugin path: /builds/macta/PharoLambda/build/pharo-vm/lib/pharo/5.0-201707201942 [default: /builds/macta/PharoLambda/build/pharo-vm/lib/pharo/5.0-201707201942/] C stack backtrace & registers: rax 0xa41278c0 rbx 0xa4127750 rcx 0xa4127978 rdx 0xa4127808 rdi 0xa4127528 rsi 0xa4127528 rbp 0xa4127698 rsp 0xa4127a30 r8 0xa4126f68 r9 0xa4127020 r10 0xa41270d8 r11 0xa4127190 r12 0xa4127248 r13 0xa4127300 r14 0xa41273b8 r15 0xa4127470 rip 0xa4127ae8 *[0x7fffa4127ae8] /builds/macta/PharoLambda/build/pharo-vm/lib/pharo/5.0-201707201942/pharo[0x41cd91] /builds/macta/PharoLambda/build/pharo-vm/lib/pharo/5.0-201707201942/pharo[0x41d11f] /lib/x86_64-linux-gnu/libpthread.so.0(+0x11670)[0x7efe11ad9670] /builds/macta/PharoLambda/build/pharo-vm/lib/pharo/5.0-201707201942/pharo[0x43645f] /builds/macta/PharoLambda/build/pharo-vm/lib/pharo/5.0-201707201942/pharo(ceBaseFrameReturn+0xc1)[0x45bec1] [0x260124e] [0x0] Smalltalk stack dump: Most recent primitives stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: stringHash:initialHash: stringHash:initialHash: basicAtLeast: basicAtLeast: new: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: compare:with:collated: compare:with:collated: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: compare:with:collated: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: compare:with:collated: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: compare:with:collated: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: compare:with:collated: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: compare:with:collated: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: compare:with:collated: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stack page bytes 8192 available headroom 5576 minimum unused headroom 5976 The script being run was - and it segâd on the first Metacello invocation when reading in a dependent spec. "CmdLine script to load project" | stdout | stdout := FileStream stdout wantsLineEndConversion: true; converter; yourself. "Add missing STON dependency in minimal image" Smalltalk at: #STON ifAbsent: [ stdout nextPutAll: 'Loading missing STON'; cr. Gofer new url: 'http://ss3.gemstone.com/ss/STON'; package: 'STON-Core'; load. "Fix-up issue with Undeclared not firing a change in minimal image" { MCFileTreeRepository. MCFileTreeStCypressReader. MCFileTreeAbstractReader } do: [:c | c compileAll ] ]. "Create a stub TestCase (if needed) for packages not minimally defined" Smalltalk at: #TestCase ifAbsent: [ stdout nextPutAll: 'Creating missing TestCase'; cr. Object subclass: #TestCase ]. Metacello new repository: 'filetree://../src'; baseline: 'Lambda'; load. Metacello new repository: 'filetree://../src'; baseline: 'LambdaRuntime'; load. Smalltalk at: #IceRepositoriesBrowser ifPresent: [ :i | stdout nextPutAll: 'Removing rogue ', i name; cr. i allInstances do: [:b | b become: String new ]]. Smalltalk at: #OmSessionStore ifPresent: [ :i | stdout nextPutAll: 'Unregistering ', i name; cr. SessionManager default unregisterClassNamed: i name ]. SmalltalkImage current garbageCollect.

2 2

Re: [Pharo-dev] Creating the smallest server runtime footprint
by Pavel Krivanek Aug. 7, 2017

Aug. 7, 2017

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-32bit-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

4 38

About cr and lf
by Stephane Ducasse Aug. 6, 2017

Aug. 6, 2017

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? Stef

17 39

Re: [Pharo-dev] PharoLauncher - uninformative Pharo7 template names
by Torsten Bergmann Aug. 6, 2017

Aug. 6, 2017

1 0

[Calypso] Inherited methods checkbox look backwards to me
by Mariano Martinez Peck Aug. 4, 2017

Aug. 4, 2017

Hi Denis, I love the inherited methods feature. Really. Seconds ago, I just clicked to show inherited methods, I checkboxed the superclass, then I saw both methods (the one I override and the one of the superclass), clicked on both, and magic...I was comparing them with a nice diff. AESOME!!!!! The only seem that didn't look obvious to me is the "sort" of the classes of the inherited protocols. It goes contrary to everwhere else. ProtoObject is on the bottom and immediate superclass on the top. Can't we make it as always? ProtoObject on the bottom and immediate on top? I know, this is a very little detail...but I also wanted to express my happiness with this feature hahaha. Cheers, -- Mariano http://marianopeck.wordpress.com

4 5

Re: [Pharo-dev] [vwnc] Live Programming in Smalltalk development environments survey + raffle
by Juraj Kubelka Aug. 3, 2017

Aug. 3, 2017

Hi Helge, we are targeting it to ICSE 2018. With crossed fingers it will happen :-) Cheers, Juraj > El 03-08-2017, a las 10:30, Nowak, Helge <HNowak(a)cincom.com> escribiÃ³: > > Dear Juraj, Romain and Alexandre, <> > > this is indeed an interesting piece of research! Where will you publish the results with detailed analysis? > > Cheers > Helge > > Helge Nowak > Cincom Smalltalk Technical Account Manager EMEA > <image001.png> <http://www.cincomsmalltalk.com/> > Cincom Systems GmbH & Co. oHG > Am Kronberger Hang 4 > 65824 Schwalbach/Ts. > GERMANY > office > mobile > fax > > website > email > +49 89 89 66 44 94 > +49 172 74 00 402 > +49 89 89 66 44 95 > > http://www.cincomsmalltalk.com <http://www.cincomsmalltalk.com/> > hnowak(a)cincom.com <mailto:hnowak@cincom.com> > A standpoint is an intellectual horizon of radius zero. -- Albert Einstein > > GeschÃ¤ftsfÃ¼hrer/Managing Directors: Thomas M. Nies, Donald E. Vick > oHG mit Sitz/based in Schwalbach/Ts. (Amtsgericht KÃ¶nigstein/Ts. HRA 2653) > Pers. haftender Gesellschafter/Partner liable to unlimited extent: > Cincom Systems Verwaltungsgesellschaft mbH (Amtsgericht KÃ¶nigstein/Ts. HRB 5069) > > --- CONFIDENTIALITY STATEMENT --- > This e-mail transmission contains information that is intended to be privileged and confidential. It is intended only for the addressee named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited, please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. > > > Von: Juraj Kubelka [mailto:juraj.kubelka@icloud.com] > Gesendet: Donnerstag, 3. August 2017 09:31 > An: Any question about pharo is welcome <pharo-users(a)lists.pharo.org>; Pharo Development List <pharo-dev(a)lists.pharo.org>; Squeak Virtual Machine Development Discussion <vm-dev(a)lists.squeakfoundation.org>; squeak-dev(a)lists.squeakfoundation.org; vwnc(a)lists.cs.illinois.edu > Betreff: [vwnc] Live Programming in Smalltalk development environments survey + raffle > > â âWe are apologize for multiple copies.â â > > Dear Smalltalker, > > Live programming frees developers from the "edit-compile-run" loop and allows people to interact with running programs very easily. Live programming is getting popular, but many of its features have > been present in Smalltalk for a very long time. > > We want to understand how Smalltalk software developers use live programming features in practice. We would be grateful if you could participate in our 10-minute survey on this subject: > http://bit.ly/2ufcg2D <http://bit.ly/2ufcg2D> > > As a thank you for your participation, you will be able to participate in a raffle to win a Smalltalk book of your choice. If you wish to participate, you will need to share your email with us, so > that we can contact you. > We will appreciate if you share the survey > - Twitter post: https://twitter.com/JurajKubelka/status/893006267085709312 <https://twitter.com/JurajKubelka/status/893006267085709312> > - Facebook post: https://www.facebook.com/juraj.kubelka/posts/10212505941300008 <https://www.facebook.com/juraj.kubelka/posts/10212505941300008> > > By participating in the survey you will: > - help me to successfully finish my PhD, > - push Smalltalk awareness in Live Programming research community, > - bring new integrated electronic communication ideas, and > - bring new ideas to improve our Smalltalk Live Programming experience :-) > > We will close the survey on Wednesday, August 9, 2017 AoE. > > Thank you and we really hope you enjoy participating in our survey! > > Juraj Kubelka, PhD Student at the University of Chile > > Romain Robbes, Professor at Free University of Bozen-Bolzano > > Alexandre Bergel, Professor at the University of Chile

1 0

Live Programming in Smalltalk development environments survey + raffle
by Juraj Kubelka Aug. 3, 2017

Aug. 3, 2017

â âWe are apologize for multiple copies.â â Dear Smalltalker, Live programming frees developers from the "edit-compile-run" loop and allows people to interact with running programs very easily. Live programming is getting popular, but many of its features have been present in Smalltalk for a very long time. We want to understand how Smalltalk software developers use live programming features in practice. We would be grateful if you could participate in our 10-minute survey on this subject: http://bit.ly/2ufcg2D <http://bit.ly/2ufcg2D> As a thank you for your participation, you will be able to participate in a raffle to win a Smalltalk book of your choice. If you wish to participate, you will need to share your email with us, so that we can contact you. We will appreciate if you share the survey - Twitter post: https://twitter.com/JurajKubelka/status/893006267085709312 <https://twitter.com/JurajKubelka/status/893006267085709312> - Facebook post: https://www.facebook.com/juraj.kubelka/posts/10212505941300008 <https://www.facebook.com/juraj.kubelka/posts/10212505941300008> By participating in the survey you will: - help me to successfully finish my PhD, - push Smalltalk awareness in Live Programming research community, - bring new integrated electronic communication ideas, and - bring new ideas to improve our Smalltalk Live Programming experience :-) We will close the survey on Wednesday, August 9, 2017 AoE. Thank you and we really hope you enjoy participating in our survey! Juraj Kubelka, PhD Student at the University of Chile Romain Robbes, Professor at Free University of Bozen-Bolzano Alexandre Bergel, Professor at the University of Chile

1 0