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

This week (52 and 53/2020) on the Issue Tracker

by Marcus Denker

A bit lateâ¦ this is what happened the last two weeks of 2020: Fixes ===== - Fix class variable entanglement issue #8045 https://github.com/pharo-project/pharo/pull/8045 - Change Sorter broken #8154 https://github.com/pharo-project/pharo/pull/8154 - Fixes in the Parser #8148 https://github.com/pharo-project/pharo/pull/8148 - Fix Morphic Shortcut Error handling #8156 https://github.com/pharo-project/pharo/pull/8156 - Fixes #6993 against P9: Incorrect error message on failed parsing of a number with high radix #6995 https://github.com/pharo-project/pharo/pull/6995 - Add `visitSelectorNode:` #8163 https://github.com/pharo-project/pharo/pull/8163 - Fix broken (deprecated) UTF8TextConverter #8177 https://github.com/pharo-project/pharo/pull/8177 Debugger ========= - 8135-When-executing-a-doit-against-a-context-the-class-is-not-correct #8136 https://github.com/pharo-project/pharo/pull/8136 - Do not add DoIts to the cache for now. fixes #7955 #7959 https://github.com/pharo-project/pharo/pull/7959 - Debugger fuel out stack command #8141 https://github.com/pharo-project/pharo/pull/8141 Class Definitions ================= - 8150-Trait-creation-should-use-the-traitBuilder #8151 https://github.com/pharo-project/pharo/pull/8151 - 8145-Cleaning-subclass-users #8149 https://github.com/pharo-project/pharo/pull/8149 - 8181-When-fluid-class-on-two-traitTest-are-failing #8190 https://github.com/pharo-project/pharo/pull/8190 Features ======== - 8120-RPackageOrganizer-and-RPackage-should-report-about-if-a-package-is-a-test-package #8152 https://github.com/pharo-project/pharo/pull/8152 - Switch to pharo-icon-pack v1.0.1-idea11 #8089 https://github.com/pharo-project/pharo/pull/8089 - Add a lint rule for classes to have no "Uncategorized" classes in the package #8033 https://github.com/pharo-project/pharo/pull/8033 Refactorings ============ - Fix issue 4902, remove duplicated method #8147 https://github.com/pharo-project/pharo/pull/8147 - Fix Abstract instance variables issue #8138 https://github.com/pharo-project/pharo/pull/8138 Dead Code ========= - 8158-ContextquickStep-is-unused-and-strange #8159 https://github.com/pharo-project/pharo/pull/8159 - DelayBasicScheduler had debug code left from review #7990 https://github.com/pharo-project/pharo/pull/7990 - remove itemFilterName for the spotter, as it seems to be unusedâ¦ #6700 https://github.com/pharo-project/pharo/pull/6700 Cleanups ======== - 8143-Cleaning-Fluid-Builder #8144 https://github.com/pharo-project/pharo/pull/8144 - Tag uncategorized classes in package Refactoring-Tests-Core #8019 https://github.com/pharo-project/pharo/pull/8019 - RBMethodNode #pragmas is the only instance variable for AST children that has an accessor checking for nil #7979 https://github.com/pharo-project/pharo/pull/7979 - Move business logic from new tools to system-support #7659 https://github.com/pharo-project/pharo/pull/7659 - 8127-FFICalloutAPITestmethod2-sends-non-implemented-call #8139 https://github.com/pharo-project/pharo/pull/8139 - remove unused ivar DelayBasicScheduler #8164 https://github.com/pharo-project/pharo/pull/8164 - Fix testCreationByUnnamed #8165 https://github.com/pharo-project/pharo/pull/8165 - Fix #8196 clean some shadowed variables #8197 https://github.com/pharo-project/pharo/pull/8197 Pharo 8 backports ======= - Fixes #6993 against P8: Incorrect error message on failed parsing of a number with high radix #6994 https://github.com/pharo-project/pharo/pull/6994 - backportIfErrorDo #6154 https://github.com/pharo-project/pharo/pull/6154

Jan. 5, 2021

Progress Report -> Refactoring Project - ( December 28 - 31 )

by EVELYN CUSI LOPEZ

Hello everyone. Last week I did these tasks: - Migrate extract method command to commander2 (as an experiment to review how effort we need to migrate all refactorings). - Fix push up with sharedPools issue. - Start to create extract setUp and tearDown methods. Tasks for this week: - Finish to create extract setUp and tearDown methods. - Fix undo refactoring issue. - Add option to limit classes where we replace senders of method to other method (https://github.com/pharo-project/pharo/issues/8087) - Fix push up issue (https://github.com/pharo-project/pharo/issues/2656) Cheers, Evelyn

Jan. 4, 2021

Headless VM and compositing -- was Re: Re: Can anyone get recent Pharo9 builds to work on Linux?

by Martin McClure

I figured out the compositing problem with the headless VMs on Linux. SDL, by default, requests that the window manager disable compositing. This behavior can be overridden starting with SDL 2.0.8. For more information, see https://github.com/pharo-project/pharo/issues/8220. For anyone else seeing this problem in KDE, there is a workaround. System Settings / Display and Monitor / Compositor contains an item "Allow applications to block compositing." This is on by default. When turned off, Pharo works better. Thanks, -Martin On 12/27/20 9:49 PM, Martin McClure wrote: > Thanks, Esteban > > That method does get me a working Pharo, which I was having trouble > with before (though I *thought* I'd tried exactly that...). > > However, it also somehow disables the compositor on my entire display, > making it very hard to see where one (non-Pharo) window ends and > another begins. > Compositing comes back when I quit Pharo. The old VM doesn't exhibit > this odd side-effect. > > Thanks, > -Martin > > On 12/27/20 12:52 AM, Esteban Lorenzano wrote: >> Hi Martin, >> >> I just did : >> >> wget -O- get.pharo.org/64/90+vmHeadlessLatest | bash >> ./pharo-ui Pharo.image >> >> And I had no problem at all (except a libgit2 version that will be >> fixed soon). >> >> I am using a Manjaro, but I do not see why it should not work on others. >> >> Esteban >> >> On Dec 27 2020, at 12:07 am, Martin McClure <martin(a)hand2mouse.com> >> wrote: >> >> If anyone can get recent (within the last week or so) 64-bit Pharo9 >> images to work on Linux, please let me know how you did that! >> I've tried >> everything I can think of and no luck. >> >> For the purposes of this query, "working'' means that you can open a >> playground, type into the it, then backspace over what you've typed. >> >> If you can do that on Linux, this information would be much >> appreciated: >> >> * What build are you running? >> * What VM are you running and where did you get it? >> * How do you launch it? If from the command-line, what arguments? >> >> Thanks, >> -Martin >> >

Jan. 3, 2021