- Pharo-users - lists.pharo.org

Re: Pharo in Docker.

by Guillermo Polito

Hi @Philippe, this is too few info to help, but maybe you can try the following: - are you sure the image inside the container and outside are the same version? => what if you use the same version outside the docker file? - the issue happens because of a deprecation exception, what if you disable them through the settings (there is a programmatic way to do it)? G > El 1 jul. 2023, a las 09:28, pvdh(a)pt.lu escribiÃ³: > > Hello, > > I am trying to run TinyBlog and Pharo in a Docker container. It run, but it crashes after a while with the following log: > > pva@dd8:~/docker/PharoTinyBlogDocker$ docker logs --tail 1000 b5172118c19f > ZnZincServerAdaptor > DeprecationPerformedNotification: Automatic deprecation code rewrite: The method MAContainerComponent>>#isReadonly called from TBSMagritteFormRenderer>>#renderElement: has been deprecated. Use #isReadOnly instead. > DeprecationPerformedNotification: Automatic deprecation code rewrite: The method MADescriptionComponent>>#isReadonly called from TBSMagritteCheckboxComponent>>#renderEditorOn: has been deprecated. Use #isReadOnly instead. > SmalltalkImageInstanceID class>>startUpSyntax Error on line 1: 'Variable or expression expected' > ========================================================= > 1: `@receiver readonly: > _^_ > SmalltalkImageInstanceID class>>startUpSyntax Error on line 1: 'Variable or expression expected' > ========================================================= > 1: `@receiver readonly: > _^_ > ZnZincServerAdaptor > I have tried to fix the problem in a regular image and it does not behave the same. > > Is there a way to debug graphically the Pharo located in the docker file ? I did not find any resources on the net concerning this kind of configuration. > > Thanks in advance for your help, > > Philippe Vanderheyden > > > > > > > -- > Cordialement, > Philippe > > Philippe Vanderheyden > Rue Maria Teresa, 15 > L-8448 Steinfort > T: 77 07 66 > G: 621 365 901 > <pvdh.vcf>

Aug. 9, 2023

This week (29-31/2023) on the Pharo Issue Tracker

by Marcus Denker

# This week (29-31/2023) on the Pharo Issue Tracker This is one log for three weeks (29-31) # Pharo 11 - backport Pharo11: Fix doubleClick on tab and on text selection. #14287 https://github.com/pharo-project/pharo/pull/14287 - Backport fixed tests #14409 https://github.com/pharo-project/pharo/pull/14409 - Backport fix GitHub rate limit #14411 https://github.com/pharo-project/pharo/pull/14411 - Backport display scale factor improvements to Pharo 11 #14351 https://github.com/pharo-project/pharo/pull/14351 - Backport scale 2.0 icons support to Pharo 11 #14352 https://github.com/pharo-project/pharo/pull/14352 # Features - Added coverage highlighting in DrTest #14379 https://github.com/pharo-project/pharo/pull/14379 - Push tag API in the class builder #14394 https://github.com/pharo-project/pharo/pull/14394 # Fixes - Changed finder behavior to not depend on copies #14163 https://github.com/pharo-project/pharo/pull/14163 - rapid click on two different items in a list gets interpreted as a double-click on the first item #14346 https://github.com/pharo-project/pharo/pull/14346 - Hermes: HEMethod needs to handle Protocol now instead of String #14386 https://github.com/pharo-project/pharo/pull/14386 - Fix bug of method returning a text as source code #14375 https://github.com/pharo-project/pharo/pull/14375 - Iterate over a copy of the actionMap in Object>>removeActionsSatisfying: (fixes #14317) #14325 https://github.com/pharo-project/pharo/pull/14325 - Class are created with the wrong environment #14329 https://github.com/pharo-project/pharo/pull/14329 - Ensure copied references in filesystem are resolved before copy #14341 https://github.com/pharo-project/pharo/pull/14341 - safer UUID comparison #14344 https://github.com/pharo-project/pharo/pull/14344 - safer morph access in NECMenuMorph>>#mouseDown: #14356 https://github.com/pharo-project/pharo/pull/14356 - [P12] Traits has to install method when is generated code #14156 https://github.com/pharo-project/pharo/pull/14156 - Replaced the random generator from Pharo. #14230 https://github.com/pharo-project/pharo/pull/14230 - Enhance roassal with version v1.02 #14373 https://github.com/pharo-project/pharo/pull/14373 - optionInlineNone suppresses #optionInlineX at CompilationContext level (fixes #14323) #14397 https://github.com/pharo-project/pharo/pull/14397 # RPackage Cleanup - Reduce usage of RPackage organizer #14370 https://github.com/pharo-project/pharo/pull/14370 - Do not rename category through announcements #14332 https://github.com/pharo-project/pharo/pull/14332 - Improve CompiledMethod>>#isExtension #14295 https://github.com/pharo-project/pharo/pull/14295 - Remove brittle method in RPackage #14292 https://github.com/pharo-project/pharo/pull/14292 - Use better package API in Monticello #14306 https://github.com/pharo-project/pharo/pull/14306 - Update package API of slot tests #14311 https://github.com/pharo-project/pharo/pull/14311 - Improve package cleaning API #14312 https://github.com/pharo-project/pharo/pull/14312 - Do not use deprecated API to create the default package #14316 https://github.com/pharo-project/pharo/pull/14316 - Improve package API used by Calypso #14321 https://github.com/pharo-project/pharo/pull/14321 - Make sure packages created with protocols are announced #14320 https://github.com/pharo-project/pharo/pull/14320 - Improve coherence of RPackage tests #14333 https://github.com/pharo-project/pharo/pull/14333 - Deprecate ensureExistAndRegisterPackageNamed: #14337 https://github.com/pharo-project/pharo/pull/14337 - SImplify class addition in RPackage #14347 https://github.com/pharo-project/pharo/pull/14347 - Deprectaed #definedClassesDo: #14350 https://github.com/pharo-project/pharo/pull/14350/files - Simplify class removal in packages #14359 https://github.com/pharo-project/pharo/pull/14359 - Simplify some classes management in RPackage #14358 https://github.com/pharo-project/pharo/pull/14358 - Do not remove classes from packages using the name #14363 https://github.com/pharo-project/pharo/pull/14363 - Clean method removal of RPackage #14360 https://github.com/pharo-project/pharo/pull/14360 - Forbid to have an extension method in the package owning the class #14354 https://github.com/pharo-project/pharo/pull/14354 - Speed up in package management #14366 https://github.com/pharo-project/pharo/pull/14366 - Do not remove classes through announcement #14388 https://github.com/pharo-project/pharo/pull/14388 - Simplify API of RPackage #14377 https://github.com/pharo-project/pharo/pull/14377 - Do not use global environment in RPackage #14368 https://github.com/pharo-project/pharo/pull/14368 - Simplify class addition assuming classes are created empty #14364 https://github.com/pharo-project/pharo/pull/14364 - Fix remaining announcement subscribtion #14405 https://github.com/pharo-project/pharo/pull/14405 - Package: React to class renaming without announcement #14407 https://github.com/pharo-project/pharo/pull/14407 - Use real classes in #classDefinedSelectors #14410 https://github.com/pharo-project/pharo/pull/14410 - RPackage:â¯Save package defined selectors with class instance #14416 https://github.com/pharo-project/pharo/pull/14416 - Use PackageTagAdded instead of CategoryAdded #14424 https://github.com/pharo-project/pharo/pull/14424 - Package: Remove methods without announcement #14420 https://github.com/pharo-project/pharo/pull/14420 - Package: Save extension selectors under real classes #14419 https://github.com/pharo-project/pharo/pull/14419 - RPackageTag should store real classes #14434 https://github.com/pharo-project/pharo/pull/14434 - RPackage: Factorize import code #14436 https://github.com/pharo-project/pharo/pull/14436 - RPackage: Simplify some code in RPackageOrganizer #14437 https://github.com/pharo-project/pharo/pull/14437 - RPackage: Improve creation of package during demotion to tag #14440 https://github.com/pharo-project/pharo/pull/14440 # Categories / Protocols - Fix bug with reset protocol of Calypso #14376 https://github.com/pharo-project/pharo/pull/14376 - Remove usage of categories in Fuel #14315 https://github.com/pharo-project/pharo/pull/14315 - Do not remove categories through announcements #14307 https://github.com/pharo-project/pharo/pull/14307 - Adapt check in RBAddMethodChange>>protocols: now that the argument may be a first-class Protocol (fixes #14324) #14327 https://github.com/pharo-project/pharo/pull/14327 - Use "protocol" vocabulary in MCTestCase #14322 https://github.com/pharo-project/pharo/pull/14322 - TestRunner should not rely on category announcements #14430 https://github.com/pharo-project/pharo/pull/14430 - Deprecate CategoryRemoved and CategoryRenamed #14438 https://github.com/pharo-project/pharo/pull/14438 # Epicea Souce Logging - Epicea:â¯Migrate category addition and removal to package tag API #14427 https://github.com/pharo-project/pharo/pull/14427 - Disable Epicea in tests #14017 https://github.com/pharo-project/pharo/pull/14017 - Introduce Class>>packageName and simplify Epicea #14408 https://github.com/pharo-project/pharo/pull/14408 - Epicea: Finish refactoring about packages and tags in Epicea #14428 https://github.com/pharo-project/pharo/pull/14428 # Refactoring Engine - Rename generateCompositeChangesFor: to generateChangesFor: #14304 https://github.com/pharo-project/pharo/pull/14304 - Cleanup transformation/refactoring hierarchy #14349 https://github.com/pharo-project/pharo/pull/14349 - Removing the use options in transformation. All test green #14382 https://github.com/pharo-project/pharo/pull/14382 - Enh/extract method transformation #14396 https://github.com/pharo-project/pharo/pull/14396 - Fixing shared variable remove #14402 https://github.com/pharo-project/pharo/pull/14402 - Fix RBCondition test #14413 https://github.com/pharo-project/pharo/pull/14413 - fixing deprecancies introduced by miss refactoring #14412 https://github.com/pharo-project/pharo/pull/14412 - Refactor: unify refactoring and transformation execution api #14374 https://github.com/pharo-project/pharo/pull/14374 - [Refactor] unified refactoring/transformation execution API #14432 https://github.com/pharo-project/pharo/pull/14432 # Tests - Improve flacky test #14425 https://github.com/pharo-project/pharo/pull/14425 - Remove the need of ClassFactoryWithOrganization #14393 https://github.com/pharo-project/pharo/pull/14393 - Make ClassFactoryForTestCase follow changes on class definition #14398 https://github.com/pharo-project/pharo/pull/14398 - Fix fuel tests #14392 https://github.com/pharo-project/pharo/pull/14392 # Simplifications - Improve ClassDescription API of package tags #14342 https://github.com/pharo-project/pharo/pull/14342 - Simplify class builder environment management #14330 https://github.com/pharo-project/pharo/pull/14330 - Use ClassFactoryForTestCase instead of FLClassFactoryForTestCase #14404 https://github.com/pharo-project/pharo/pull/14404 # Cleanups - remove rootsOfTheWorld that was buggy and unused. #14442 https://github.com/pharo-project/pharo/pull/14442 - Small cleanups in Announcement package #14297 https://github.com/pharo-project/pharo/pull/14297 - Replace 'controling' protocol with 'controlling' #14313 https://github.com/pharo-project/pharo/pull/14313 - Fix protocols of methods in extension of their own package #14357 https://github.com/pharo-project/pharo/pull/14357 - Remove unused parameter #14389 https://github.com/pharo-project/pharo/pull/14389 # Documentation - Update regex doc #14328 https://github.com/pharo-project/pharo/pull/14328 - Fix regex doc #14331 https://github.com/pharo-project/pharo/pull/14331

Aug. 7, 2023

Re: How to run a Pharo 8 image on an Apple Silicon (ARM64)?

by varvello＠yahoo.com

Guillermo Polito wrote: > Pharo8 is pretty old :) Hi Gulliermo, Have you any stats on what are the most used Pharo version? > The best I can propose is that you try compiling the VM without the JIT compiler. > That will not give you optimum performances, but acceptable ones compared to Rosetta. > > Iâd suggest you try to compile using the branch pharo-9. Thatâs probably the oldest branch that is easy to build using cmake. > > If the pharo-9 branch does not work for your image, then maybe you should check the branches (see the branches v8.x.x). > > For installation/build instructions, please follow the readme instructions. If you find any issues, tell us, maybe there are cheap workarounds or fixes :). Thank you for your hints. I try to move the codebase to Pharo9, if it is too cumbersome then I try to compile the VM without JIT. Cheers Davide > Hope that helps, > Guille > > > El 6 ago. 2023, a las 22:07, stephane ducasse [stephane.ducasse@inria.fr](mailto:stephane.ducasse@inria.fr) escribiÃ³: > > > > > On 4 Aug 2023, at 20:24, Davide Varvello via Pharo-users [pharo-users@lists.pharo.org](mailto:pharo-users@lists.pharo.org) wrote: > > > > > > Hi Guys, > > > I want to use my old Pharo 8 image on an Apple Silicon (ARM64). I downloaded the stable VM for apple silicon http://files.pharo.org/get-files/110/pharo-vm-Darwin- <http://files.pharo.org/get-files/110/pharo-vm-Darwin-arm64-stable.zip>arm64 <http://files.pharo.org/get-files/110/pharo-vm-Darwin-arm64-stable.zip>-stable.zip <http://files.pharo.org/get-files/110/pharo-vm-Darwin-arm64-stable.zip> but it isn't working with my pharo8 image. > > > > > > My old VM is working, of course, but I suppose it's because of Rosetta... and the performance is not optimal. > > > > > > Any other solution? > > > > I do not think that we have a solution. Iâm sorry but we decided that we cannot garantee that old Pharo version can run on Apple Silicon > > just because of engineering effort. > > With Pharo we are always trying not to trade the past for the future but this is difficult. > > > > S.

Aug. 7, 2023

Re: How to run a Pharo 8 image on an Apple Silicon (ARM64)?

by varvello＠yahoo.com

Hi Steph, I see, I hoped as Pharo 8 and M1 were born in 2020 that Pharo8 was supported Davide

Aug. 7, 2023

Re: How to run a Pharo 8 image on an Apple Silicon (ARM64)?

by Guillermo Polito

Pharo8 is pretty old :) The best I can propose is that you try compiling the VM without the JIT compiler. That will not give you optimum performances, but acceptable ones compared to Rosetta. Iâd suggest you try to compile using the branch pharo-9. Thatâs probably the oldest branch that is easy to build using cmake. If the pharo-9 branch does not work for your image, then maybe you should check the branches (see the branches v8.x.x). For installation/build instructions, please follow the readme instructions. If you find any issues, tell us, maybe there are cheap workarounds or fixes :). Hope that helps, Guille > El 6 ago. 2023, a las 22:07, stephane ducasse <stephane.ducasse(a)inria.fr> escribiÃ³: > > > >> On 4 Aug 2023, at 20:24, Davide Varvello via Pharo-users <pharo-users(a)lists.pharo.org> wrote: >> >> Hi Guys, >> I want to use my old Pharo 8 image on an Apple Silicon (ARM64). I downloaded the stable VM for apple silicon http://files.pharo.org/get-files/110/pharo-vm-Darwin- <http://files.pharo.org/get-files/110/pharo-vm-Darwin-arm64-stable.zip>arm64 <http://files.pharo.org/get-files/110/pharo-vm-Darwin-arm64-stable.zip>-stable.zip <http://files.pharo.org/get-files/110/pharo-vm-Darwin-arm64-stable.zip> but it isn't working with my pharo8 image. >> >> My old VM is working, of course, but I suppose it's because of Rosetta... and the performance is not optimal. >> >> Any other solution? >> > > I do not think that we have a solution. Iâm sorry but we decided that we cannot garantee that old Pharo version can run on Apple Silicon > just because of engineering effort. > With Pharo we are always trying not to trade the past for the future but this is difficult. > > S.

Aug. 7, 2023

Re: How to run a Pharo 8 image on an Apple Silicon (ARM64)?

by stephane ducasse

> On 4 Aug 2023, at 20:24, Davide Varvello via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > Hi Guys, > I want to use my old Pharo 8 image on an Apple Silicon (ARM64). I downloaded the stable VM for apple silicon http://files.pharo.org/get-files/110/pharo-vm-Darwin- <http://files.pharo.org/get-files/110/pharo-vm-Darwin-arm64-stable.zip>arm64 <http://files.pharo.org/get-files/110/pharo-vm-Darwin-arm64-stable.zip>-stable.zip <http://files.pharo.org/get-files/110/pharo-vm-Darwin-arm64-stable.zip> but it isn't working with my pharo8 image. > > My old VM is working, of course, but I suppose it's because of Rosetta... and the performance is not optimal. > > Any other solution? > I do not think that we have a solution. Iâm sorry but we decided that we cannot garantee that old Pharo version can run on Apple Silicon just because of engineering effort. With Pharo we are always trying not to trade the past for the future but this is difficult. S.

Aug. 6, 2023

How to run a Pharo 8 image on an Apple Silicon (ARM64)?

by varvello＠yahoo.com

Hi Guys,Â \ I want to use my old Pharo 8 image on an Apple Silicon (**ARM64**). I downloaded the stable VM for apple siliconÂ [http://files.pharo.org/get-files/110/pharo-vm-Darwin-](http://files.pharo.o… but it isn't working with my pharo8 image.Â \ \ My old VM is working, of course, but I suppose it's because of Rosetta... and the performance is not optimal.Â \ \ Any other solution?Â \ \ TIAÂ \ Davide

Aug. 4, 2023

UK Smalltalk User Group Meeting: Show'n'Tell - 26 July 2023

by Giovanni Corriga

For this month's UKSTUG meeting, we'll open the floor to the whole audience and let people show what they are working on. If you have an interesting project to show, or if you'd like to get some help with some hard problem, just show up and be ready to present! This will be an online meeting from home. If you'd like to join us, please sign up in advance on the meeting's Meetup page ( https://www.meetup.com/ukstug/events/294397093/ ) to receive the meeting details. Donât forget to bring your laptop and drinks!

July 26, 2023

ð Join the Smalltalk Innovation Celebration at ESUG 2023 Tech Awards! ð

by Noury Bouraqadi

Dear Pharoes, You are cordially invited to submit your creations to the ESUG 2023 Tech Awards. This is your golden opportunity to showcase your work, exchange ideas and feedback, and be inspired by fellow Smalltalk enthusiasts worldwide. Plus, there's a chance to win a prize worth up to 500 euros! Join the Smalltalk Tech Awards and help show how cool is Smalltalk. Reply to this message now! Noury On behalf of the ESUG board -- PS. Please spread the word and let others know about the ESUG 2023 Tech Awards

July 17, 2023

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

by Marcus Denker

# This week (28/2023) on the Pharo Issue Tracker Due to holiday season, the next weekly report will be done beginning of August. But activity does not stop! If you do not want to miss anything, consider watching the pharo github repo at https://github.com/pharo-project/pharo # Pharo11 Backports - [Pharo11] backport Slot related fixes #13950 and #13949 #14275 https://github.com/pharo-project/pharo/pull/14275 - [Pharo11] This is a backport: 14034 debugger does not evaluate in the context of the receiver #14274 https://github.com/pharo-project/pharo/pull/14274 - Depends on DocumentBrowser v1.0.1 #14277 https://github.com/pharo-project/pharo/pull/14277 # Fixes - 14226-nil-cannot-be-pinned-in-memory #14227 https://github.com/pharo-project/pharo/pull/14227 - FileBrowser. View as hex not working #14210 https://github.com/pharo-project/pharo/pull/14210 - added convenience methods to easy the usage of TFProcessLocalWorker #14255 https://github.com/pharo-project/pharo/pull/14255 - Treat Integers and Fractions as having scale 0 in ScaledDecimal arithmetic (fixes #14238) #14259 https://github.com/pharo-project/pharo/pull/14259 - Fix haltOn tests after debug them #14167 https://github.com/pharo-project/pharo/pull/14167 - fix calculous of layout when morph is not visible #14229 https://github.com/pharo-project/pharo/pull/14229 - Fix SpChangeSorterPresenter, MessageBrowserPresenter #567 https://github.com/pharo-spec/NewTools/pull/567 - Disable automated transform for deprecation of Object>>asOrderedCollection #14237 https://github.com/pharo-project/pharo/pull/14237 # Refactoring Engine - Fix the preconditions related to packages in refactorings #14236 https://github.com/pharo-project/pharo/pull/14236 - Refactor: clean RBCondition and add popUp flag #14240 https://github.com/pharo-project/pharo/pull/14240 - Refactoring: reuse RBAddMethodTransformRefactoring #14245 https://github.com/pharo-project/pharo/pull/14245 - Fix: update changes preview table when changing active scope #14267 https://github.com/pharo-project/pharo/pull/14267 - Splitting preconditions #14233 https://github.com/pharo-project/pharo/pull/14233 - Fix failing release test about refactorings #14252 https://github.com/pharo-project/pharo/pull/14252 # Compiler / Variables - This fixes #isClean as described in #14141 #14282 https://github.com/pharo-project/pharo/pull/14282 - ClassParser: parse non-fluid defintion of CompiledBlock #14270 https://github.com/pharo-project/pharo/pull/14270 - Improve deprecated slot #14265 https://github.com/pharo-project/pharo/pull/14265 # RPackage - Simplification in Monticello #14244 https://github.com/pharo-project/pharo/pull/14244 - Factorize some unregistering code #14290 https://github.com/pharo-project/pharo/pull/14290 - Remove some overriden methods in Monticello #14293 https://github.com/pharo-project/pharo/pull/14293 - Merge addition of class definition in rpackage #14291 https://github.com/pharo-project/pharo/pull/14291 - Cleaning in RPackage tests #14288 https://github.com/pharo-project/pharo/pull/14288 - Start unification of package removal #14283 https://github.com/pharo-project/pharo/pull/14283 - Push usage of #ensurePackage: #14280 https://github.com/pharo-project/pharo/pull/14280 - Simplify package removal #14281 https://github.com/pharo-project/pharo/pull/14281 - Remove unused method parameter in repackaging #14278 https://github.com/pharo-project/pharo/pull/14278 - Clean MCWorkingCopy #14248 https://github.com/pharo-project/pharo/pull/14248 - Remove rpackage presence check #14272 https://github.com/pharo-project/pharo/pull/14272 - Clean PackageOrganizer methods in testing protocol #14224 https://github.com/pharo-project/pharo/pull/14224 - Deprecate RPackageOrganizer>>#registerPackageNamed: #14260 https://github.com/pharo-project/pharo/pull/14260 - Fix bug in tag creation while creating a category #14256 https://github.com/pharo-project/pharo/pull/14256 - Introduce RPackageOrganizer>>ensurePackage: #14254 https://github.com/pharo-project/pharo/pull/14254 - Deprecate #includesPackageNamed: #14246 https://github.com/pharo-project/pharo/pull/14246 - Introduce RPackageOrganizer#hasPackage: #14232 https://github.com/pharo-project/pharo/pull/14232 # Protocols - Deprecated CompiledMethod tag API #14243 https://github.com/pharo-project/pharo/pull/14243 - Bugfix: Fix double protocol request in Calypso #14268 https://github.com/pharo-project/pharo/pull/14268 - Do not prevent all announcements during method classification #14273 https://github.com/pharo-project/pharo/pull/14273 - Remove unclassify hack #14264 https://github.com/pharo-project/pharo/pull/14264 - Deprecate class reorganized #14285 https://github.com/pharo-project/pharo/pull/14285 - Rename more methods and classes to use "Protocol" vocabulary #14266 https://github.com/pharo-project/pharo/pull/14266 - Fix logging of protocol in Opal #13886 https://github.com/pharo-project/pharo/pull/13886 - Rename some more tags into protocol #14247 https://github.com/pharo-project/pharo/pull/14247 - Do not register to ClassReorganized #566 https://github.com/pharo-spec/NewTools/pull/566 # Cleanup - Remove dead code in bootstrap #14258 https://github.com/pharo-project/pharo/pull/14258 - Update bootstrap scripts #14249 https://github.com/pharo-project/pharo/pull/14249 - 14239-remove-ReAnySatisfyRule #14279 https://github.com/pharo-project/pharo/pull/14279 - Cleanup: Explore it menu entries #14271 https://github.com/pharo-project/pharo/pull/14271 - DeadCodeCleanup-07-10 #14253 https://github.com/pharo-project/pharo/pull/14253 - Dependency Analyser title management #14225 https://github.com/pharo-project/pharo/pull/14225 - 1422-SpDemoconnectPresenters-uses-non-existing-setSelectedItem #1423 https://github.com/pharo-spec/Spec/pull/1423

July 14, 2023