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

Re: [Pharo-dev] [Pharo 7.0-dev] Build #580: 21350 Enhance LibC with piping and the platform with running commands

by Marcus Denker

> On 20 Feb 2018, at 13:31, ci-pharo-ci-jenkins2(a)inria.fr wrote: > > There is a new Pharo build available! > > The status of the build #580 was: FAILURE. > > The Pull Request #893 was integrated: "21350 Enhance LibC with piping and the platform with running commands" > Pull request url: https://github.com/pharo-project/pharo/pull/893 > > Issue Url: https://pharo.fogbugz.com/f/cases/21350 > Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… [kernel-unix-32] Downloading the latest pharoVM: [kernel-unix-32] http://files.pharo.org/get-files/70/pharo-linux-stable.zip <http://files.pharo.org/get-files/70/pharo-linux-stable.zip> [kernel-unix-32] mkdir: cannot create directory âpharo-vmâ: File exists

Feb. 20, 2018

[Pharo 7.0-dev] Build #580: 21350 Enhance LibC with piping and the platform with running commands

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

There is a new Pharo build available! The status of the build #580 was: FAILURE. The Pull Request #893 was integrated: "21350 Enhance LibC with piping and the platform with running commands" Pull request url: https://github.com/pharo-project/pharo/pull/893 Issue Url: https://pharo.fogbugz.com/f/cases/21350 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 20, 2018

[Pharo 7.0-dev] Build #579: 21263-WorldState--displayWorldsubmorphs--canvas--finish---canvas-can-be-nil-at-startup-of-the-image

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

There is a new Pharo build available! The status of the build #579 was: FAILURE. The Pull Request #817 was integrated: "21263-WorldState--displayWorldsubmorphs--canvas--finish---canvas-can-be-nil-at-startup-of-the-image" Pull request url: https://github.com/pharo-project/pharo/pull/817 Issue Url: https://pharo.fogbugz.com/f/cases/21263 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 20, 2018

Re: [Pharo-dev] Latest Pharo 70 linux VM is itimer?

by Alistair Grant

On 20 February 2018 at 11:01, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > fixed Thanks! Alistair >> On 20 Feb 2018, at 10:59, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> yes, there is an error. >> it should be the threaded version. >> >> Esteban >> >>> On 20 Feb 2018, at 10:42, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>> >>> Hi Everyone, >>> >>> Downloading the latest 7.0 linux VM with: >>> >>> curl get.pharo.org/vmLatest70 | bash >>> >>> on linux gives a itimer VM: >>> >>> $ ./pharo --version >>> 5.0-201802171019 Sat Feb 17 10:27:09 UTC 2018 gcc 4.8.4 [Production >>> Spur ITHB VM] >>> CoInterpreter VMMaker.oscog-eem.2320 uuid: >>> e2692e35-5fc8-4623-95d0-b445b3329f75 Feb 17 2018 >>> StackToRegisterMappingCogit VMMaker.oscog-eem.2324 uuid: >>> 904abc56-e5a8-467e-a337-880211e33805 Feb 17 2018 >>> VM: 201802171019 https://github.com/OpenSmalltalk/opensmalltalk-vm.git >>> $ Date: Sat Feb 17 11:19:01 2018 +0100 $ >>> Plugins: 201802171019 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ >>> Linux travis-job-cc93cae9-4623-4046-bc51-1d5e0f1daa41 >>> 4.4.0-101-generic #124~14.04.1-Ubuntu SMP Fri Nov 10 19:05:36 UTC 2017 >>> i686 i686 i686 GNU/Linux >>> plugin path: /tmp/p7vm/pharo-vm/lib/pharo/5.0-201802171019 [default: >>> /tmp/p7vm/pharo-vm/lib/pharo/5.0-201802171019/] >>> >>> >>> >>> My understanding is that this should be threaded heartbeat. >>> >>> Can someone clarify what's happening? >>> >>> Thanks! >>> Alistair >>> >> > >

Feb. 20, 2018

Re: [Pharo-dev] Latest Pharo 70 linux VM is itimer?

by Esteban Lorenzano

fixed > On 20 Feb 2018, at 10:59, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > yes, there is an error. > it should be the threaded version. > > Esteban > >> On 20 Feb 2018, at 10:42, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> >> Hi Everyone, >> >> Downloading the latest 7.0 linux VM with: >> >> curl get.pharo.org/vmLatest70 | bash >> >> on linux gives a itimer VM: >> >> $ ./pharo --version >> 5.0-201802171019 Sat Feb 17 10:27:09 UTC 2018 gcc 4.8.4 [Production >> Spur ITHB VM] >> CoInterpreter VMMaker.oscog-eem.2320 uuid: >> e2692e35-5fc8-4623-95d0-b445b3329f75 Feb 17 2018 >> StackToRegisterMappingCogit VMMaker.oscog-eem.2324 uuid: >> 904abc56-e5a8-467e-a337-880211e33805 Feb 17 2018 >> VM: 201802171019 https://github.com/OpenSmalltalk/opensmalltalk-vm.git >> $ Date: Sat Feb 17 11:19:01 2018 +0100 $ >> Plugins: 201802171019 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ >> Linux travis-job-cc93cae9-4623-4046-bc51-1d5e0f1daa41 >> 4.4.0-101-generic #124~14.04.1-Ubuntu SMP Fri Nov 10 19:05:36 UTC 2017 >> i686 i686 i686 GNU/Linux >> plugin path: /tmp/p7vm/pharo-vm/lib/pharo/5.0-201802171019 [default: >> /tmp/p7vm/pharo-vm/lib/pharo/5.0-201802171019/] >> >> >> >> My understanding is that this should be threaded heartbeat. >> >> Can someone clarify what's happening? >> >> Thanks! >> Alistair >> >

Feb. 20, 2018

Re: [Pharo-dev] Latest Pharo 70 linux VM is itimer?

by Esteban Lorenzano

yes, there is an error. it should be the threaded version. Esteban > On 20 Feb 2018, at 10:42, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Everyone, > > Downloading the latest 7.0 linux VM with: > > curl get.pharo.org/vmLatest70 | bash > > on linux gives a itimer VM: > > $ ./pharo --version > 5.0-201802171019 Sat Feb 17 10:27:09 UTC 2018 gcc 4.8.4 [Production > Spur ITHB VM] > CoInterpreter VMMaker.oscog-eem.2320 uuid: > e2692e35-5fc8-4623-95d0-b445b3329f75 Feb 17 2018 > StackToRegisterMappingCogit VMMaker.oscog-eem.2324 uuid: > 904abc56-e5a8-467e-a337-880211e33805 Feb 17 2018 > VM: 201802171019 https://github.com/OpenSmalltalk/opensmalltalk-vm.git > $ Date: Sat Feb 17 11:19:01 2018 +0100 $ > Plugins: 201802171019 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > Linux travis-job-cc93cae9-4623-4046-bc51-1d5e0f1daa41 > 4.4.0-101-generic #124~14.04.1-Ubuntu SMP Fri Nov 10 19:05:36 UTC 2017 > i686 i686 i686 GNU/Linux > plugin path: /tmp/p7vm/pharo-vm/lib/pharo/5.0-201802171019 [default: > /tmp/p7vm/pharo-vm/lib/pharo/5.0-201802171019/] > > > > My understanding is that this should be threaded heartbeat. > > Can someone clarify what's happening? > > Thanks! > Alistair >

Feb. 20, 2018

Latest Pharo 70 linux VM is itimer?

by Alistair Grant

Hi Everyone, Downloading the latest 7.0 linux VM with: curl get.pharo.org/vmLatest70 | bash on linux gives a itimer VM: $ ./pharo --version 5.0-201802171019 Sat Feb 17 10:27:09 UTC 2018 gcc 4.8.4 [Production Spur ITHB VM] CoInterpreter VMMaker.oscog-eem.2320 uuid: e2692e35-5fc8-4623-95d0-b445b3329f75 Feb 17 2018 StackToRegisterMappingCogit VMMaker.oscog-eem.2324 uuid: 904abc56-e5a8-467e-a337-880211e33805 Feb 17 2018 VM: 201802171019 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Sat Feb 17 11:19:01 2018 +0100 $ Plugins: 201802171019 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Linux travis-job-cc93cae9-4623-4046-bc51-1d5e0f1daa41 4.4.0-101-generic #124~14.04.1-Ubuntu SMP Fri Nov 10 19:05:36 UTC 2017 i686 i686 i686 GNU/Linux plugin path: /tmp/p7vm/pharo-vm/lib/pharo/5.0-201802171019 [default: /tmp/p7vm/pharo-vm/lib/pharo/5.0-201802171019/] My understanding is that this should be threaded heartbeat. Can someone clarify what's happening? Thanks! Alistair

Feb. 20, 2018

[JOB][Research] 3 Year Starting Research Positions

by Marcus Denker

Inria opended a call for starting researchers. This is a three year contract. REQUIREMENTS - Have a French doctorate or an equivalent international degree - From 2 to 8 years of experience in research (after the thesis) - No age or nationality conditions. - Deadline: April 3rd, 2018 Before writing their research program, the applicants are strongly encouraged to contact the teams or project(s)-teams leaders concerned by their applications. More information on the official website: https://www.inria.fr/en/institute/recruitment/offers/starting-research-posi… MISSION Join one of our two lines of research: Tools for Software Maintenance or New Programming Language Constructs for Software Evolution. THE REGION Lille is strategically located in Northern Europe with train connections to Paris (1h), London (1h30) and Brussels (30 min.) The Nord Pas de Calais region is a dynamic area in both industry and research for computer science with companies that are european leaders in their branch. Lille, the capital of northern France is an attractive metropolis of over 1 million inhabitants. Cost of living in Lille is lower than that of very big cities such as Paris and London. THE TEAM RMoD is an Inria research project team. It consists of 5 permant researchers (Inria CR and DR, as well as University Assistant Professors) and Engineers, postdocs and students (Master and PhD). RMoD is an international team with more than 20 members from six countries. LINKS: RMoD: http://rmod.lille.inria.fr INRIA Lille: http://www.inria.fr/lille/ INRIA in General: http://www.inria.fr Lille: http://en.wikipedia.org/wiki/Lille http://wikitravel.org/en/Lille Please contact the head of the research team: Stephane.Ducasse(a)inria.fr or one of the following group members: Nicolas.Anquetil(a)inria.fr, Marcus.Denker(a)inria.fr Permanent Link: https://rmod.inria.fr/web/blog/2018-02-19

Feb. 20, 2018

[ANN] Pharo Sprint Feb 23

by Marcus Denker

Pharo Sprint Feb 23 https://association.pharo.org/event-2789568 For a list of all future Pharo Event, have a look at: https://association.pharo.org/events (you can get iCal entries and subsribe to an event specific mailinglist bu registering) Marcus

Feb. 20, 2018

Re: [Pharo-dev] NeoCSV nil-Handling

by Sven Van Caekenberghe

Sean, > On 19 Feb 2018, at 02:33, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Sven Van Caekenberghe-2 wrote >> What do you think ? > > Could #emptyFieldValue: accept a block instead of the actual value? Or be > per-field? Or both? Then the default could still be set via the current > mechanism, keeping the usual API simple, but the user would have a bit more > control. Have a look at the following: === Name: Neo-CSV-Core-SvenVanCaekenberghe.27 Author: SvenVanCaekenberghe Time: 19 February 2018, 10:28:24.688684 pm UUID: a08d6c1c-f921-0d00-aaa4-29b9044088b7 Ancestors: Neo-CSV-Core-SvenVanCaekenberghe.26 Add special option #passNil for NeoCSVReader>>#emptyFieldValue: so that converter blocks do get nil passed in for empty/missing fields and can act accordingly Add NeoCSVReaderTests>>#testEmptyFieldValuePassNil === Name: Neo-CSV-Tests-SvenVanCaekenberghe.24 Author: SvenVanCaekenberghe Time: 19 February 2018, 10:28:03.52381 pm UUID: 1598291b-f921-0d00-aaa3-c7c0044088b7 Ancestors: Neo-CSV-Tests-SvenVanCaekenberghe.23 Add special option #passNil for NeoCSVReader>>#emptyFieldValue: so that converter blocks do get nil passed in for empty/missing fields and can act accordingly Add NeoCSVReaderTests>>#testEmptyFieldValuePassNil === Now you can do as follows: | date1 date2 | date1 := '1900-01-01' asDate. date2 := '2000-12-31' asDate. self assert: ((NeoCSVReader on: 'date1,date2\2018-01-01,2018-02-01\2018-01-01,\,2018-02-01\\' withCRs readStream) emptyFieldValue: #passNil; addFieldConverter: [ :input | input ifNil: [ date1 ] ifNotNil: [ input asDate ] ]; addFieldConverter: [ :input | input ifNil: [ date2 ] ifNotNil: [ input asDate ] ]; skipHeader; upToEnd) equals: (Array with: (Array with: '2018-01-01' asDate with: '2018-02-01' asDate) with: (Array with: '2018-01-01' asDate with: date2) with: (Array with: date1 with: '2018-02-01' asDate) with: (Array with: date1 with: date2)). Note how the first field's default empty value is now date1 and second field's is date2. Sven

Feb. 19, 2018