October 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] State of files.pharo.org

by stephan

On 06-10-17 16:00, Ben Coman wrote: > Without know what actions they may have tries, I'd generally say it seems > that it can't be solved with local testing since that is a different > environment. Ideally your DevOps guys could get on a machine in a remote > corner of the world exhibiting the problem, to help them "see" the > problem. That could be easily and cheaply done by using some of the vps providers that let you work with a machine in a datacenter of your choosing. Anyway, what might help the Inria team is a traceroute from the slow connection Stephan

Oct. 11, 2017

Re: [Pharo-dev] Videos ESUG17 Day1 online

by Tudor Girba

Thanks, Marcus! Doru > On Oct 11, 2017, at 9:50 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > The videos of the first day are online: > > https://www.youtube.com/playlist?list=PLJ5nSnWzQXi_THfKwhzxFwbXy00YTi0uv > > > More coming soon. > > Marcus > > -- www.tudorgirba.com www.feenk.com "We can create beautiful models in a vacuum. But, to get them effective we have to deal with the inconvenience of reality."

Oct. 11, 2017

[Pharo 7.0-dev] Build #177: 14443 unify transcript packages

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

There is a new Pharo build available! The status of the build #177 was: SUCCESS. The Pull Request #340 was integrated: "14443 unify transcript packages" Pull request url: https://github.com/pharo-project/pharo/pull/340 Issue Url: https://pharo.fogbugz.com/f/cases/14443 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 11, 2017

Videos ESUG17 Day1 online

by Marcus Denker

Hi, The videos of the first day are online: https://www.youtube.com/playlist?list=PLJ5nSnWzQXi_THfKwhzxFwbXy00YTi0uv <https://www.youtube.com/playlist?list=PLJ5nSnWzQXi_THfKwhzxFwbXy00YTi0uv> More coming soon. Marcus

Oct. 11, 2017

[TechTalk] 17th Oct: Artificial Intelligence

by Marcus Denker

Pharo TechTalk: Artificial Intelligence ââââââââââââââââââââââââ A regular chat about Pharo. Happens on Discord. Topic: Artificial Intelligence. This is an interactive mini lecture about AI by Alexandre Bergel. 17 Oct 2017 5:00 PM - 7:00 PM (UTC+02:00) This is 17h Paris time. you can download a calendar entry here: https://association.pharo.org/event-2642664

Oct. 11, 2017

Re: [Pharo-dev] XPath chapter...

by monty

Great effort. The guide is concise and beginner friendly. I emailed you a git commit patch you can apply with `git am` (I don't use github) that fixes some things and expands on others. And for the record, I'm not "Monty Kamath" and I don't know him. > Sent: Sunday, September 24, 2017 at 1:03 PM > From: "Stephane Ducasse" <stepharo.self(a)gmail.com> > To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Subject: [Pharo-dev] XPath chapter... > > Hi > > I'm fully convinced that we can have the best language if we do not > let people find their way super easily to do what they want to do we > will fail. > Documentation is KEY and I feel a bit alone. > > Since I always wanted to learn XPath I started to write a chapter on > XPath. I hope that I did not write too many mistakes. > > Pull requests are welcome here > https://github.com/SquareBracketAssociates/Booklet-Scraping > > I would love to have one booklet on SAX and DOM handling. > > > Stef >

Oct. 11, 2017

Re: [Pharo-dev] PharoMinimal ?

by Torsten Bergmann

>If you will tell me what exactly you need we can make it work together as in case of PharoLambda. Even when this offer from Pavel was for Sven I would like to ask: What about a minimal "TelePharo ready image" that one can remotely connect to and then debug, enhance, ... Thanks T.

Oct. 10, 2017

Re: [Pharo-dev] [Pharo 7.0-dev] Build #176: 20505-The-special-objects-array-needs-to-be-recreated-during-bootstrap

by Pavel Krivanek

I agree with you, it is too dirty solution. The next try: https://pharo.fogbugz.com/f/cases/20506/Fix-special-objects-array Thank you for the pointers. Cheers, -- Pavel 2017-10-10 14:04 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com>: > Hi Pavel, > > I don't like this change. > > First, there is no comment nor explanation why that is needed. This change > is obscure, if we forget in a couple of months why that line of code is > there we may > - delete it unintentionally > - or leave it forever and fear to clean it up because we do not > understand it :( > > Second, It looks that recreating the special objects array there, like > that, means that it was not correctly created from the beginning. We should > instead create it correctly from the beginning. > > I think we should revert this change. > > On Tue, Oct 10, 2017 at 12:24 PM, <ci-pharo-ci-jenkins2(a)inria.fr> wrote: > >> There is a new Pharo build available! >> >> The status of the build #176 was: SUCCESS. >> >> The Pull Request #336 was integrated: "20505-The-special-objects-arr >> ay-needs-to-be-recreated-during-bootstrap" >> Pull request url: https://github.com/pharo-project/pharo/pull/336 >> >> Issue Url: https://pharo.fogbugz.com/f/cases/20505 >> Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20p >> ull%20request%20and%20branch%20Pipeline/job/development/176/ >> > > > > -- > > > > 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> >

Oct. 10, 2017

Re: [Pharo-dev] [Pharo 7.0-dev] Build #176: 20505-The-special-objects-array-needs-to-be-recreated-during-bootstrap

by ClÃ©ment Bera

Hi Guille, For "First": I looked into this problem with Pavel this morning. The special object array being incorrectly created leads to problems when a large object (bigger that growthHeadroom) is created, as it does not go through the handleFailingBasicNew methods. Typically, Pavel could not load Seaside into the minimal image because of that. The problem lies with the initialization of error codes. For "Second": I don't mind what you do as long as it solves the problem of large allocations on minimal images. In any case the problems lies with the error code symbols, so that the code in basicNew: ec == #'insufficient object memory' ifTrue: [^self handleFailingBasicNew: sizeRequested]. takes the correct branch. Before Pavel's change, the condition was false during bootstrap leading to large allocation crashing the VM, ec was equal to 9 instead of #'insufficient object memory', since the error codes in the special object array were incorrectly initialized somehow. PS: Who is nobody ? Cheers On Tue, Oct 10, 2017 at 2:04 PM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > Hi Pavel, > > I don't like this change. > > First, there is no comment nor explanation why that is needed. This change > is obscure, if we forget in a couple of months why that line of code is > there we may > - delete it unintentionally > - or leave it forever and fear to clean it up because we do not > understand it :( > > Second, It looks that recreating the special objects array there, like > that, means that it was not correctly created from the beginning. We should > instead create it correctly from the beginning. > > I think we should revert this change. > > On Tue, Oct 10, 2017 at 12:24 PM, <ci-pharo-ci-jenkins2(a)inria.fr> wrote: > >> There is a new Pharo build available! >> >> The status of the build #176 was: SUCCESS. >> >> The Pull Request #336 was integrated: "20505-The-special-objects-arr >> ay-needs-to-be-recreated-during-bootstrap" >> Pull request url: https://github.com/pharo-project/pharo/pull/336 >> >> Issue Url: https://pharo.fogbugz.com/f/cases/20505 >> Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20p >> ull%20request%20and%20branch%20Pipeline/job/development/176/ >> > > > > -- > > > > 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> > -- ClÃ©ment BÃ©ra Pharo consortium engineer https://clementbera.wordpress.com/ BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq

Oct. 10, 2017

Re: [Pharo-dev] [Pharo 7.0-dev] Build #176: 20505-The-special-objects-array-needs-to-be-recreated-during-bootstrap

by Guillermo Polito

Hi Pavel, I don't like this change. First, there is no comment nor explanation why that is needed. This change is obscure, if we forget in a couple of months why that line of code is there we may - delete it unintentionally - or leave it forever and fear to clean it up because we do not understand it :( Second, It looks that recreating the special objects array there, like that, means that it was not correctly created from the beginning. We should instead create it correctly from the beginning. I think we should revert this change. On Tue, Oct 10, 2017 at 12:24 PM, <ci-pharo-ci-jenkins2(a)inria.fr> wrote: > There is a new Pharo build available! > > The status of the build #176 was: SUCCESS. > > The Pull Request #336 was integrated: "20505-The-special-objects- > array-needs-to-be-recreated-during-bootstrap" > Pull request url: https://github.com/pharo-project/pharo/pull/336 > > Issue Url: https://pharo.fogbugz.com/f/cases/20505 > Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending% > 20pull%20request%20and%20branch%20Pipeline/job/development/176/ > -- 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

Oct. 10, 2017