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

Re: [Pharo-dev] [ANN] New Academic Partner: ENIT

by CÃ©drick BÃ©ler

First of all, thanks for the introduction Marcus. Just that people know, and to introduce myself, Iâm CÃ©drik BÃ©ler, associate professor at ENIT (Nation Engineering School of Tarbes). ENIT is a French generalist engineering school in Tarbes (southwest of France). Iâm very happy that ENIT is now part of the consortium as academic member. Pharo and Smalltalk have been a huge source of inspiration for me during my PHD back in 2004/2008, so Iâm really happy to have a more concrete participation now. My objectives are of two kind: (1) use Pharo as a digital workbench to teach engineering students and experiment ICT trends like IoT (PharoThings/Pi3/PiZero/ESP32), AI, web applications (client/server, MQTT, API usage with Zinc, web scrapping with XPATH and Zinc and Neoâ¦). (2) use Pharo for my research to prototype Cyber-Physical Systems (mainly in the field of predictive maintenance) and Distributed Information Systems (called Singular Information System). Iâll give a talk at ESUG as an experience feedback for point (1). In the future, Iâll present our research development around CPSâs. Iâm also interested in developing a local user group. Some students get interested. In Biarritz, ESTIA, I also have some common interest in developing such CPS researches/platforms. If people from this area are using Pharo/Smalltalk, please do not hesitate to contact me. To conclude, Iâm interested in plenty of Pharo sub-projects like (non exhaustive list): - The web/network stack (Zinc, Zodiac, Neo, XPathâ¦) - PharoThings - Bloc/Brick/Roassal - Wooden3D (VR and AR) - Workflow - Distributed networking (opportunistic, MESH, discovery, â¦) See you soon over there, Cheers, CÃ©drick BÃ©ler ENIT associate professor Discord: cedreek#8178 > Le 4 juil. 2018 Ã 11:27, Marcus Denker <marcus.denker(a)inria.fr> a Ã©crit : > > [ANN] New Academic Partner: ENIT > > The Pharo Consortium is very happy to announce that ENIT has joined as a Academic Partner. > > About > - ENIT Ecole Nationale d'ingÃ©nieurs de Tarbes: http://www.enit.fr > - Pharo Consortium: http://consortium.pharo.org > > The goal of the Pharo Consortium is to allow companies and institutions to > support the ongoing development and future of Pharo. > > Individuals can support Pharo via the Pharo Association: > > http://association.pharo.org

July 4, 2018

[Pharo 7.0-dev] Build #1112: 22212 Some cleanups in GrowlMorph

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

There is a new Pharo build available! The status of the build #1112 was: SUCCESS. The Pull Request #1601 was integrated: "22212 Some cleanups in GrowlMorph" Pull request url: https://github.com/pharo-project/pharo/pull/1601 Issue Url: https://pharo.fogbugz.com/f/cases/22212 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 4, 2018

Re: [Pharo-dev] Commenting test classes?

by Norbert Hartl

> Am 04.07.2018 um 00:45 schrieb Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com>: > > Le 04/07/2018 Ã 00:39, Tim Mackinnon a Ã©crit : >> Au contraire - when looking at a Test - seeing inline the comment of the >> class to remind me what Iâm supposed to be testing is actually quite >> helpful. I fully expect this is where GtDocumentor is going to take us >> (if we integrate it into our tools) - letting us inline things so we >> donât have to go and hunt them out. >> >> > > > In general most of my tests classes are here to test one class, then the > name is "NameOfMyClassTests". In that case there is no need for a > comment like "I am a test class for NameOfMyClass". > > I comment tests classes only when it's more functional tests and that > they cover a part of the system. > > But I don't want to have to add comment such as "I am a test class for > NameOfMyClassâ for the vast majority of my test classes. > same for me. Superfluous things have negative impact. Norbert

July 4, 2018

[Pharo 7.0-dev] Build #1111: 22226 Cleanups in DebuggerModel

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

There is a new Pharo build available! The status of the build #1111 was: FAILURE. The Pull Request #1611 was integrated: "22226 Cleanups in DebuggerModel" Pull request url: https://github.com/pharo-project/pharo/pull/1611 Issue Url: https://pharo.fogbugz.com/f/cases/22226 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 4, 2018

[ANN] New Academic Partner: SQLab

by Marcus Denker

The Pharo Consortium is very happy to announce that SQLab has joined as a Academic Partner. About - Software Quality Laboratory, Part of University of Novi Sad: https://sqlab.pmf.uns.ac.rs - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: http://association.pharo.org

July 4, 2018

[ANN] New Academic Partner: ENIT

by Marcus Denker

[ANN] New Academic Partner: ENIT The Pharo Consortium is very happy to announce that ENIT has joined as a Academic Partner. About - ENIT Ecole Nationale d'ingÃ©nieurs de Tarbes: http://www.enit.fr - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: http://association.pharo.org

July 4, 2018

ANN: new stable VM promoted to P7

by Esteban Lorenzano

Hi all, I promoted a new stable VM for Pharo 7.0. This one corresponds to build: 201806281256-a8a1dc1 If everything goes fine, I will backport it for Pharo 6.1 in one month. (and if something goes wrong, I will rollback so please let me know any issues). cheers, Esteban

July 4, 2018

Re: [Pharo-dev] Promote new Pharo 7 VM?

by Esteban Lorenzano

youâre right :) > On 3 Jul 2018, at 13:55, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Esteban, > > On Mon, 18 Jun 2018 at 23:15, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> yes, why not :) >> but, remember the cycle: >> >> 1. two weeks in latest (that starts today) > > Just a friendly reminder that the two weeks is done... :-) > > Thanks, > Alistair > > >> 2. one month in stable 7.0 >> 3. promote to stable 6.1 >> >> yes, is annoying, but is the scheme has worked the better to avoid problems. >> >> cheers, >> Esteban >> >>> On 18 Jun 2018, at 14:20, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>> >>> Hi Esteban, >>> >>> Would you consider promoting a new Pharo 7 VM? >>> >>> 140ff02 should finally solve an issue I've had with time zones and DST >>> on Windows in the FileAttributesPlugin. >>> >>> Testing I've done on this VM: >>> >>> - Loaded up and used my normal dev environment. >>> - Run the full automated test suite on: >>> -- Linux 64 bit >>> -- Linux 32 bit >>> -- Win 32 bit >>> >>> In each case the set of failures in my environment roughly aligns with >>> the current stable VM and the proposed one. >>> >>> I guess if anyone else has any objections they'll reply to this. :-) >>> >>> Of course, if you've got any questions or concerns, please let me know. >>> >>> In case it is useful for anyone, download links are: >>> >>> Linux 64 bit: http://files.pharo.org/vm/pharo-spur64/linux/pharo-linux-x86_64threaded-201… >>> Linux 32 bit: http://files.pharo.org/vm/pharo-spur32/linux/pharo-linux-i386threaded-20180… >>> Mac 64 bit: >>> - http://files.pharo.org/vm/pharo-spur64/mac/pharo-mac-x86_64-201806171702-14… >>> - http://files.pharo.org/vm/pharo-spur64/mac/pharo-mac-x86_64-201806171702-14… >>> Mac 32 bit: >>> - http://files.pharo.org/vm/pharo-spur32/mac/pharo-mac-i386-201806171702-140f… >>> - http://files.pharo.org/vm/pharo-spur32/mac/pharo-mac-i386-201806171702-140f… >>> Win 32 bit: http://files.pharo.org/vm/pharo-spur32/win/pharo-win-i386-201806171702-140f… >>> >>> >>> Thanks! >>> Alistair >>> >> >> >

July 4, 2018

Re: [Pharo-dev] About the infinite debugger

by Martin McClure

On 07/03/2018 05:02 PM, Martin McClure wrote: > On 06/29/2018 07:48 AM, Guillermo Polito wrote: >> I know that the exception handling/debugging has been modified several >> times in the latest years (some refactorings, hiding contexts...), we >> unfortunately don't have tests for it, so I'd like some more pair of >> eyes on it. Ben, Martin could you take a look? >> > Hi Guille, > I'm just back from vacation last week, and about to go on vacation for > another week, but I'll see what I can see. > About the primitive pragmas for context-marking, I think some of those > were changed for the exception handling fix that Andres and I did a few > years back, so *could* be involved in this. I'd hate to see regression > in the exception handling in an attempt to fix this bug. > After a look at at the pull request, I'm quite sure that removing the prim 199 marker is the wrong thing to do. Thanks, Pablo, for restoring it! The start of execution of exception handlers must be marked in order for #findNextHandlerContext to work correctly. If these contexts are not marked, exceptions signaled from inside an exception handler can find the wrong handler. See the code and comment in #findNextHandlerContext. I'm afraid that I cannot immediately help with the debugger problem, since I don't know the debugger nearly as well as I do the exception handling code, and I'm going on vacation for a week in 20 minutes. :-) Perhaps when I get back I can take a look at it if it is still a problem by then. Regards, -Martin

July 4, 2018

Re: [Pharo-dev] About the infinite debugger

by Martin McClure

On 06/29/2018 07:48 AM, Guillermo Polito wrote: > Hi all, > > during today's sprint we have been working with lots of people on the > infinite debugger problem (https://pharo.fogbugz.com/f/cases/22085/) > We have checked the emails sent in the latest month. Then, together > with Quentin, Pablo, Pavel, Yoan we have been discussing and testing > hypothesis all day. We have been also comparing the debuggers code > between pharo 3/4 (where the bug was is present) and pharo 7, but this > was not necessarily straight forward as the code is not the same and > there is no easy diff... > > AAAAND, we have found that the problem may come from a wrong pragma > marker. Just removing that pragma gives us back the same behaviour as > inÂ Pharo 3/4. :D > > https://github.com/pharo-project/pharo/pull/1621 > > I know that the exception handling/debugging has been modified several > times in the latest years (some refactorings, hiding contexts...), we > unfortunately don't have tests for it, so I'd like some more pair of > eyes on it. Ben, Martin could you take a look? > Hi Guille, I'm just back from vacation last week, and about to go on vacation for another week, but I'll see what I can see. About the primitive pragmas for context-marking, I think some of those were changed for the exception handling fix that Andres and I did a few years back, so *could* be involved in this. I'd hate to see regression in the exception handling in an attempt to fix this bug. Regards, -Martin

July 4, 2018