February 2018 - Pharo-dev - lists.pharo.org

NeoCSV nil-Handling

by Sean P. DeNigris

I'd like a hook to specify default values more dynamically. The use case is that I created a glue layer between Magritte and NeoCSV so one can meta-describe how to extract CSV fields into objects. For example: ``` descriptionDate <magritteDescription> ^ MADateDescription new accessor: #date; priority: 400; propertyAt: #csvFieldName put: 'Date'; propertyAt: #csvReader put: [ :s | (s, '/2017') asDate ]; default: Date today; yourself ``` The problem is that there doesn't seem to be a way to plug #default: above into NeoCSV because other hooks like #addField:converter: seem to be skipped for nil values, shortcutting to a statically described per-csv-file emptyFieldValue. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Feb. 13, 2018

Re: [Pharo-dev] Iceberg 0.6.8 backported to 6.1

by Sean P. DeNigris

EstebanLM wrote > I backported iceberg 0.6.8 to Pharo 6.1, so now it is in sync with the > version on Pharo 7.0 Sweet! I think I should now be able to get all my CI back up and running on GitLab :) ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Feb. 13, 2018

Re: [Pharo-dev] Iceberg 0.6.8 backported to 6.1

by Julien

Nice, thank you! Julien --- Julien Delplanque Doctorant Ã lâUniversitÃ© de Lille 1 http://juliendelplanque.be/phd.html Equipe Rmod, Inria BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40 > Le 13 fÃ©vr. 2018 Ã 13:33, Esteban Lorenzano <estebanlm(a)gmail.com> a Ã©crit : > > Hi, > > I backported iceberg 0.6.8 to Pharo 6.1, so now it is in sync with the version on Pharo 7.0 > > Esteban

Feb. 13, 2018

[Pharo 7.0-dev] Build #542: 21332-Jobs-from-the-same-PR-should-not-run-in-parallel

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #542 was: FAILURE. The Pull Request #875 was integrated: "21332-Jobs-from-the-same-PR-should-not-run-in-parallel" Pull request url: https://github.com/pharo-project/pharo/pull/875 Issue Url: https://pharo.fogbugz.com/f/cases/21332 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 13, 2018

Iceberg 0.6.8 backported to 6.1

by Esteban Lorenzano

Hi, I backported iceberg 0.6.8 to Pharo 6.1, so now it is in sync with the version on Pharo 7.0 Esteban

Feb. 13, 2018

[ANN] 15/2: Pharo TechTalk: Contributing to Pharo 7

by Marcus Denker

Pharo TechTalk: Contributing to Pharo 7 When? 15 Feb 2018 5:00 PM - 7:00 PM (UTC+01:00) What? Contributing to Pharo7 We will show: - How to submit issue tracker entries to the Pharo Issue Tracker - How to do a Pull Request if you want to do a fix or enhancment - How to review and comment other peoples fixes. https://association.pharo.org/event-2797065

Feb. 13, 2018

[Pharo 7.0-dev] Build #541: 21308 Remove unnecessary "self run:" in ArrayTest

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #541 was: SUCCESS. The Pull Request #848 was integrated: "21308 Remove unnecessary "self run:" in ArrayTest" Pull request url: https://github.com/pharo-project/pharo/pull/848 Issue Url: https://pharo.fogbugz.com/f/cases/21308 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 13, 2018

[Pharo 7.0-dev] Build #540: 21303 Remove unnecessary "self run:" in TestValueWithinFix

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #540 was: SUCCESS. The Pull Request #853 was integrated: "21303 Remove unnecessary "self run:" in TestValueWithinFix" Pull request url: https://github.com/pharo-project/pharo/pull/853 Issue Url: https://pharo.fogbugz.com/f/cases/21303 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 13, 2018

Re: [Pharo-dev] Cleaning up... baseClass, instanceSide, theNonMetaclass

by Stephane Ducasse

xkcd so to the point. So we will kill two and keep one. On Mon, Feb 12, 2018 at 12:12 PM, Ben Coman <btc(a)openinworld.com> wrote: > I found it quite insightful when I read someone describe that the way > Smalltalk uses Classes is essentially the Factory Pattern. > That makes me wonder whether classClass and classSide of a class might > confuse newcomers > and maybe factorySide of a class would make more sense. > > The again... > https://xkcd.com/927/ > > cheers -ben > > > On 12 February 2018 at 16:45, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > >> In my code I use to use instanceSide and classSide. don't know why. >> Maybe they are clearer to me? >> >> On Sun, Feb 11, 2018 at 8:59 PM, Denis Kudriashov <dionisiydk(a)gmail.com> >> wrote: >> >>> 2018-02-11 18:14 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >>> >>>> Hi >>>> >>>> We already got this discussion and I plan to address it. >>>> Now I discovered that in addition to instanceSide and theNonMetaclass >>>> we have >>>> >>>> - classClass and baseClass >>>> - theMetaclass and theNonMetaclass >>>> - instanceSide and classSide >>>> >>>> https://pharo.fogbugz.com/f/cases/20941/deprecate-theMetacla >>>> ss-and-the-theNonMeta >>>> >>>> Even if instanceSide and classSide come from UI concerns I think that >>>> there are much >>>> better than the others. >>>> >>> >>> + 100 >>> >>> >>>> >>>> So have you any concerns and prefer one of the other couples? Because >>>> we should stop >>>> accumulate cruft in the system. We do not need three ways to do the >>>> same. >>>> >>>> Stef >>>> >>>> >>> >> >> >> -- >> >> >> >> 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 <+33%206%2052%2070%2066%2013> >> > >

Feb. 13, 2018

Re: [Pharo-dev] [Vm-dev] Random corrupted data when copying from very large byte array

by Cyrille Delaunay

Hi everyone, With last answers from Eliot and Alistair, I understand that using a ""GCC 5 VM" may solve the issue. Am I right ? I am willing to give a try on mac os and check if the issue show up with such a vm. But where can I download such a vm ? 2018-01-23 9:24 GMT+01:00 Alistair Grant <akgrant0710(a)gmail.com>: > Hi Eliot, > > On 23 January 2018 at 01:47, Eliot Miranda <eliot.miranda(a)gmail.com> > wrote: > > > > Hi Alistair, > > > > On Mon, Jan 22, 2018 at 1:42 AM, Alistair Grant <akgrant0710(a)gmail.com> > wrote: > >> > >> > >> Hi Eliot, > >> > >> On Sat, Jan 20, 2018 at 09:19:04AM +0100, Alistair Grant wrote: > >> > Hi Eliot, > >> > > >> > On 19 January 2018 at 23:04, Eliot Miranda <eliot.miranda(a)gmail.com> > wrote: > >> > > Hi Alistair, Hi Cl??ment, > >> > > > >> > > On Fri, Jan 19, 2018 at 12:53 PM, Alistair Grant < > akgrant0710(a)gmail.com> > >> > > wrote: > >> > >> > >> > >> Hi Cl??ment, > >> > >> > >> > >> On 19 January 2018 at 17:21, Alistair Grant <akgrant0710(a)gmail.com> > wrote: > >> > >> > Hi Cl??ment, > >> > >> > > >> > >> > On 19 January 2018 at 17:04, Cl??ment Bera < > bera.clement(a)gmail.com> > >> > >> > wrote: > >> > >> >> Does not seem to be related to prim 105. > >> > >> >> > >> > > > >> > > > >> > > I suspect that the problem is the same compactor bug I've been > trying to > >> > > reproduce all week, and have just fixed. Could you try and > reproduce with a > >> > > VM built from the latest commit? > >> > > >> > Happy to, but I'm out all day today, so it will be tomorrow or Monday. > >> > > >> > Cheers, > >> > Alistair > >> > (on the run...) > >> > >> > >> I've tested this with 2 images and 3 VMs in all 6 > >> combinations: > >> > >> - "Old VM": commit date: Wed Jan 10 23:39:30 2018 -0800, gcc 4.8.5 > >> - "New VM": commit date: Sat Jan 20 13:52:26 2018 +0100, gcc 4.8.5 > >> - "GCC 5 VM": commit date: Sat Jan 20 13:52:26 2018 +0100, gcc 5.4.0 > >> - Clean image: commit id: b28d466f > >> - Work image: commit id: eb0a6fb1 > >> > >> The gcc 5 is only there because I was playing with it. The results may > >> be useful, or completely misleading. :-) > >> > >> Each time I ran "5 timesRepeat: [ self test4 ]" > >> with the halts replaced with a count increment. > >> test4 is the method provided in Cyrille's original message. > >> > >> Result summary: > >> > >> - Old VM + Work image: 5, 5, 5, 0, 0 > >> - Old VM + Clean image: 5, 5, 0, 0, 0 > >> - New VM + Work image: 5, 0, 5, 5, 5 > >> - New VM + Clean image: 0, 0, 1, 5, 5 > >> - GCC 5 + Work image: 0, 0, 0, 0, 0 > >> - GCC 5 + Clean image: 0, 0, 0, 0, 0 > > > > > > This is strong evidence for the issue being a compiler bug with 4.8.x > > If exactly the same input source for the Vm wrks with gcc 5 but not with > 4.8.x then there is a small chance it is due to the Vm relying on undefined > behavior, but I doubt it. > > Assuming it is a gcc bug then > > - it should be documented in the HowToBuild files for the relevant > platforms > > - Ci builds should start using gcc 5 and dispense with gcc 4.8.x > > - since the problem is fixed with gcc 5 there seems little point trying > to identify which version of gcc introduces the problem and communicating > the problem to the gcc maintainers > > > > What's the status of the bug on Windows and Mac OS X? > > > I can't check MacOS. Clement? > > I get the problem on Windows (version info below). > > Note that Max Leske and I have been using gcc 4.8 because of a problem > with OSProcess and gcc 5 (it possibly doesn't affect me anymore, I'm > currently using OSSubprocess). See: > > http://lists.squeakfoundation.org/pipermail/vm-dev/2017-May/025216.html > > I'll try and confirm correct OSSubprocess operation with gcc 5, but it > will take a while, I'm battling too many different problems at the > moment: > > - TZ and DST handling on Windows > - Windows VM suddenly can't find any of its plugins. Is anyone else > seeing strange behaviour here with VMs from the last few days? > -- It looks like the plugin handling mechanism is completely different > on Windows to Unix, so the VM doesn't report where it is looking and > doesn't provide the option to specify the directory. Grrrrrgh. > - My linux build environment. > - real life :-) > > > Windows version info: > > OS: Windows 10 > Image: Pharo 7.0 Build information: > Pharo-7.0+alpha.build.439.sha.481071068244d0484241924f79ba791f80701316 > (32 Bit) > VM: > Win32 built on Nov 27 2017 00:05:44 GMT Compiler: 6.4.0 [Production Spur > VM] > CoInterpreter VMMaker.oscog- nice.2281 uuid: > 4beeaee7-567e-1a4b-b0fb-bd95ce302516 Nov 27 2017 > StackToRegisterMappingCogit VMMaker.oscog-nice.2283 uuid: > 2d20324d-a2ab-48d6-b0f6-9fc3d66899da Nov 27 2017 > VM: 201711262336 https://github.com/OpenSmalltalk/opensmalltalk-vm.git > $ Date: Mon Nov 27 00:36:29 2017 +0100 $ > Plugins: 201711262336 https://github.com/OpenSmalltalk/opensmalltalk- > vm.git $ > > > > > Cheers, > Alistair > > -- Cyrille Delaunay

Feb. 13, 2018