January 2020 - Pharo-dev - lists.pharo.org

Unnecessary double checks of infinity
by Serge Stinckwich Jan. 22, 2020

Jan. 22, 2020

Hi all, I'm having a look how floats are printed. Why we check two times if a Float is infinite ? A first time in: Float>>printOn: stream base: base ... self isInfinite ifTrue: [ stream nextPutAll: 'Float infinity'. ^ self sign = -1 ifTrue: [ stream nextPutAll: ' negated' ] ]. ... and a second time in: Float>>absPrintExactlyOn: aStream base: base ... self isInfinite ifTrue: [ aStream nextPutAll: 'Float infinity'. ^ self]. ... the same in Float>>absPrintInexactlyOn: aStream base: base ... self isInfinite ifTrue: [aStream nextPutAll: 'Float infinity'. ^ self]. ... Apparently the last two methods are never called when number is infinite. I remove the second checks and apparently nothing breaks (all number tests are still green). Regards, -- Serge Stinckwic h Int. Research Unit on Modelling/Simulation of Complex Systems (UMMISCO) Sorbonne University (SU) French National Research Institute for Sustainable Development (IRD) U niversity of YaoundÃ© I, Cameroon "Programs must be written for people to read, and only incidentally for machines to execute." https://twitter.com/SergeStinckwich

1 1

Fwd: [GitHub] Deprecation Notice
by ducasse Jan. 22, 2020

Jan. 22, 2020

what will be the implication? > Begin forwarded message: > > From: GitHub <noreply(a)github.com> > Subject: [GitHub] Deprecation Notice > Date: 21 January 2020 at 21:03:28 CET > To: StÃ©phaneDucasse <stephane.ducasse(a)inria.fr> > > Hi @Ducasse, > > You recently used a password to access an endpoint through the GitHub API using Zinc HTTP Components 1.0 (Pharo/9.0). We will deprecate basic authentication using password to this endpoint soon: > > https://api.github.com/repositories/169849137 <https://api.github.com/repositories/169849137> > > We recommend using a personal access token (PAT) with the appropriate scope to access this endpoint instead. Visit https://github.com/settings/tokens <https://github.com/settings/tokens> for more information. > > Thanks, > The GitHub Team

6 9

Processor>>activeProcess is wrong when a process is stepped by a forked process
by Thomas Dupriez Jan. 21, 2020

Jan. 21, 2020

Hello Some time ago, I've stumbled upon a challenging bug in pharo. I tried some things, but this bug still eludes me. Maybe someone here has an idea? The bug is that the value of `Processor activeProcess` is wrong inside a process being stepped by a forked process. In other words, let's say process D is the (frozen) process I am debugging, and its code is to store the active process into some variable with `p := Processor activeProcess`: - If I step process D normally (with `D step`), then p is correct and worth process D - If I fork to create a process F that steps process D, then p is incorrect and worth process F You will find below the code of the two tests I am using to show the bug, as well as a condensed version of my findings so far. If you have any idea or lead as to where this bug could come from, I would be very grateful. Thomas Dupriez ----- Here is the code of the failing test, where process F steps process D: ``` /testActiveProcessInProcessSteppedInForkedProcess// //| s p D done |// //Â Â Â s := Semaphore new. done := false.// //Â Â Â "Create debugged process"// //Â Â Â D := [p := Processor activeProcess. done := true] newProcess name: 'D'; yourself.// //Â Â Â "Until the execution of the debugged process is over, create a forked process to step it"// //Â Â Â [done]// //Â Â Â Â Â Â whileFalse: [ // //Â Â Â Â Â Â Â Â Â [debuggedProcess step. s signal] forkNamed: 'F'.// //Â Â Â Â Â Â Â Â Â s wait.// //Â Â Â Â Â Â ].// //Â Â Â self assert: D identicalTo: p/ ``` And here is the passing test, where we step process D directly: ``` /testActiveProcessInProcessDirectlyStepped// //| s p D done |// //Â Â Â s := Semaphore new. done := false.// //Â Â Â "Create debugged process"// //Â Â Â D := [p := Processor activeProcess. done := true] newProcess name: 'D'; yourself.// //Â Â Â "Until the execution of the debugged process is over, step it directly"// //Â Â Â [done]// //Â Â Â Â Â Â whileFalse: [ // //Â Â Â Â Â Â Â Â Â debuggedProcess step.// //Â Â Â Â Â Â ].// //Â Â Â self assert: D identicalTo: p/ ``` ----- Here are my findings so far: The call chain of Process>>step is: - Process>>step - which calls Process>>evaluate:onBehalfOf: - which calls BlockClosure>>ensure: - which calls BlockClosure>>valueNoContextSwitch 1) Replacing the call to BlockClosure>>valueNoContextSwitch with a call to BlockClosure>>value does not affect the results of the test 2) Since #valueNoContextSwitch is a primitive, it cannot be instrumented easily. I instrumented right before and after it gets called in the code of BlockClosure>>ensure to check the value of active process. No wrong value there, so the problem appears inside the execution of #valueNoContextSwitch, and it disappears before this method call returns. 3) The block being evaluated by #valueNoContextSwitch contains a call to Context>>step, which ultimately calls InstructionStream>>interpretNextV3PlusClosureInstructionFor: (the method that read what the next bytecode is and applies it to the execution it is stepping. I instrumented this method to log the name of the active process, and the context being stepped during the execution of both tests. The log show a difference between the passing and failing test: - Passing test: the active process is D for a long time, then 'Test execution watch dog" for a bit, and finally, it is "Morphic UI Process". So everything looks in order: the active process is D until the test ends and the UI process takes control back - Failing test: The logged active process alternates between F and D, and looks like this: (I put some F D patterns in bold for readability) *F D* F D *F D*.....*F D* F F D F F *F D* F D *F D*...*F D* D D D D r M M M M... "M" is the morphic UI Process, "r" is a seemingly random process whose name is "1006977792" in the log. I also logged the ast nodes being stepped, but I don't really know how to exploit it. 4) I did some experiments by tweaking the tests and changing which process creates D, which process steps F...and had surprising results: 4-1) Original failing test a In the original failing test, the test process creates the debugged process and a fork, and the fork steps the debugged process (blue arrow). This test fails. 4-2) Original passing test a In the original passing test, the test process creates the debugged process and steps it. This test passes. 4-3) Forked process creates AND steps the debugged process a If the forked process is the one to create the debugged process, the test passes! 4-4) /Forked process creates the debugged process, and TestProcess steps it/ a So maybe the test passes whenever the debugged process is a descendant of the process stepping it? No, 4-5) shows that it is not necessary. 4-5) /A forked process creates the debugged process. Another forked process steps the debugged process /a

2 1

Short Survey about automatic deprecation rewrites
by Guillermo Polito Jan. 21, 2020

Jan. 21, 2020

Hi all, We would like to share with you a short survey about the automatic deprecation rewrites that have been around since Pharo 6. It will be super useful for us to enhance the support for migrations. We estimate it will take ~< 3 minutes to fill. This survey is aimed at people both *using* Pharo, or writing libraries and frameworks for Pharo. If youâre a library/framework maintainer and you know people using your library, would you mind share it with them? Link to the survey: https://sondages.inria.fr/index.php/133442?lang=en <https://sondages.inria.fr/index.php/133442?lang=en> Thanks a lot! Guille, in behalf of the Pharo consortium

4 3

[Pharo 9.0] Build #16: Switch to the light theme
by ci-pharo-ci-jenkins2＠inria.fr Jan. 21, 2020

Jan. 21, 2020

There is a new Pharo build available! The status of the build #16 was: SUCCESS. The Pull Request #5535 was integrated: "Switch to the light theme" Pull request url: https://github.com/pharo-project/pharo/pull/5535 Issue Url: https://github.com/pharo-project/pharo/issues/switchToLightTheme Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Pharo 8.0 Released!
by Esteban Lorenzano Jan. 21, 2020

Jan. 21, 2020

Dear World and dynamic language lovers: The time has come for Pharo 8.0 <https://pharo.org/>! Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. Here are the key highlights of this release: The 64-bit version has become the recommended version for Windows as it was for Unix and OSX. Iceberg, the git client for Pharo, reached its version 1.6.5 with several improvements and bugfixes. Calypso, Pharoâs system browser has new and better refactoring integrations and AST-based suggestions for class definitions. The unified foreign function interface (UnifiedFFI) has been improved with more support for literal objects, better type coercions, and more documentation. Several speed improvements in code searches and compilation. In addition, this version includes several previews of new tools such as the Spec2 GUI framework with native widget integration and the new DrTests test analysis tool and opens the door for the upcoming headless VMs for servers and non-blocking FFI. These are just the more prominent highlights, but the details are just as important. We have closed a massive amount of issues: 2805 issues! A comprehensive changelog can be found at https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo80Change… <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo60Change…>). While the technical improvements are significant, still the most impressive fact is that the new code that got in the main Pharo 8.0 image was contributed by more than 100 people. Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors to this release: Serge Stinckwich, Myroslava Romaniuk, Hilaire Fernandes, Alexandre Bergel, David Bajger, Sean DeNigris, Theodore Moen, Dayne Guerra Calle, Juraj Kubelka, Max Leske, Santiago Jose Dandois, Alistair Grant, Sabine Mana, Chia Yu, Stephan Eggermont, Milton Mamani, Pavel Krivanek, Ben Coman, Marcus Denker, Pierre Misse, Christophe Demarey, Allex Oliveira, Andreina Cota, Theo Rogliano, ClÃ©ment Dutriez, Quentin Ducasse, Cyril Ferlicot, Cameron Bierwagen, Marek Niepieklo, Clotilde Toullec, Esteban Lorenzano, Vincent Blondeau, Danil Osipchuk, Eiichiro Ito, Noury Bouraqadi, Oleksandr Zaytsev, Jason Riggs, Alain Plantec, Kasper Osterbye, Leonardo Cecchi, Chi Huynh, Santiago Bragagnolo, Antonio Pierro, Pablo Tesone, Tim Mackinnon, Wesley Duerksen, Wilfred Hughes, John Brant, Evelyn Cusi Lopez, Manuel Leuenberger, Thomas Dupriez, Norbert Hartl, Torsten Bergmann, Gabriel Omar Cotelli, Carlo Teixeira, Guille Polito, Torsten Bergman, Damien Pollet, Holger Hans Peter Freyther, Julio Ripoll, Carolina Hernandez Phillips, Julien Delplanque, Hugo Lasnier, James Foster, Will Hensel, Erik Stel, Sven Van Caekenberghe, MartÃn Dias, Tomohiro Oda, Konrad Hinsen, SeÌbastien Roccaserra, StÃ©phane Ducasse, Denis Kudriashov, Ellis Harris, Steven Costiou (If you contributed with Pharo 8.0 development in any way and we missed your name, please send us a mail and we will add you). Enjoy! The Pharo Team Try Pharo: http://pharo.org/download <https://pharo.org/download> Learn Pharo: http://pharo.org/documentation <https://pharo.org/documentation> If you cannot see this, follow this link: http://pharo.org/news/pharo8.0-released

9 10

[Pharo 9.0] Build #15: saferOmbuFileAccess
by ci-pharo-ci-jenkins2＠inria.fr Jan. 21, 2020

Jan. 21, 2020

There is a new Pharo build available! The status of the build #15 was: SUCCESS. The Pull Request #5532 was integrated: "saferOmbuFileAccess" Pull request url: https://github.com/pharo-project/pharo/pull/5532 Issue Url: https://github.com/pharo-project/pharo/issues/saferOmbuFileAccess Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Pharo TechTalk Jan 23
by Marcus Denker Jan. 21, 2020

Jan. 21, 2020

A regular chat about Pharo. Happens on Discord. â¢ When 23 Jan 2020 â¢ 5:00 PM - 6:00 PM (UTC+01:00) Topic: Contributing to Iceberg (Git support) https://association.pharo.org/event-3697009

1 0

[Pharo 9.0] Build #14: SUCCESS
by ci-pharo-ci-jenkins2＠inria.fr Jan. 21, 2020

Jan. 21, 2020

There is a new Pharo build available! The status of the build #14 was: SUCCESS. Could not extract further issue information from commit message: Merge branch 'Pharo8.0' into Pharo9.0 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Mm10s] 2020-01-20
by ducasse Jan. 20, 2020

Jan. 20, 2020

Last week - concurrent programming booklet - coded an interpreter for the new version of ObjVlisp called PicoCore. - reviewing work of Esteban Villalobos on improving rules - renaming rules and learning the hard way that we should have a protocol to unload classes (like in VW). - resuming fluid class definition parser - code reviews for P8 - better ProgramNodeVisitor (more and nicer hooks) -> Pharo 90 Forthcoming - finish concurrent programming booklet - working on fluid definition parser - look at live typing with hernan wilkinson - start to play with Spec20 - want to be a guinea pig for the new debugger

1 0