August 2021 - Pharo-users - lists.pharo.org

Re: Introducing new feature dataTypes for the PolyMath/DataFrame project

by Balaji G

Hi Konrad Thanks for pointing this out. You are right with how the data types are calculated, similar to collection >> commonSuperClass. But this time, it is calculated only during the creation of DataFrame once and for all. Now coming to the next part, Kindly have a look at the below code. ------------------------------ series := #( nil nil nil ) asDataSeries. series calculateDataType. "UndefinedObject" . A nil value, or a Series of nil values yields UndefinedObject as its super class. There was an error with the dataset used on that example blog post. I have corrected it now. The problem was that the dataset was not clean, and had some garbage values of different types in that column. This resulted in a column, with type Object . This was the dataset and specifically the last column resulted in this mistake. On Sat, Aug 7, 2021 at 9:58 PM Konrad Hinsen <konrad.hinsen(a)fastmail.net> wrote: > Hi Balaji, > > > Please go through the following blog post. Any kind of suggestion or > > feedback is welcome. > > That's a nice description, easy to follow. But there is a missing piece: > how do you actually find the dataType for a series of values? My first > guess was that you are using the same method as Collection >> > commonSuperclass, but then a nil value should yield UndefinedObject, not > Object as in your example. > > Cheers > Konrad. >

Aug. 7, 2021

Re: Introducing new feature dataTypes for the PolyMath/DataFrame project

by Konrad Hinsen

Hi Balaji, > Please go through the following blog post. Any kind of suggestion or > feedback is welcome. That's a nice description, easy to follow. But there is a missing piece: how do you actually find the dataType for a series of values? My first guess was that you are using the same method as Collection >> commonSuperclass, but then a nil value should yield UndefinedObject, not Object as in your example. Cheers Konrad.

Aug. 7, 2021

Introducing new feature dataTypes for the PolyMath/DataFrame project

by Balaji G

Hello Everyone, I have been working on the addition of a new feature, DataFrame >> dataTypes, which briefs us about the data type of columns in dataframes we work on. Summarising a dataset is really important during the initial stage of any Data Science and Machine Learning tasks. Knowing the data type of the attribute is one major thing to begin with. I have tried to work with some sample datasets for a clear understanding of this new feature. Please go through the following blog post. Any kind of suggestion or feedback is welcome. Link to the Post : https://balaji612141526.wordpress.com/2021/08/06/introducing-new-feature-in… Previous discussions can be found here : https://lists.pharo.org/empathy/thread/BFOHPRUU72MDYVTJP3YV2DQ5LAZHXELE and here : https://lists.pharo.org/empathy/thread/JZXKXGHSURC3DCDA2NXA7KDWZ2EINAZ5 Cheers Balaji G

Aug. 6, 2021

Re: [ANN] Pharo 9 released!

by Offray Vladimir Luna CÃ¡rdenas

I'm catching up with the good news! Thanks a lot to everyone who makes them possible. Happy pharoeing!!! ;-), Offray On 15/07/21 4:14 a.Â m., Esteban Lorenzano wrote: > Dear World and dynamic language lovers:Â > > The time has come for Pharo 9 <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 features of Pharo 9:Â Â Â > > * > Full redesign of the Spec UI framework (new logic, application, > style, GTK3 back-end) > * > New tools: > * > o > new playground, > o > new object centric inspector, > o > new object centric debugger. > o > better and new Refactorings > o > class comments are now written in Microdown format (Markdown > compatible) > o > classes now can be defined using a "fluid" api (Preview) > * > New completion framework that adapts better to edition contexts > and is customizable > * > Fast universal non-blocking FFI which now uses libFFI as backend. > * > Pharo now supports Windows, OSX, Linux (Ubuntu, Debian, Fedora, > openSUSE, Arch, Raspbian) and multiple architectures (Intel/ARM > 32/64bits). > * > Virtual Machine > * > o > Idle VM > o > Support for ARM 64bits > o > Support for Apple M1 > o > More than 3000 tests > o > Built for Ubuntu 18.04, 19.04, 20.04, 21.04, 21.10; Debian 9, > 10, Testing; Fedora 32, 32, 34; openSUSE 15.1, 15.2, > Tumbleweed; Manjaro; Arch > * > Uses SDL 2.0 as back-end by default. It supports extended event > handling, including trackpad support. > * > General speed up due to compiler optimisations and UI simplification. > * > And many, many more tests. > > > These are just the more prominent highlights, but the details are just > as important. We have closed a massive amount of issues: around 1400 > issues and 2150 pull requests. > > A more extended changelog can be found at > https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo90Change… > <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo90Change…>. > > While the technical improvements are significant, still the most > impressive fact is that the new code that got in the main Pharo 9 > image was contributed by more than 90 people. > > Pharo is more than code. It is an exciting project involving a great > community.Â > > We thank all the contributors to this release: > > Aaron Bieber, Ackerley Tng, Alban Benmouffek, Ale Cossio, Alexandre > Bergel, Alistair Grant, Allex Oliveira, Angela Chia-Ling, Arturo > Zambrano, Asbathou Biyalou-Sama, Ben Coman, Benoit Verhaegue, Carlo > Teixeira, Carlos Lopez, Carolina Hernandez, Charles A. Monteiro, > Christoph Thiede, Christophe Demarey, Clotilde Toullec, Cyril > Ferlicot, Damien Pollet, Daniel Aparicio, David Bajger, David SÃ¡nchez > i Gregori, Denis Kudriashov, Ellis Harris, Eric Brandwein, Eric Gade, > Erik Stel, ErikOnBike, Esteban Lorenzano, Esteban Villalobos, Evelyn > Cusi Lopez, Evelyn Cusi Lopez, Ewan Dawson, Francis Pineda, Francis > Pineda, Gabriel Omar Cotelli, Geraldine Galindo, Giovanni Corriga, > Guille Polito, Himanshu jld, Johan Brichau, Jonathan van Alteren, > Jordan Montt, Julien Delplanque, Kamil Kukura, Kasper Ãsterbye, Kurt > Kilpela, Laurine Dargaud, Marco Rimoldi, Marcus Denker, Martin Dias, > Martin McClure, Massimo Nocentini, Max Leske, Maximilian Ignacio > Willembrinck Santander, Milton Mamani Torres, Moussa Saker, Myroslava > Romaniuk, Nicolas Anquetil, Norbert Hartl, Nour Djihan, Oleksandr > Zaitsev, Pablo SÃ¡nchez RodrÃguez, Pablo Tesone, Pavel Krivanek, > Philippe Lesueur, Pierre Misse, Rakshit P., Rob Sayers, Roland > Bernard, Ronie Salgado, Sean DeNigris, Sebastian Jordan MontaÃ±o, Serge > Stinckwich, Stephan Eggermont, Steven Costiou, StÃ©phane Ducasse, Sven > Van Caekenberghe, Thomas Dupriez, ThÃ©o Lanord, ThÃ©o Rogliano, Todd > Blanchard, Torsten Bergmann, Vincent Blondeau, WÃ©slleymberg Lisboa. > Â > > (If you contributed with Pharo 9 development in any way and we missed > your name, please send us an email 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>

Aug. 5, 2021

Is BuildingApplicationWithSpec2 project dead?

by tau

Hi . I'm talking about the Spec2 book located at https://github.com/SquareBracketAssociates/BuildingApplicationWithSpec2 . This book was really helpful to get me started with building GUI . However, it is obviously incomplete and there is a message from a maintainer (StÃ©phane Ducasse) inside the book stating that he'll stop working on it. Moreover, pull requests from Stephan Eggermont and rvillemeur have been waiting since last year. So, Is this book project dead and what are the alternatives? Regards.

Aug. 4, 2021

mongo code triggered #maxExternalSemaphores: on image restart

by Yanni Chiu

I had a problem where my image became unusable a few seconds after starting up. I got help on the database discord channel, and got my image back to usable. Hereâs a summary. [MacOS, Pharo9, MongoTalk 1.24, the image runs a Seaside,Voyage,Mongo app]. 1. I got the stack trace (see attached) a few seconds after image startup, then the image became unusable and had to be terminated from the OS. 2. I eventually figured out that I needed to re-establish the ssh tunnel to my mongo database. After that, I was able to start the image without problem. 3. A potential fix may have been in MongoTalk 1.25, where connections were being leaked due to non-local returns. The fix (see attached) would add an ensure: block. I filed-in the fix, which I was able to do, with the ssh tunnel on. 4. I turned off the ssh tunnel, then tried to start the image with the MongoTalk change installed and saved. But I still got the debugger after a few seconds. I eventually noticed that the image was still usable, if I just closed the debugger (actually, closed it two times, because it came up again). In the Transcript was: WARNING: Had to GC to make room for more external objects. If this happens often, it would be a good idea to either: - Raise the maxExternalSemaphores size. - Write your code to explicitly release them rather than wait for finalization. WARNING: Had to increase size of semaphore signal handling table due to many external objects concurrently in use You should increase this size at startup using #maxExternalSemaphoresSilently: Current table size: 1024 WARNING: Had to increase size of semaphore signal handling table due to many external objects concurrently in use You should increase this size at startup using #maxExternalSemaphoresSilently: Current table size: 2048 So the MongoTalk fix would have salvaged the image too. 5. Digging around, I found the following would clean things up: MongoMonitor allInstances. "size: 95" MongoMonitor allInstancesDo: [ :each | each stop; tearDown ]. Smalltalk garbageCollect. MongoMonitor allInstances. "size: 6â After that, the pharo CPU usage went down from 23% to 5% Cheers, Yanni Chiu

Aug. 4, 2021

Facing a very strange Issue while creating a Pull Request

by Balaji G

Hello Everyone, I have been working in Pharo for the PolyMath/DataFrame project for around 4 months now. There has been an issue with every PR I try to make.I did not pay enough attention to it at the beginning, but it is making it hard for the maintainers of the project to review my PR. The problem is that Github shows more number of files changed than actual changed, I actually made changes in 2 files but total files changed in Github shows 8, while I did not even touch the remaining files.but the code is the same and it is removed and added in remaining files which is super strange. I am using Windows 10 Operating System with 8GB Ram and 512 GB SSD, Intel core 13 10th Generation. I tried the following to solve the issue but failed: 1) Uninstalled Pharo Launcher and re-installed it again. Even deleted every image and started everything fresh again. 2) Created a new Github account only for this problem, forked a fresh copy there, but did not help. 3) Tried Linux Mint Operating System and did the same. While the first PR through Linux (where I added just a test method) worked, I started facing the same problem later on. 4) I also somehow managed to grab a Mac OS High Sierra and installed Pharo, did the same. But no change. 5) I thought this could be due to CRLF to LF changes, which is common when switching Operating Systems, like End of the file, end of the line, tabs being converted to spaces etc. But this is definitely not the case here I guess. 5) I have also tried using the SSH protocol while cloning from Github. It did not make any difference. Please take a look at this short video in order to understand this issue clearly: https://youtu.be/AEmOh1-tyA0 <https://youtu.be/AEmOh1-tyA0> . You can look at the fork: https://github.com/BalajiG1862/DataFrame. The commit Information: https://github.com/BalajiG1862/DataFrame/commit/37604091538987b3ed93c34b8ed… <https://github.com/BalajiG1862/DataFrame/commit/37604091538987b3ed93c34b8ed…> . I tried every possible way to rectify this, even bugging a few members from Pharo Community through Direct Message. I have been trying to overcome this for the past 10 days full time, and yet no single clue. I am pretty sure there is something minor that I am missing, but could not find and rectify it. Every single idea will definitely benefit me anyhow, because I have nothing more to try. Hoping for someone to actually read till here Balaji G

Aug. 3, 2021

Re: Preserve VCS history while renaming package

by Vitor Medina Cruz

Found this issue: https://github.com/pharo-vcs/iceberg/issues/82 I did the renaming from git bash and it works as a good workaraound. On Fri, Jul 30, 2021 at 11:49 AM Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > Hello, > > Is it possible to rename a package while keeping code history? When I do > that, for example, rename from A to B, Iceberg shows me that A is no longer > loaded, it is not aware of the refactoring. If I remove A and add package B > and prompts a commit, it shows me like all inside B is new and that A was > deleted, losing the renaming history link. Is it possible to keep that > link, and workaround or such thing, or for now it isn't supported? > > Thanks, > Vitor >

Aug. 1, 2021

Re: Are there any docs for ReferenceFinder?

by Tim Mackinnon

As a follow-on question to this - it seems that the playground keeps hidden references to things (although the image I am trying this in, looks to be some earlier P9 image - so potentially the GTK version of the playground is better). However I am wondering why if I close my playground and open a fresh one, and restore its snippets - why the following doesnât seem to clean up garbage: 3 timesRepeat: [ Smalltalk garbageCollect ]. MwpDocumentDetails allInstances. Neither does the following: Smalltalk garbageCollect. Smalltalk garbageCollect. Smalltalk garbageCollect. MwpDocumentDetails allInstances. But the following: Smalltalk garbageCollect. <- cmd-g this 3 times MwpDocumentDetails allInstances. Does? Something seems rather suspicious to me in all thisâ¦ although I need to replicate this in a proper P9 image - but I was curious what the difference is - and whether its the playground that is the leading cause of this? Tim > On 1 Aug 2021, at 15:56, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi everyone - I was curious why my image is 3gb, and recently someone mentioned ReferenceFinder which Iâve not used before - however the class comment for it is very terse and it doesnât really explain what a âreference path isâ and how to interpret the results you get back from it? > > eg. I did the following - as I have lots of instances of Document object I have been using in an an inspector - however I had cleared out the owner objects list of these things, and so they should be gone. However I see the following: > > ReferenceFinder findAllPathsTo: X allInstances first. > > Result - a collection of objects (as in the photo). So am I to understand that the âpathâ is actually the collection? Each item in the collection is the next segment of the path to the ultimate object (which might be useful for the class description to say - and I will correct if thatâs the case). > > <PastedGraphic-1.png>

Aug. 1, 2021

Are there any docs for ReferenceFinder?

by Tim Mackinnon

Hi everyone - I was curious why my image is 3gb, and recently someone mentioned ReferenceFinder which Iâve not used before - however the class comment for it is very terse and it doesnât really explain what a âreference path isâ and how to interpret the results you get back from it? eg. I did the following - as I have lots of instances of Document object I have been using in an an inspector - however I had cleared out the owner objects list of these things, and so they should be gone. However I see the following: ReferenceFinder findAllPathsTo: X allInstances first. Result - a collection of objects (as in the photo). So am I to understand that the âpathâ is actually the collection? Each item in the collection is the next segment of the path to the ultimate object (which might be useful for the class description to say - and I will correct if thatâs the case).

Aug. 1, 2021