February 2023 - Pharo-users

This week (8/2023) on the Pharo Issue Tracker

by Marcus Denker

We merged 24 PRs this week: Compiler ======== - Improve faulty parsing #12778 https://github.com/pharo-project/pharo/pull/12778 - Improve faulty parsing of cascades #12816 https://github.com/pharo-project/pharo/pull/12816 - Improve faulty parsing of assigments #12815 https://github.com/pharo-project/pharo/pull/12815 Features ======== - Introducing a Color Palette to cache the allocation of Color objects by tht UITheme #12771 https://github.com/pharo-project/pharo/pull/12771 - Add #closeTo: on sequenceable collection #12800 https://github.com/pharo-project/pharo/pull/12800 - Filter on substrings in DrTest #12823 https://github.com/pharo-project/pharo/pull/12823 - load equals packages #12616 https://github.com/pharo-project/pharo/pull/12616 - Debugger configuration toolbar improvements #467 https://github.com/pharo-spec/NewTools/pull/467 Fixes ===== - Update Roassal version v0.9.9m #12792 https://github.com/pharo-project/pharo/pull/12792 - Sync Zinc 17 February 2023 #12794 https://github.com/pharo-project/pharo/pull/12794 - 1279 merge menu should indicate the sense of the action #1680 https://github.com/pharo-vcs/iceberg/pull/1680 - Fixes: Committing with empty description can lead to problems #1681 #1682 https://github.com/pharo-vcs/iceberg/pull/1682 - Fixes testInstanceSideInitializeMethodNeedsToBeInInitializationProtocol #12797 https://github.com/pharo-project/pharo/pull/12797 Cleanups ======== - Remove #wantsSteps from object and uses #respondsTo: in the system wiâ¦ #12793 https://github.com/pharo-project/pharo/pull/12793 - Remove old unicode initializer #12803 https://github.com/pharo-project/pharo/pull/12803 - Rename bootstrap 3rd step to be the 2nd now #12812 https://github.com/pharo-project/pharo/pull/12812 - AthensPathBuilder should be abstract #12827 https://github.com/pharo-project/pharo/pull/12827 - Fix typo #12801 https://github.com/pharo-project/pharo/pull/12801 - extract return. fix: #12809 #12810 https://github.com/pharo-project/pharo/pull/12810 - Remove depreceted class reference #12808 https://github.com/pharo-project/pharo/pull/12808 - Condensation of source 2 #12799 https://github.com/pharo-project/pharo/pull/12799 - Condensation of sources 3 #12802 https://github.com/pharo-project/pharo/pull/12802 - replace == nil with ifNil:ifNotNil: #12814 https://github.com/pharo-project/pharo/pull/12814 - Cleanup: Condense Zodiac packages #12762 https://github.com/pharo-project/pharo/pull/12762

Feb. 24, 2023

Re: New Memory Profiler

by Marcus Denker

I will have a look, it has nothing to do with the memory profiler. Marcus > On 23 Feb 2023, at 17:57, Bernardo Ezequiel Contreras <vonbecmann(a)gmail.com> wrote: > > is it possible to inspect this > https://github.com/pharo-project/pharo/issues/12831 > <https://github.com/pharo-project/pharo/issues/12831> > ? and see what's going on? > > On Tue, Feb 21, 2023 at 8:04 AM Sebastian Jordan Montano <sebastian.jordan(a)inria.fr <mailto:sebastian.jordan@inria.fr>> wrote: >> Hello, >> >> I have been working on a new Memory Profiling for profiling object allocations. >> The profiler has reached a first stable version and I would like to share it with you. https://github.com/jordanmontt/illimani-memory-profiler >> >> The profiler gives some statistics, cool visualizations, like a heat-map, about the allocations and memory usage. >> If you want to profile the memory of some applications, this tool can help you. >> Also, if you have some use cases or you have some feedback please let us know because we are looking to improve the tool :) >> >> Cheers, >> Sebastian Jordan >> > > > -- > Bernardo E.C. > > Sent from a cheap desktop computer in South America.

Feb. 24, 2023

Re: Pharo accepted to Google Summer of Code 2023

by Guillermo Polito

Thanks guys for the super job with the admin, the website, and the gathering of ideas! > El 23 feb. 2023, a las 16:53, Sebastian Jordan Montano <sebastian.jordan(a)inria.fr> escribiÃ³: > > Hello! > We are happy to announce that we got accepted for this year Google Summer of Code! > This is really good for us because it helps to expand the impact of our technologies and to have more people involved in our community. > > Please share it on your social medias. I will put some links > - GSoc website https://summerofcode.withgoogle.com/ <https://summerofcode.withgoogle.com/> > - Gsoc website of Pharo organisation: https://www.gsocorganizations.dev/organization/pharo-consortium/ <https://www.gsocorganizations.dev/organization/pharo-consortium/> > - our gsoc page https://gsoc.pharo.org/ideas <https://gsoc.pharo.org/ideas> > > Cheers, > Sebastian Jordan in regard of the Pharo Consortium

Feb. 24, 2023

Exercism's new test runner - review needed

by bajger＠gmail.com

Hi there! \ Iâm looking for someone, who could do review of PR that implements new test runner for Exercism project that includes Pharo track. It is nice integration of using Pharo from command line, Docker (with different build args for loading correct baseline) and testing the test suite with json output (according to Exercism specific format). \ Exercism core maintainters lack knowledge of Pharo. Your help is welcome! PR here: https://github.com/exercism/pharo-smalltalk/pull/563 Related Docker part (already reviewed): https://github.com/exercism/pharo-smalltalk-test-runner/pull/16 Cheers, David

Feb. 24, 2023

Re: New Memory Profiler

by Bernardo Ezequiel Contreras

is it possible to inspect this https://github.com/pharo-project/pharo/issues/12831 ? and see what's going on? On Tue, Feb 21, 2023 at 8:04 AM Sebastian Jordan Montano < sebastian.jordan(a)inria.fr> wrote: > Hello, > > I have been working on a new Memory Profiling for profiling object > allocations. > > The profiler has reached a first stable version and I would like to share > it with you. https://github.com/jordanmontt/illimani-memory-profiler > > The profiler gives some statistics, cool visualizations, like a heat-map, > about the allocations and memory usage. > > If you want to profile the memory of some applications, this tool can help > you. > > Also, if you have some use cases or you have some feedback please let us > know because we are looking to improve the tool :) > > Cheers, > > Sebastian Jordan > > -- Bernardo E.C. Sent from a cheap desktop computer in South America.

Feb. 23, 2023

Pharo accepted to Google Summer of Code 2023

by Sebastian Jordan Montano

Hello! We are happy to announce that we got accepted for this year Google Summer of Code! This is really good for us because it helps to expand the impact of our technologies and to have more people involved in our community. Please share it on your social medias. I will put some links - GSoc website [ https://summerofcode.withgoogle.com/ | https://summerofcode.withgoogle.com/ ] - Gsoc website of Pharo organisation: [ https://www.gsocorganizations.dev/organization/pharo-consortium/ | https://www.gsocorganizations.dev/organization/pharo-consortium/ ] - our gsoc page [ https://gsoc.pharo.org/ideas | https://gsoc.pharo.org/ideas ] Cheers, Sebastian Jordan in regard of the Pharo Consortium

Feb. 23, 2023

Re: New Memory Profiler

by Esteban Lorenzano

nice :) On Feb 21 2023, at 12:04 pm, Sebastian Jordan Montano <sebastian.jordan(a)inria.fr> wrote: > Hello, > > I have been working on a new Memory Profiling for profiling object allocations. > The profiler has reached a first stable version and I would like to share it with you. https://github.com/jordanmontt/illimani-memory-profiler > > > The profiler gives some statistics, cool visualizations, like a heat-map, about the allocations and memory usage. > If you want to profile the memory of some applications, this tool can help you. > Also, if you have some use cases or you have some feedback please let us know because we are looking to improve the tool :) > > Cheers, > Sebastian Jordan >

Feb. 21, 2023

New Memory Profiler

by Sebastian Jordan Montano

Hello, I have been working on a new Memory Profiling for profiling object allocations. The profiler has reached a first stable version and I would like to share it with you. [ https://github.com/jordanmontt/illimani-memory-profiler | https://github.com/jordanmontt/illimani-memory-profiler ] The profiler gives some statistics, cool visualizations, like a heat-map, about the allocations and memory usage. If you want to profile the memory of some applications, this tool can help you. Also, if you have some use cases or you have some feedback please let us know because we are looking to improve the tool :) Cheers, Sebastian Jordan

Feb. 21, 2023

This week (7/2023) on the Pharo Issue Tracker

by Marcus Denker

We merged 42 PRs and closed 66 issues Fixes ===== - Unnecessary characters rule should be an information and not a warning #12764 https://github.com/pharo-project/pharo/pull/12764 - FIx #wantsSteps deprecated calls #12782 https://github.com/pharo-project/pharo/pull/12782 - Removing the TStDebuggerExtension trait from the dummy debugger presenter #463 https://github.com/pharo-spec/NewTools/pull/463 Tests ===== - add some Duration tests #12777 https://github.com/pharo-project/pharo/pull/12777 - 11368-Failing-on-CI-random-CoNarrowHistoryFetcherTesttestNarrowingReturnsSameElementsThatCallingDirectly #12768 https://github.com/pharo-project/pharo/pull/12768 - categorization tests should print culprints if any #12780 https://github.com/pharo-project/pharo/pull/12780 Documentation ============= - Missing class comment: BaselineOfBeacon #12640 https://github.com/pharo-project/pharo/pull/12640 - Missing class comment BaselineOfClap and lint issue #12642 https://github.com/pharo-project/pharo/pull/12642 Cleanup ======= - Adjust #initialize categorization cases #12638 https://github.com/pharo-project/pharo/pull/12638 - Remove BlueInk packages #12612 https://github.com/pharo-project/pharo/pull/12612 - use String>>streamContens: and assert:equals: #12786 https://github.com/pharo-project/pharo/pull/12786 - 29 of the kind Cleanup: Condense SUnit packages #12630 https://github.com/pharo-project/pharo/pull/12630

Feb. 17, 2023

Re: ESUG 2023 Call for participation

by Steffen MÃ¤rcker

Hi! Is there a firm submission deadline set yet? Ciao, Steffen stephane ducasse schrieb am Samstag, 11. Februar 2023 18:49:42 (+01:00): > ESUG 2023 Call for Presentations > 28.8.2023 to 01.9.2023 > Lyon France > https://esug.github.io > https://esug.github.io/2023-Conference/conf2023.html > > ESUG is the premium and fun conference around smalltalk technologies. > You can support the ESUG conference in many different ways: > - Sponsor the conference. New sponsoring packages are described at http://www.esug.org/supportesug/becomeasponsor/ > - Submit a talk, a software or a paper to one of the events. See below. > - Attend the conference. We'd like to beat the previous record of attendance (180 people at Koln 2019)! > - Students can get free registration and hosting if they enroll into the the Student Volunteers program. See below. > > ## Developers Forum: International Smalltalk Developers Conference > > We are looking for YOUR experience on using Smalltalk. You will have 30 min for presentations and 45 min for hands-on tutorials. > The list of topics for the normal talks and tutorials includes, but is not limited to the following: > - XP practices, Development tools, Experience reports > - Model driven development, Web development, Team management > - Meta-Modeling, Security, New libraries & frameworks > - Educational material, Embedded systems and robotics > - SOA and Web services, Interaction with other programming languages > - Teaching Pearls and Show us Your Business > > New this year!!! We added two types of sessions in addition to the regular talks and show us your projects sessions. > Show your business 10 min session (Get prepared!!) > Teaching pearls : we want some session on how to teach some design aspects. We want your tip and tricks to teach Smalltalk or OOP. > We expect to have several 10 to 15 min sessions aggregated. > > ### How to submit? > > Make a Pull Request here https://github.com/ESUG/esug.github.io/tree/source/2023-Conference/talks > [Or but only if you are not connected to the worldâ¦ send an email to stephane.ducasse(a)inria.fr] > > Title: [ESUG 2023] Please follow the template below the email will be automatically processed! > Name: > Email: > Abstract: > Bio: > > ## Call for Student Volunteers > Student volunteers help keep the conference running smoothly; in return, they have free accommodations, while still having most of the time to enjoy the conference. > > Pay attention: the places are limited so do not wait till the last minute to apply. > > Conference details: > Send an email to stephane.ducasse at inria.fr and Oleksandr Zaitsev with: > > Title: [ESUG 2023 Student] > name, gender, university/school, country, email address > short description of you and why you are interested in participating > > For which period is accommodation covered? Accommodation is covered from Sunday 27.8.2023 to 01.9.2023 (including nights from Sunday to Monday and from Thursday to Friday). Students will be hosted in student rooms. ESUG additionally covers for the lunches during the week and one dinner. > > Duties include handling registration as people arrive at the conference, filling coffee machines, collecting presentation slides for ESUG right after the presentation is given, being present at an information desk to answer questions, and generally being helpful. Student volunteering makes the conference better, takes a fairly small amount of time and doesn't significantly interfere with enjoying and learning from the conference. Please Note, this role requires discipline and constant attention to all attendees. > > Information about hotel > Student Volunteer rooms are booked at (to be announced). If you are student volunteer, do not book yourself, we have arranged the booking already! > -- Gesendet mit Vivaldi Mail. Laden Sie Vivaldi kostenlos von vivaldi.com herunter.

Feb. 15, 2023