October 2023 - Pharo-dev - lists.pharo.org

Re: # This week (40/2023) on the Pharo Issue Tracker

by Tim Mackinnon

I don't look in depth every week - but gosh there are always some great items in the list when you do look. Its all the little details the make you smile - removing old usages etc. This is how you fix a big system bit by bit - its very inspirational and a good example for the day jobs as well. Thanks everyone... people do appreciate it. Tim On Fri, 6 Oct 2023, at 1:45 PM, Marcus Denker wrote: > # Fixes > > - Fix intersection of dictionaries #14812 > https://github.com/pharo-project/pharo/pull/14812 > > - Fix announcements during class creation #14816 > https://github.com/pharo-project/pharo/pull/14816 > > - Prevent SystemDictionary key to be something else than symbols #14813 > https://github.com/pharo-project/pharo/pull/14813 > > - Kernel: Fix CompiledMethod>>#propertyAt:ifPresent: #14823 > https://github.com/pharo-project/pharo/pull/14823 > > - Allow defining methods from class pane again #14824 > https://github.com/pharo-project/pharo/pull/14824 > > - 14864-Recompiling-a-method-when-a-tool-looks-at-it-DNU-name-is-nil #14865 > https://github.com/pharo-project/pharo/pull/14865 > > - speedup-runtimeUndeclaredRead #14873 > https://github.com/pharo-project/pharo/pull/14873 > > - Fix Deprecation for methods that use #runtimeUndeclaredRead #14872 > https://github.com/pharo-project/pharo/pull/14872 > > # Features > > - There is #workDatesDo:, but no #workDates #14820 > https://github.com/pharo-project/pharo/pull/14820 > > > # Graphics > > - Factor out methods for allocating and drawing the cache canvas from > HandMorph onto FormCanvas #14890 > https://github.com/pharo-project/pharo/pull/14890 > > - Factor out methods for saving and restoring patches from HandMorph > onto Canvas #14841 > https://github.com/pharo-project/pharo/pull/14841 > > - Remove some unused methods from the Canvas hierarchy #14855 > https://github.com/pharo-project/pharo/pull/14855 > > - Defer change list update to avoid a race condition #14853 > https://github.com/pharo-project/pharo/pull/14853 > > # Package cleanup > > - Remove usage of #category: in trait tests #14877 > https://github.com/pharo-project/pharo/pull/14877 > > - RPackage: Simplify tests and fix bug in package removal #14875 > https://github.com/pharo-project/pharo/pull/14875 > > - RPackage: Introduce UndefinedPackageTag #14876 > https://github.com/pharo-project/pharo/pull/14876 > > - RPackage: Revert #packageName #14825 > https://github.com/pharo-project/pharo/pull/14825 > > - Monticello: Simplify classRemoved: #14857 > https://github.com/pharo-project/pharo/pull/14857 > > - RPackage: remove private import method #14879 > https://github.com/pharo-project/pharo/pull/14879 > > - Change set should not depend on ClassRecategorized #14880 > https://github.com/pharo-project/pharo/pull/14880 > > - RPackage: ClassRepackaged announcement should know the package tags #14881 > https://github.com/pharo-project/pharo/pull/14881 > > - RPackage: New step at cleaning tests #14883 > https://github.com/pharo-project/pharo/pull/14883 > > # Refactoring Engine > > > - Refactor: reusing transformations where possible #14862 > https://github.com/pharo-project/pharo/pull/14862 > > - Refactoring: Get away from class definition #14852 > https://github.com/pharo-project/pharo/pull/14852 > > - Refactoring: Remove controllers #14828 > https://github.com/pharo-project/pharo/pull/14828 > > - fixes #14715: RBNamespace >> classNamed: should convert strings to > symbols #14831 > https://github.com/pharo-project/pharo/pull/14831 > > - [Refactoring engine] 2023 09 26 enh remove instance variable2 #14790 > https://github.com/pharo-project/pharo/pull/14790 > > - Refactoring engine: Cleaning up #14834 > https://github.com/pharo-project/pharo/pull/14834 > > # Documentation > > - Adding a #reflection: pragma on reflective methods #14821 > https://github.com/pharo-project/pharo/pull/14821 > > - Bootstrap: Add logs to early steps of the bootstrap #14861 > https://github.com/pharo-project/pharo/pull/14861 > > # Tools > > - Debugger protocol cleaning #590 > https://github.com/pharo-spec/NewTools/pull/590 > > - Debugger class side cleaning #594 > https://github.com/pharo-spec/NewTools/pull/594 > > - Scrolling to selection when selecting path to the receiver class in > the meta browser (Fix for the meta browser in the inspector) #597 > https://github.com/pharo-spec/NewTools/pull/597 > > - StVersionBrowserPresenter : no need to use #instanceSideParentName > (which is Ring1 specific) #596 > https://github.com/pharo-spec/NewTools/pull/596 > > - fix #testStackTablePackagesLabels: use correct DoIt selector #595 > https://github.com/pharo-spec/NewTools/pull/595 > > - Fix for issue #592 self for number in inspector #593 > https://github.com/pharo-spec/NewTools/pull/593 > > - Removing deprecated debugger command (StShowFullStackCommand) #591 > https://github.com/pharo-spec/NewTools/pull/591 > > > # Cleanup > > > - fix a isForWorkspace: send #1459 > https://github.com/pharo-spec/Spec/pull/1459 > > - Move #isTraitDefinition to Pharo from Tonel #14889 > https://github.com/pharo-project/pharo/pull/14889 > > - 10094-SourceFileArraychangeRecordsFordo-is-Ring1-specific #14866 > https://github.com/pharo-project/pharo/pull/14866 > > - EDDebuggingAPI: use #changeRecordsFor: #14870 > https://github.com/pharo-project/pharo/pull/14870 > > - Ring-Cleanup-isMetaSide #14856 > https://github.com/pharo-project/pharo/pull/14856 > > - 10-02-Deprecation-Cleanup #14847 > https://github.com/pharo-project/pharo/pull/14847 > > - Refactor message send: subclass of Message #14829 > https://github.com/pharo-project/pharo/pull/14829 > > - Refactor Pragma: subclass of Message #14835 > https://github.com/pharo-project/pharo/pull/14835 > > - Reflectivity cleaning and comments #14892 > https://github.com/pharo-project/pharo/pull/14892

Oct. 6, 2023

# This week (40/2023) on the Pharo Issue Tracker

by Marcus Denker

# Fixes - Fix intersection of dictionaries #14812 https://github.com/pharo-project/pharo/pull/14812 - Fix announcements during class creation #14816 https://github.com/pharo-project/pharo/pull/14816 - Prevent SystemDictionary key to be something else than symbols #14813 https://github.com/pharo-project/pharo/pull/14813 - Kernel: Fix CompiledMethod>>#propertyAt:ifPresent: #14823 https://github.com/pharo-project/pharo/pull/14823 - Allow defining methods from class pane again #14824 https://github.com/pharo-project/pharo/pull/14824 - 14864-Recompiling-a-method-when-a-tool-looks-at-it-DNU-name-is-nil #14865 https://github.com/pharo-project/pharo/pull/14865 - speedup-runtimeUndeclaredRead #14873 https://github.com/pharo-project/pharo/pull/14873 - Fix Deprecation for methods that use #runtimeUndeclaredRead #14872 https://github.com/pharo-project/pharo/pull/14872 # Features - There is #workDatesDo:, but no #workDates #14820 https://github.com/pharo-project/pharo/pull/14820 # Graphics - Factor out methods for allocating and drawing the cache canvas from HandMorph onto FormCanvas #14890 https://github.com/pharo-project/pharo/pull/14890 - Factor out methods for saving and restoring patches from HandMorph onto Canvas #14841 https://github.com/pharo-project/pharo/pull/14841 - Remove some unused methods from the Canvas hierarchy #14855 https://github.com/pharo-project/pharo/pull/14855 - Defer change list update to avoid a race condition #14853 https://github.com/pharo-project/pharo/pull/14853 # Package cleanup - Remove usage of #category: in trait tests #14877 https://github.com/pharo-project/pharo/pull/14877 - RPackage: Simplify tests and fix bug in package removal #14875 https://github.com/pharo-project/pharo/pull/14875 - RPackage: Introduce UndefinedPackageTag #14876 https://github.com/pharo-project/pharo/pull/14876 - RPackage: Revert #packageName #14825 https://github.com/pharo-project/pharo/pull/14825 - Monticello: Simplify classRemoved: #14857 https://github.com/pharo-project/pharo/pull/14857 - RPackage: remove private import method #14879 https://github.com/pharo-project/pharo/pull/14879 - Change set should not depend on ClassRecategorized #14880 https://github.com/pharo-project/pharo/pull/14880 - RPackage: ClassRepackaged announcement should know the package tags #14881 https://github.com/pharo-project/pharo/pull/14881 - RPackage: New step at cleaning tests #14883 https://github.com/pharo-project/pharo/pull/14883 # Refactoring Engine - Refactor: reusing transformations where possible #14862 https://github.com/pharo-project/pharo/pull/14862 - Refactoring: Get away from class definition #14852 https://github.com/pharo-project/pharo/pull/14852 - Refactoring: Remove controllers #14828 https://github.com/pharo-project/pharo/pull/14828 - fixes #14715: RBNamespace >> classNamed: should convert strings to symbols #14831 https://github.com/pharo-project/pharo/pull/14831 - [Refactoring engine] 2023 09 26 enh remove instance variable2 #14790 https://github.com/pharo-project/pharo/pull/14790 - Refactoring engine: Cleaning up #14834 https://github.com/pharo-project/pharo/pull/14834 # Documentation - Adding a #reflection: pragma on reflective methods #14821 https://github.com/pharo-project/pharo/pull/14821 - Bootstrap: Add logs to early steps of the bootstrap #14861 https://github.com/pharo-project/pharo/pull/14861 # Tools - Debugger protocol cleaning #590 https://github.com/pharo-spec/NewTools/pull/590 - Debugger class side cleaning #594 https://github.com/pharo-spec/NewTools/pull/594 - Scrolling to selection when selecting path to the receiver class in the meta browser (Fix for the meta browser in the inspector) #597 https://github.com/pharo-spec/NewTools/pull/597 - StVersionBrowserPresenter : no need to use #instanceSideParentName (which is Ring1 specific) #596 https://github.com/pharo-spec/NewTools/pull/596 - fix #testStackTablePackagesLabels: use correct DoIt selector #595 https://github.com/pharo-spec/NewTools/pull/595 - Fix for issue #592 self for number in inspector #593 https://github.com/pharo-spec/NewTools/pull/593 - Removing deprecated debugger command (StShowFullStackCommand) #591 https://github.com/pharo-spec/NewTools/pull/591 # Cleanup - fix a isForWorkspace: send #1459 https://github.com/pharo-spec/Spec/pull/1459 - Move #isTraitDefinition to Pharo from Tonel #14889 https://github.com/pharo-project/pharo/pull/14889 - 10094-SourceFileArraychangeRecordsFordo-is-Ring1-specific #14866 https://github.com/pharo-project/pharo/pull/14866 - EDDebuggingAPI: use #changeRecordsFor: #14870 https://github.com/pharo-project/pharo/pull/14870 - Ring-Cleanup-isMetaSide #14856 https://github.com/pharo-project/pharo/pull/14856 - 10-02-Deprecation-Cleanup #14847 https://github.com/pharo-project/pharo/pull/14847 - Refactor message send: subclass of Message #14829 https://github.com/pharo-project/pharo/pull/14829 - Refactor Pragma: subclass of Message #14835 https://github.com/pharo-project/pharo/pull/14835 - Reflectivity cleaning and comments #14892 https://github.com/pharo-project/pharo/pull/14892

Oct. 6, 2023

Re: [Issue tracker] Please check your issues on the issue tracker

by Marcus Denker

Thanks, this is useful ! We reduced the open issue by ~25 yesterday, not bad. > On 6 Oct 2023, at 03:28, Daniel Slomovits <daniels220(a)gmail.com> wrote: > > I would add, you can refer to yourself as @me in the search field, so the following link is the same for everyone: > > https://github.com/pharo-project/pharo/issues/created_by/@me > > You can also combine open issues and open/unmerged PRs into a single search by deleting is:issue from the query, resulting in: > > https://github.com/pharo-project/pharo/issues?q=is%3Aopen+author%3A%40me > > On Thu, Oct 5, 2023 at 10:49â¯AM Noury Bouraqadi <bouraqadi(a)gmail.com <mailto:bouraqadi@gmail.com>> wrote: >> Did a pass. Thank you for the reminder Marcus. >> >> Noury >> On Oct 5 2023, at 2:16 pm, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >> Hi, >> >> Please check the issue tracker. >> >> Often when a bug is fixed, you might even think âYES! the bug I reported is now fixedâ and you naturally assume that your issue therefore was closed. >> >> But that is not always the case. >> - people forgot to link PRs to the issues >> - gitub in the past just did not close the issue even if it was linked (seems to work better now) >> - There might be *another* issue that was closed (your issue was a not detected duplicate) >> - The issue was closed due to other reasons >> - Code changed and it is not relevant anymore >> >> >> So please please, check your old issues ! >> >> https://github.com/pharo-project/pharo/issues >> >> >> You can easily search for he ones that you added, for me this would be: >> >> https://github.com/pharo-project/pharo/issues/created_by/MarcusDenker

Oct. 6, 2023

Re: [Issue tracker] Please check your issues on the issue tracker

by Daniel Slomovits

I would add, you can refer to yourself as @me in the search field, so the following link is the same for everyone: https://github.com/pharo-project/pharo/issues/created_by/@me You can also combine open issues and open/unmerged PRs into a single search by deleting is:issue from the query, resulting in: https://github.com/pharo-project/pharo/issues?q=is%3Aopen+author%3A%40me On Thu, Oct 5, 2023 at 10:49â¯AM Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: > Did a pass. Thank you for the reminder Marcus. > > Noury > On Oct 5 2023, at 2:16 pm, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > Please check the issue tracker. > > Often when a bug is fixed, you might even think âYES! the bug I reported > is now fixedâ and you naturally assume that your issue therefore was closed. > > But that is not always the case. > - people forgot to link PRs to the issues > - gitub in the past just did not close the issue even if it was linked > (seems to work better now) > - There might be *another* issue that was closed (your issue was a not > detected duplicate) > - The issue was closed due to other reasons > - Code changed and it is not relevant anymore > > > So please please, check your old issues ! > > https://github.com/pharo-project/pharo/issues > > > You can easily search for he ones that you added, for me this would be: > > https://github.com/pharo-project/pharo/issues/created_by/MarcusDenker > >

Oct. 6, 2023

Re: [Issue tracker] Please check your issues on the issue tracker

by Noury Bouraqadi

Did a pass. Thank you for the reminder Marcus. Noury On Oct 5 2023, at 2:16 pm, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > Please check the issue tracker. > > Often when a bug is fixed, you might even think âYES! the bug I reported is now fixedâ and you naturally assume that your issue therefore was closed. > > But that is not always the case. > - people forgot to link PRs to the issues > - gitub in the past just did not close the issue even if it was linked (seems to work better now) > - There might be *another* issue that was closed (your issue was a not detected duplicate) > - The issue was closed due to other reasons > - Code changed and it is not relevant anymore > > > So please please, check your old issues ! > > https://github.com/pharo-project/pharo/issues > > > You can easily search for he ones that you added, for me this would be: > > https://github.com/pharo-project/pharo/issues/created_by/MarcusDenker

Oct. 5, 2023

[Issue tracker] Please check your issues on the issue tracker

by Marcus Denker

Hi, Please check the issue tracker. Often when a bug is fixed, you might even think âYES! the bug I reported is now fixedâ and you naturally assume that your issue therefore was closed. But that is not always the case. - people forgot to link PRs to the issues - gitub in the past just did not close the issue even if it was linked (seems to work better now) - There might be *another* issue that was closed (your issue was a not detected duplicate) - The issue was closed due to other reasons - Code changed and it is not relevant anymore So please please, check your old issues ! https://github.com/pharo-project/pharo/issues You can easily search for he ones that you added, for me this would be: https://github.com/pharo-project/pharo/issues/created_by/MarcusDenker

Oct. 5, 2023

Re: Sockets not working under heavy VM load?

by Pavel Krivanek

Hi Sven, it seems to be fixed, thank you for your attention. Cheers, -- Pavel Ät 28. 9. 2023 v 16:36 odesÃlatel Sven Van Caekenberghe <sven(a)stfx.eu> napsal: > I know this is very old, but is this still an issue today ? > > > On 29 Dec 2021, at 12:30, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: > > > > Hi, > > > > we have some performance issues with Glorp over P3 and, after some > investigation, I have a theory that could explain it. And I would like to > know your opinion if it is correct. > > > > To reproduce this issue, you can try something easy. Just create a > process with normal or higher priority that will try to read something from > a socket. And, in parallel, do in a separate thread an operation that takes > all the processor time for several seconds. > > > > ```` > > [ > > 5 seconds wait. > > Time now traceCr. > > ZnClient new > > url: 'https://www.google.com'; > > get. > > Time now traceCr. > > ] forkAt: 60. > > > > [1000 timesRepeat: [ 10000 factorial ] ] timeToRun > > ```` > > (you may try a different safe server address) > > > > The processes run in parallel until the time when the first process > tries to obtain data from the socket. Then it hangs and waits until > finishing of the second process. > > > > My theory is that the VM socket plugin is able to receive incoming data > from the connection and save it into the buffer. In the meantime, the > reading process is waiting on the socket semaphore. But it looks like the > plugin is not able to release the semaphore while the VM is actually doing > something. It needs to wait until the VM has nothing useful to do, and then > it is finally able to release the semaphores so Pharo processes are resumed > and can start to read. > > > > Is my theory right? > > > > Cheers, > > -- Pavel > > > > > > >

Oct. 3, 2023