February 2022 - Pharo-dev - lists.pharo.org

Re: Problem with Pharo 10 in GitHub Action CI using SmalltalkCI

by Sven Van Caekenberghe

Yes, could be. I just triggered a manual CI build for Zinc HTTP Components and it now also fails, while it succeeded yesterday (there were no code changes). So there definitely is a problem. Anyone else seeing problems CI building their projects for Pharo 10 ? > On 22 Feb 2022, at 11:16, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 22 Feb 2022, at 11:03, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Hi, >> >> I just tried to enable Pharo64-10 (not Pharo64-10.0 but that is probably another issue) in a GitHub Action CI using SmalltalkCI. >> >> https://github.com/svenvc/ston/blob/master/.github/workflows/CI.yml >> https://github.com/svenvc/ston/runs/5286121566?check_suite_focus=true >> >> This fails with >> >> NotFound: [ :cl | cl isPlatformCompatible ] not found in OrderedCollection >> OrderedCollection(Collection)>>errorNotFound: >> [self errorNotFound: aBlock] in OrderedCollection(Collection)>>detect: in Block: [self errorNotFound: aBlock] >> OrderedCollection(Collection)>>detect:ifFound:ifNone: >> OrderedCollection(Collection)>>detect:ifNone: >> OrderedCollection(Collection)>>detect: >> SmalltalkCI class>>platformClass >> ... >> >> Does anyone have any idea ? >> I seem to remember there were some issue with Metacello attributes, but maybe that is not related. >> > > maybe isPlatformCompatible checks the attributes? These where updated to be pharo10, not pharo9: > > New try at removing Pharo 9 metacello attributes #10819 > https://github.com/pharo-project/pharo/pull/10819 > > > Marcus

Feb. 22, 2022

Re: Problem with Pharo 10 in GitHub Action CI using SmalltalkCI

by Marcus Denker

> On 22 Feb 2022, at 11:03, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > I just tried to enable Pharo64-10 (not Pharo64-10.0 but that is probably another issue) in a GitHub Action CI using SmalltalkCI. > > https://github.com/svenvc/ston/blob/master/.github/workflows/CI.yml > https://github.com/svenvc/ston/runs/5286121566?check_suite_focus=true > > This fails with > > NotFound: [ :cl | cl isPlatformCompatible ] not found in OrderedCollection > OrderedCollection(Collection)>>errorNotFound: > [self errorNotFound: aBlock] in OrderedCollection(Collection)>>detect: in Block: [self errorNotFound: aBlock] > OrderedCollection(Collection)>>detect:ifFound:ifNone: > OrderedCollection(Collection)>>detect:ifNone: > OrderedCollection(Collection)>>detect: > SmalltalkCI class>>platformClass > ... > > Does anyone have any idea ? > I seem to remember there were some issue with Metacello attributes, but maybe that is not related. > maybe isPlatformCompatible checks the attributes? These where updated to be pharo10, not pharo9: New try at removing Pharo 9 metacello attributes #10819 https://github.com/pharo-project/pharo/pull/10819 Marcus

Feb. 22, 2022

Problem with Pharo 10 in GitHub Action CI using SmalltalkCI

by Sven Van Caekenberghe

Hi, I just tried to enable Pharo64-10 (not Pharo64-10.0 but that is probably another issue) in a GitHub Action CI using SmalltalkCI. https://github.com/svenvc/ston/blob/master/.github/workflows/CI.yml https://github.com/svenvc/ston/runs/5286121566?check_suite_focus=true This fails with NotFound: [ :cl | cl isPlatformCompatible ] not found in OrderedCollection OrderedCollection(Collection)>>errorNotFound: [self errorNotFound: aBlock] in OrderedCollection(Collection)>>detect: in Block: [self errorNotFound: aBlock] OrderedCollection(Collection)>>detect:ifFound:ifNone: OrderedCollection(Collection)>>detect:ifNone: OrderedCollection(Collection)>>detect: SmalltalkCI class>>platformClass ... Does anyone have any idea ? I seem to remember there were some issue with Metacello attributes, but maybe that is not related. Sven PS: I could try with other repositories but that will probably give the same result. Only Zinc does run with Pharo 10, last build a day ago. I can't spot the difference.

Feb. 22, 2022

Fwd: ESUG 2022 call for presentations And Call for student volunteers

by stephane ducasse

A reminderâ¦ S > Begin forwarded message: > > From: "stephane.ducasse(a)free.fr" <stephane.ducasse(a)free.fr> > Subject: ESUG 2022 call for presentations And Call for student volunteers > Date: 13 January 2022 at 13:23:44 CET > > ESUG 2022 > Serbia 22. â 26.8. > > 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/ <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 (170 people at Amsterdam 2008)! > 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/2022-Conference/talks > > Or but only if you are not connected to the worldâ¦ send an email to stephane.ducasse(a)inria.fr > > Title: [ESUG 2022] 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 serge.stinckwich at gmail.com with: > > title: [ESUG 2022 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 21 August until Friday 26 August 2022 (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! >

Feb. 20, 2022

This week (07/2022) on the Pharo Issue Tracker

by Marcus Denker

We merged 14 PRs and closed 17 issue tracker entries. If you want to help, there are pull requests that need to be reviewed https://github.com/pharo-project/pharo/pulls Fixes ===== - 10889-equal-CompiledBlocks-in-the-literal-frame-stored-only-once #10891 https://github.com/pharo-project/pharo/pull/10891 - 9963-MCStReadertypeOfSubclass-hard-codes-mcType-and-subclassDefiningSymbol #10875 https://github.com/pharo-project/pharo/pull/10875 - 0854-Cmd-t-stopped-working #10870 https://github.com/pharo-project/pharo/pull/10870 Cleanups ======== - 5090-SystemSettingLauncher-should-be-moved-to-System-Settings-Browser #10878 https://github.com/pharo-project/pharo/pull/10878 - Just less newHorizontal #10886 https://github.com/pharo-project/pharo/pull/10886 - Integrate Roassal3 v0.9.9f #10884 https://github.com/pharo-project/pharo/pull/10884 - 5x Cleanup newlines and blanks in packages e.g. https://github.com/pharo-project/pharo/pull/10896 Documentation / Tests ===================== - just adding two little tests for fraction accessing. #10885 https://github.com/pharo-project/pharo/pull/10885

Feb. 18, 2022

Re: [Issue tracker] Please check your older issues

by Marcus Denker

Thanks to everyone who helped digging through the old issues! We managed to close over 140 issue in 2022 already, with just 801 issues open (and >3500 issues closed overall since we moved to this issue tracker). Often it feels a bit useless âjust one issue downâ¦ what difference does that make?â. But you can only close 3500 issues by looking at each of them, one after the other... Marcus > On 7 Feb 2022, at 11:56, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > We are seeing lots of issue that are still open, but already fixed or just not valid anymore. > e.g. > > - the fix that was merged but the issue was not closed (sometimes GitHub has problems doing that) > - Bug was fixed independent of the issue > - The issue is just not relevant anymore > > > It is often quite time consuming to even find out that an issue is already fixedâ¦ > > It would be nice if everyone could check the issues that > > - you submitted yourself > - that are assigned to you > - [Bonus] where you were part of some discussion > > > https://github.com/pharo-project/pharo/issues > > > Marcus

Feb. 15, 2022

This week (06/2022) on the Pharo Issue Tracker

by Marcus Denker

We merged 13 PRs and closed 33 Issue tracker entries. More information at https://github.com/pharo-project/pharo/pulse Fixes ===== Fix some spec deprecations #10855 https://github.com/pharo-project/pharo/pull/10855 9777-SystemNavigation-default-allUnimplementedCalls-size---DNU #10835 https://github.com/pharo-project/pharo/pull/10835 5879-Printing-an-exception-should-not-rely-on-the-AST #10863 https://github.com/pharo-project/pharo/pull/10863 Bugfix in RBSelectorEnvironment #10868 https://github.com/pharo-project/pharo/pull/10868 Cleanup ======= remove Deprecated90 package #10877 https://github.com/pharo-project/pharo/pull/10877 3234-CDNode-got-polluted-with-extension-methods-that-are-on-reflectivity-for-nodes #10853 https://github.com/pharo-project/pharo/pull/10853 10847-Deprecate-canBeGlobalVarInitial-and-canBeNonGlobalVarInitial #10848 https://github.com/pharo-project/pharo/pull/10848 10864-deprecate-unused-class-ProtocolRemovalException #10865 https://github.com/pharo-project/pharo/pull/10865 Deprecate KMCategoryTarget #10876 https://github.com/pharo-project/pharo/pull/10876 cleanup: rewrite users of unicodeToMacRoman to use Zn encoders #10873 https://github.com/pharo-project/pharo/pull/10873 cleanup: rewrite users of leadingChar #10874 https://github.com/pharo-project/pharo/pull/10874 testNoUncategorizedMethods-lowerbound #10866 https://github.com/pharo-project/pharo/pull/10866 Cleanup-CDAbstractClassDefinitionParser #10852 https://github.com/pharo-project/pharo/pull/10852

Feb. 10, 2022

Pharo GSoC 2022 call for projects

by Sebastian Jordan Montano

Hello to all, We, as Pharo organization, are appliying to the Google Summer of Code (GSoC) 2022 version. More info in: https://summerofcode.withgoogle.com/ >From GSoC Page: "Google Summer of Code is a global, online program focused on bringing new contributors into open source software development. GSoC Contributors work with an open source organization on a 12+ week programming project under the guidance of mentors." Now we are preparing to postulate. We would like to have the most projects as possible. Like that, we will contribute to Pharo and to Open Source in general. If you have any project and you are willing to be a mentor please send us your proposal! We would be happy to work with you. Yours sincerely, Sebastian Jordan GSoC Program Organizer from Pharo Consortium

Feb. 8, 2022

[Issue tracker] Please check your older issues

by Marcus Denker

Hi, We are seeing lots of issue that are still open, but already fixed or just not valid anymore. e.g. - the fix that was merged but the issue was not closed (sometimes GitHub has problems doing that) - Bug was fixed independent of the issue - The issue is just not relevant anymore It is often quite time consuming to even find out that an issue is already fixedâ¦ It would be nice if everyone could check the issues that - you submitted yourself - that are assigned to you - [Bonus] where you were part of some discussion https://github.com/pharo-project/pharo/issues Marcus

Feb. 7, 2022

This week (05/2022) on the Pharo Issue Tracker

by Marcus Denker

We merged 15 PRs and closed 31 Issues. Fixes ===== - Increasing minimum size for Calypso browser #10838 https://github.com/pharo-project/pharo/pull/10838 - Add back beautifulcomments #10832 https://github.com/pharo-project/pharo/pull/10832 - 10800-Broken-FT2-library-setting #10851 https://github.com/pharo-project/pharo/pull/10851 Breakpoint interaction ====================== - Breakpoint position from cursor #10812 https://github.com/pharo-project/pharo/pull/10812 - Inserting variable breakpoint when the selected node is variable https://github.com/pharo-project/pharo/pull/10841 Cleanup ======= - Remove Class>>isAbstract as it actually call the super class method #10825 https://github.com/pharo-project/pharo/pull/10825 - Remove Spec1 Critic Browser #10816 https://github.com/pharo-project/pharo/pull/10816 - Remove Spec1 #10818 https://github.com/pharo-project/pharo/pull/10818 - Cleanup-unsent-Deprecated90 #10833 https://github.com/pharo-project/pharo/pull/10833 - fix-users-canBeGlobalVarInitial #10820 https://github.com/pharo-project/pharo/pull/10820 - Cleanup : remove Class>>isValidTraitName. No more sender of it in theâ¦ #10826 https://github.com/pharo-project/pharo/pull/10826 - Replace Moose algos graphs by AI graphs algorithms #10839 https://github.com/pharo-project/pharo/pull/10839 - Integrate Roassal3 v0.9.9e #10846 https://github.com/pharo-project/pharo/pull/10846 Comments ======== - 10214 improving comments and adding tests to tree searcher #10636 https://github.com/pharo-project/pharo/pull/10636 - 10214 improving comments and adding tests to tree searcher #10817 https://github.com/pharo-project/pharo/pull/10817

Feb. 4, 2022