Re: [Pharo-dev] [ANN] Fari — a shell tool to fetch & prepare your fresh images

On Fri, Jan 19, 2018 at 7:02 PM, Damien Pollet wrote: > Here it is, tell me what you think: https://github.com/cdlm/fari.sh > > We discussed it with Christophe and of course there is some overlap with > PharoLauncher, and in the future, it might get replaced by a command-line > version of PharoLa

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

Ok so the bug happens in VMMaker 2265 while the change in prim 105 was introduced in 2273, so that's not it (I was surprised, there is lots of tests for this). It seems each time I have the problem, it happens when totalReadCount reach 18186240. I guess that matches some specific array growth stra

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

Hi Alistair, Hi Clément, On Fri, Jan 19, 2018 at 12:53 PM, Alistair Grant wrote: > Hi Clément, > > On 19 January 2018 at 17:21, Alistair Grant wrote: > > Hi Clément, > > > > On 19 January 2018 at 17:04, Clément Bera > wrote: > >> Does not seem to be related to prim 105. > >> > >> I am confused

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

Hi Clément, On 19 January 2018 at 17:21, Alistair Grant wrote: > Hi Clément, > > On 19 January 2018 at 17:04, Clément Bera wrote: >> Does not seem to be related to prim 105. >> >> I am confused. Has the size of the array an impact at all ? > > Yes, I tried reducing the size of the array by a fac

Re: [Pharo-dev] [ANN] Fari — a shell tool to fetch & prepare your fresh images

Le ven. 19 janv. 2018 à 20:59, Hernán Morales Durand < hernan.mora...@gmail.com> a écrit : > $ ./fari.sh > ls: cannot access './*.load.st': No such file or directory > > You may need to add a shell option in the script to include hidden file > names in expansions > > shopt -s dotglob > Ah no, thi

Re: [Pharo-dev] [ANN] Fari — a shell tool to fetch & prepare your fresh images

Hi Damien, Thanks for sharing this. This is what I did using mingw: $ wget https://github.com/cdlm/fari.sh/raw/master/fari.sh $ cat > .load.st Metacello new baseline: 'CCBC'; repository: 'gitlocal://./src'; load. $ ./fari.sh ls: cannot access './*.load.st': No such file or directory You may

[Pharo-dev] [ANN] Fari — a shell tool to fetch & prepare your fresh images

Here it is, tell me what you think: https://github.com/cdlm/fari.sh We discussed it with Christophe and of course there is some overlap with PharoLauncher, and in the future, it might get replaced by a command-line version of PharoLauncher based on Clap. But for the moment it works and fits my tw

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

Hi Clément, On 19 January 2018 at 17:04, Clément Bera wrote: > Does not seem to be related to prim 105. > > I am confused. Has the size of the array an impact at all ? Yes, I tried reducing the size of the array by a factor of 10 and wasn't able to reproduce the problem at all. With the full si

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

Does not seem to be related to prim 105. I am confused. Has the size of the array an impact at all ? It seems the problem shows since the first copy of 16k elements. I can't really reproduce the bug - it happened once but I cannot do it again. Does the bug happen with the StackVM/PharoS VM you ca

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

Luke Gorrie wrote: > For me it's another story. I'm on an unsupported platform (NixOS Linux), > I'm building the VM from random git commits because the source releases are > all antiquated, Iceberg segfaults the moment I start it, and > epica+monticello+metacello+iceberg+fogbugz+jenkins feels lik

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

2018-01-19 8:39 GMT+01:00 Esteban Lorenzano : > hi :) > > On 18 Jan 2018, at 18:39, Stephane Ducasse > wrote: > > Thanks Luke for your feedback > Guillermo and Pablo are working on a new Iceberg model and UI. > > > Model is done, we will integrate it as 0.7 version. > UI… is harder. We could do a

[Pharo-dev] Esteban's ChangeLog week of 8 January 2018

Hello! This is my weekly ChangeLog, from 8 January 2018 to 14 January 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=8/1/2018&to=14/1/2018 ChangeLog = 12 January 2018: *So well... it was the full week trying to compi

Re: [Pharo-dev] Esteban's ChangeLog week of 8 January 2018

Sorry, script was broken. I just spent some time fixing it… now they are back :) Esteban > On 19 Jan 2018, at 13:25, esteba...@gmail.com wrote: > > Hello! > > This is my weekly ChangeLog, from 8 January 2018 to 14 January 2018. > You can see it in a better format by going here: > http://log.s

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

> On 19 Jan 2018, at 13:00, Stephane Ducasse wrote: > > On Fri, Jan 19, 2018 at 8:39 AM, Esteban Lorenzano > wrote: >> hi :) >> >> On 18 Jan 2018, at 18:39, Stephane Ducasse wrote: >> >> Thanks Luke for your feedback >> Guillermo and Pablo are working on a new Ic

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

On Fri, Jan 19, 2018 at 8:39 AM, Esteban Lorenzano wrote: > hi :) > > On 18 Jan 2018, at 18:39, Stephane Ducasse wrote: > > Thanks Luke for your feedback > Guillermo and Pablo are working on a new Iceberg model and UI. > > > Model is done, we will integrate it as 0.7 version. > UI… is harder. We

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

> On 19 Jan 2018, at 10:53, Alistair Grant wrote: > > Hi Luke, > > On 19 January 2018 at 10:39, Luke Gorrie wrote: >> Thanks Esteban. It's a relief to know that eveything is my fault. >> >> Have a nice life... > > I think you're reading this more negatively than intended. > > Esteban's poi

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

Hi Luke, On 19 January 2018 at 10:39, Luke Gorrie wrote: > Thanks Esteban. It's a relief to know that eveything is my fault. > > Have a nice life... I think you're reading this more negatively than intended. Esteban's point was that when he refers to the pharo contribution process he only means

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

Hi Luke, On 19 January 2018 at 10:17, Luke Gorrie wrote: > Hi Esteban, > > I am really happy that everything is working so well for you and I hope that > other people are having a similar experience. > > For me it's another story. I'm on an unsupported platform (NixOS Linux), I'm > building the V

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

Thanks Esteban. It's a relief to know that eveything is my fault. Have a nice life... On 19 January 2018 at 10:28, Esteban Lorenzano wrote: > > > On 19 Jan 2018, at 10:17, Luke Gorrie wrote: > > Hi Esteban, > > I am really happy that everything is working so well for you and I hope > that othe

[Pharo-dev] [JOB][Research] Inria Research CRCN Position

FULL TIME PERMANENT RESEARCH POSITIONS IN LILLE, FRANCE Inria opens on January 15, 2018 nine competitions of normal class researchers. 23 positions will be filled in the 8 research centers of the Institute. The deadline for submitting applications is 19 February 2018 midnight French time. CRCN

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

> On 19 Jan 2018, at 10:17, Luke Gorrie wrote: > > Hi Esteban, > > I am really happy that everything is working so well for you and I hope that > other people are having a similar experience. > > For me it's another story. I'm on an unsupported platform (NixOS Linux), I'm > building the VM

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

Hi Esteban, I am really happy that everything is working so well for you and I hope that other people are having a similar experience. For me it's another story. I'm on an unsupported platform (NixOS Linux), I'm building the VM from random git commits because the source releases are all antiquate

[Pharo-dev] [Pharo 7.0-dev] Build #437: 20992-Use-Stdio-class-instead-of-VTermOutputDriver

There is a new Pharo build available! The status of the build #437 was: SUCCESS. The Pull Request #691 was integrated: "20992-Use-Stdio-class-instead-of-VTermOutputDriver" Pull request url: https://github.com/pharo-project/pharo/pull/691 Issue Url: https://pharo.fogbugz.com/f/cases/2099

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

Is there a summary what and why the model changed? I’m really interested as you know. And I can tell that there are still things very fishy in the whole process. Norbert > Am 19.01.2018 um 08:39 schrieb Esteban Lorenzano : > > hi :) > >> On 18 Jan 2018, at 18:39, Stephane Ducasse >