- Pharo-users - lists.pharo.org

[ANN] Pharo Consortium New Bronze Member: SRA

by Marcus Denker

The Pharo Consortium is very happy to announce that SRA has joined the Consortium as a Bronze Member. About - SRA: https://www.sra.co.jp/en/ - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association https://association.pharo.org

May 3, 2022

Re: Pharo is unresponsive after forcing quit

by Yanni Chiu

There is a discussion on discord, probably three weeks ago, about this problem on latest MacOS. A 20ms delay was added (done in the image, not VM), that improved the chances (but is not a root cause fix). On Sun, May 1, 2022 at 7:34 PM Stewart MacLean <stewart(a)xtra.co.nz> wrote: > Hi Yanni, > > Actually, your solution does work! I just tried clicking on the desktop, > but as you said you need to click on another application. > > Very strange - it seems to happen more frequently after a crash, but I > have noticed it happening on normal startup. > > Clicking on another app must "free up the log jam"... somehow... > > Cheers, > > Stewart > > > On Fri, Apr 29, 2022 at 7:49 AM Stewart MacLean <stewart(a)xtra.co.nz> > wrote: > >> Thanks all for your suggestions/replies. >> >> Nothing fixes it for now. I accept that due to the single threaded nature >> of the UI that there will be glitches occasionally, and when you are using >> low level interfaces. >> >> The weird thing is this happens after restarting, when everything should >> be pristine! >> >> Cheers, >> >> Stewart >> >> On Thu, Apr 28, 2022 at 9:41 PM Noury Bouraqadi <bouraqadi(a)gmail.com> >> wrote: >> >>> I've got it too with P9 when I leave an image open for a while. I >>> becomes unresponsive and I have to kill it from the Mac OS "force quit" >>> popup. >>> Hppened to me with the Pharo launcher too. >>> >>> >>> Noury >>> On Apr 28 2022, at 3:47 am, Yanni Chiu <yannix7db(a)gmail.com> wrote: >>> >>> Try switching focus to another app on your Mac (e.g. Finder or web >>> browser), then back to Pharo >>> >>> On Wed, Apr 27, 2022 at 8:44 PM Stewart MacLean <stewart(a)xtra.co.nz> >>> wrote: >>> >>> Hi, >>> >>> [Pharo 10 on Mac Monterey] >>> >>> Due to the multi-process nature of Bonjour that I'm attempting to >>> interface to, I am crashing the system ALOT as it disappears down a black >>> hole and I try to figure out the cause. >>> >>> However, I've noticed that most of the time when I restart Pharo it is >>> unresponsive to clicks and I have to relaunch Pharo AGAIN! Argh....! >>> >>> The mouse moves but no one is at home. Right click brings up menus, but >>> they don't respond. >>> >>> As I move the mouse, list items are highlighted. >>> >>> As this is a completely new OS process, I'm wondering what is causing >>> this behaviour? >>> >>> Has anyone else experienced this, or have an explanation? >>> >>> Cheers, >>> >>> Stewart >>> >>>

May 2, 2022

Re: Pharo is unresponsive after forcing quit

by Stewart MacLean

Hi Yanni, Actually, your solution does work! I just tried clicking on the desktop, but as you said you need to click on another application. Very strange - it seems to happen more frequently after a crash, but I have noticed it happening on normal startup. Clicking on another app must "free up the log jam"... somehow... Cheers, Stewart On Fri, Apr 29, 2022 at 7:49 AM Stewart MacLean <stewart(a)xtra.co.nz> wrote: > Thanks all for your suggestions/replies. > > Nothing fixes it for now. I accept that due to the single threaded nature > of the UI that there will be glitches occasionally, and when you are using > low level interfaces. > > The weird thing is this happens after restarting, when everything should > be pristine! > > Cheers, > > Stewart > > On Thu, Apr 28, 2022 at 9:41 PM Noury Bouraqadi <bouraqadi(a)gmail.com> > wrote: > >> I've got it too with P9 when I leave an image open for a while. I becomes >> unresponsive and I have to kill it from the Mac OS "force quit" popup. >> Hppened to me with the Pharo launcher too. >> >> >> Noury >> On Apr 28 2022, at 3:47 am, Yanni Chiu <yannix7db(a)gmail.com> wrote: >> >> Try switching focus to another app on your Mac (e.g. Finder or web >> browser), then back to Pharo >> >> On Wed, Apr 27, 2022 at 8:44 PM Stewart MacLean <stewart(a)xtra.co.nz> >> wrote: >> >> Hi, >> >> [Pharo 10 on Mac Monterey] >> >> Due to the multi-process nature of Bonjour that I'm attempting to >> interface to, I am crashing the system ALOT as it disappears down a black >> hole and I try to figure out the cause. >> >> However, I've noticed that most of the time when I restart Pharo it is >> unresponsive to clicks and I have to relaunch Pharo AGAIN! Argh....! >> >> The mouse moves but no one is at home. Right click brings up menus, but >> they don't respond. >> >> As I move the mouse, list items are highlighted. >> >> As this is a completely new OS process, I'm wondering what is causing >> this behaviour? >> >> Has anyone else experienced this, or have an explanation? >> >> Cheers, >> >> Stewart >> >>

May 1, 2022

Pharo Enterprise book HTML chapter links

by Sven Van Caekenberghe

Hi, All the Chapter Topics links on https://books.pharo.org/enterprise-pharo/ (bottom left side) are broken. Is it still possible to link to individual chapters ? Can someone have a look, it would be a shame to let this bit rot. Thx, Sven PS: Looking at the other books it seems HTML reading is completely gone, what a shame. This used to work fine.

April 30, 2022

Re: [Pharo-dev] [ANN] Pharo Launcher 3.0.1 released!

by vinref＠gmail.com

Hi This happened to me also on Windows. I killed all running instances of Pharo VM using the TaskManager, then uninstalled the currently installed version, then installed the one I just downloaded. Worked fine after that. Vince

April 30, 2022

Re: Loading from a git repository with Metacello on a running seaside image

by Emilio Oca

Hey, Breaking the ice, by following the logic behind 'Pull' button at 'Working copy of..." from iceberg repo UI, I found I can put this: aRemote := IceGitRemote name: 'origin' url: ' https://github.com/User/MyProject.git'. aRemote localRepository: (IceRepository registry detect: [ :each | each includesPackageNamed: 'MyProject' ]). localBranch := IceGitLocalBranch named: 'refs/heads/main' inRepository: aRemote localRepository. aRemote fetchBranch: localBranch. remoteBranch := aRemote remoteBranchNamed: localBranch name ifAbsent: [ ]. aRemote localRepository workingCopy mergeCommit: remoteBranch commit. under a seaside anchor callback and get the running image self update. I still have to make it work within docker, but it is a start. Thanks all Best Emilio On Fri, Apr 29, 2022 at 8:01 PM Dale Henrichs < dale.henrichs(a)gemtalksystems.com> wrote: > Emilio, > > Okay ... we're peeling the onion :) ... > > At this point it sounds like you need to do a flushCache on your filetree > repository in order to force Metacello to re-download from the github into > the local package-cache. > > But if Iceberg is involved, I am not the person to ask ... I am not > familiar with the changes that have been made to Metacello to get it to > work with Iceberg ... > > Dale > > > > On Fri, Apr 29, 2022 at 3:16 PM Emilio Oca <emiliooca(a)gmail.com> wrote: > >> Hi Dale >> >> Thanks again, still not working. >> After updating github I am unable to pull the changes into the image. >> So far the only way is to hit Pull button at the "Working copy of >> MyProyect" repo window. >> I wish I could reproduce what that button does. >> >> Even this: >> Metacello new >> repository: 'github://...'; >> baseline: 'MyProyect'; >> get >> does not update my file system at iceberg/ >> >> Best >> >> Emilio >> >> On Thu, Apr 28, 2022 at 3:29 PM Dale Henrichs < >> dale.henrichs(a)gemtalksystems.com> wrote: >> >>> Emilio, >>> >>> I wasn't quite sure whether or not you were concerned about having the >>> BaselineOf refreshed or a reload of the packages managed by the BaselineOf >>> and as Gabriel mentions, the missing #projectClass method is the most >>> common problem ... >>> >>> By default Metacello does not refresh a BaselieOf in your image if it is >>> already present, however, you can force a refresh of a BaselineOf by using >>> the the Metcello #get command: >>> >>>> Metacello new baseline:'MyProject'; >>>> repository: 'github://myUser/MyProject:main/myProject'; >>>> get; >>>> load. >>> >>> This would be a good pattern to follow when reloading projects after >>> updating from github ... and I am a bit surprised that this question is not >>> asked more often :) >>> >>> Dale >>> >>> On Mon, Apr 25, 2022 at 6:06 PM Emilio Oca <emiliooca(a)gmail.com> wrote: >>> >>>> Hi Gabriel, Dale! >>>> >>>> My BaselineOf had only #baseline: >>>> Added #projectClass >>>> But is still not working. >>>> It seems to be doing the load, but not the pull before the load. >>>> >>>> I had implemented no more than #baseLine: and now projectClass. >>>> >>>> If I go through the UI and do the pull it works perfectly. >>>> Can I replicate that with a script? >>>> >>>> Best >>>> >>>> Emilio >>>> >>>> On Mon, Apr 25, 2022 at 6:49 PM Dale Henrichs < >>>> dale.henrichs(a)gemtalksystems.com> wrote: >>>> >>>>> Emilio, >>>>> >>>>> Are you using a repository without Monticello meta data? If so, then >>>>> you need to change the #projectClass of you your baseline to: >>>>> >>>>>> projectClass >>>>>> Smalltalk at: #'MetacelloCypressBaselineProject' ifPresent: [ :cl | >>>>>> ^ cl ]. >>>>>> ^ super projectClass >>>>> >>>>> >>>>> unless the #projectClass is MetacelloCypressBaselineProject, Metacello >>>>> will think that your package versions are 'cypress.1' and Metacello will >>>>> not load packages with the same version .... when the #projectClass is >>>>> MetacelloCypressBaselineProject, Metacello will always load the package and >>>>> let Monticello filter out the changes ... >>>>> >>>>> Dale >>>>> >>>>> On Mon, Apr 25, 2022 at 2:39 PM Esteban Lorenzano <estebanlm(a)netc.eu> >>>>> wrote: >>>>> >>>>>> mmm, you may be having another problem elsewhere, because what I >>>>>> typed should be working (is how we enforce the load of new versions to run >>>>>> the tests, for example). >>>>>> >>>>>> Esteban >>>>>> >>>>>> On Apr 25 2022, at 11:30 pm, Emilio Oca <emiliooca(a)gmail.com> wrote: >>>>>> >>>>>> Hi Esteban >>>>>> >>>>>> Thanks for the hint. >>>>>> It is still not working. >>>>>> Even if I remove BaselineOfMyProject and MyProject. >>>>>> When it reloads, it doesn't loads the last version of head at github >>>>>> but the one that was already at the image. >>>>>> >>>>>> I just want to update up to what is at gibhub head. Is there another >>>>>> way? >>>>>> >>>>>> Best >>>>>> >>>>>> Emilio >>>>>> >>>>>> On Sat, Apr 23, 2022 at 1:56 AM Esteban Lorenzano <estebanlm(a)netc.eu> >>>>>> wrote: >>>>>> >>>>>> Hi Emilio, >>>>>> >>>>>> You need something like this: >>>>>> >>>>>> Metacello new >>>>>> repository: 'github://pharo-spec/Spec:Pharo10'; >>>>>> baseline: 'Spec2'; >>>>>> onConflict: [ :e | e useIncoming ]; >>>>>> onUpgrade: [ :e | e useIncoming ]; >>>>>> ignoreImage; >>>>>> load >>>>>> >>>>>> ignoreImage, onConflict, onUpgrade. >>>>>> >>>>>> BUT if your image already has a baseline for your project then >>>>>> Metacello will not reload it (hence your project may not be loaded >>>>>> correctly, since baseline may have changed). >>>>>> >>>>>> In that case, I always execute before something like: >>>>>> >>>>>> #( 'BaselineOfSpec2' 'BaselineOfSpecCore' ) do: [ :each | >>>>>> (RPackageOrganizer default packageNamed: each ifAbsent: [ nil ]) >>>>>> ifNotNil: [ :aPackage | aPackage removeFromSystem ] ] >>>>>> >>>>>> >>>>>> I ack this is hacky, but it works :) >>>>>> >>>>>> Esteban >>>>>> >>>>>> On Apr 23 2022, at 3:21 am, Emilio Oca <emiliooca(a)gmail.com> wrote: >>>>>> >>>>>> Hi List >>>>>> >>>>>> I need some help with Metacello, and may be git too >>>>>> >>>>>> I would like to be able to, in a running headless image, load the >>>>>> last commit of a git repo >>>>>> >>>>>> Something like >>>>>> Metacello new baseline:'MyProject'; >>>>>> repository: 'github://myUser/MyProject:main/myProject'; >>>>>> load. >>>>>> works just once and may open some dialogs >>>>>> >>>>>> Something like this >>>>>> [ >>>>>> [ >>>>>> Metacello new baseline:'MyProject'; >>>>>> repository: 'github://myUser/MyProject:main/myProject'; >>>>>> onConflictUseIncoming; >>>>>> load. >>>>>> ] on: MetacelloSkipDirtyPackageLoad do: [ :ex | ex resume: false ]. >>>>>> ] on: MCMergeOrLoadWarning do: [ :ex | ex load ]. >>>>>> Avoids the dialogs and alerts but the code is still not updated. >>>>>> >>>>>> My intention is to be able to 'refresh' a running seaside image with >>>>>> its latest development version from a git repo (avoiding to personally >>>>>> reach the server and rebuild the docker image) >>>>>> What am I missing? >>>>>> >>>>>> Best >>>>>> >>>>>> Emilio >>>>>> >>>>>>

April 30, 2022

Re: [Pharo-dev] [ANN] Pharo Launcher 3.0.1 released!

by Shaping

PL 3.0.1 is still failing to open on Windows. The VM instance appears in TaskMan. Shaping From: Christophe Demarey <christophe.demarey(a)inria.fr> Sent: Friday, 29 April, 2022 03:50 To: Pharo Development List <pharo-dev(a)lists.pharo.org>; Pharo-users <pharo-users(a)lists.pharo.org> Subject: [Pharo-dev] [ANN] Pharo Launcher 3.0.1 released! Hi all, Pharo Launcher 3.0.1 has just been released! It is available from http://pharo.org/download. It fixes some issues reported on Pharo Launcher 3.0. Here is the changelog: Pharo Launcher v3.0.1 Bug fixes: * #554 <https://github.com/pharo-project/pharo-launcher/issues/554> UI does not show up on Windows * #551 <https://github.com/pharo-project/pharo-launcher/issues/551> Show folder button is broken in Windows 10 * #550 <https://github.com/pharo-project/pharo-launcher/issues/550> About Box shows "untitled Window" * #549 <https://github.com/pharo-project/pharo-launcher/issues/549> Better display of download error messages. * #358 <https://github.com/pharo-project/pharo-launcher/issues/358> Restore proxy authentication settings. Regards, The Pharo team.

April 30, 2022

Re: Loading from a git repository with Metacello on a running seaside image

by Dale Henrichs

Emilio, Okay ... we're peeling the onion :) ... At this point it sounds like you need to do a flushCache on your filetree repository in order to force Metacello to re-download from the github into the local package-cache. But if Iceberg is involved, I am not the person to ask ... I am not familiar with the changes that have been made to Metacello to get it to work with Iceberg ... Dale On Fri, Apr 29, 2022 at 3:16 PM Emilio Oca <emiliooca(a)gmail.com> wrote: > Hi Dale > > Thanks again, still not working. > After updating github I am unable to pull the changes into the image. > So far the only way is to hit Pull button at the "Working copy of > MyProyect" repo window. > I wish I could reproduce what that button does. > > Even this: > Metacello new > repository: 'github://...'; > baseline: 'MyProyect'; > get > does not update my file system at iceberg/ > > Best > > Emilio > > On Thu, Apr 28, 2022 at 3:29 PM Dale Henrichs < > dale.henrichs(a)gemtalksystems.com> wrote: > >> Emilio, >> >> I wasn't quite sure whether or not you were concerned about having the >> BaselineOf refreshed or a reload of the packages managed by the BaselineOf >> and as Gabriel mentions, the missing #projectClass method is the most >> common problem ... >> >> By default Metacello does not refresh a BaselieOf in your image if it is >> already present, however, you can force a refresh of a BaselineOf by using >> the the Metcello #get command: >> >>> Metacello new baseline:'MyProject'; >>> repository: 'github://myUser/MyProject:main/myProject'; >>> get; >>> load. >> >> This would be a good pattern to follow when reloading projects after >> updating from github ... and I am a bit surprised that this question is not >> asked more often :) >> >> Dale >> >> On Mon, Apr 25, 2022 at 6:06 PM Emilio Oca <emiliooca(a)gmail.com> wrote: >> >>> Hi Gabriel, Dale! >>> >>> My BaselineOf had only #baseline: >>> Added #projectClass >>> But is still not working. >>> It seems to be doing the load, but not the pull before the load. >>> >>> I had implemented no more than #baseLine: and now projectClass. >>> >>> If I go through the UI and do the pull it works perfectly. >>> Can I replicate that with a script? >>> >>> Best >>> >>> Emilio >>> >>> On Mon, Apr 25, 2022 at 6:49 PM Dale Henrichs < >>> dale.henrichs(a)gemtalksystems.com> wrote: >>> >>>> Emilio, >>>> >>>> Are you using a repository without Monticello meta data? If so, then >>>> you need to change the #projectClass of you your baseline to: >>>> >>>>> projectClass >>>>> Smalltalk at: #'MetacelloCypressBaselineProject' ifPresent: [ :cl | >>>>> ^ cl ]. >>>>> ^ super projectClass >>>> >>>> >>>> unless the #projectClass is MetacelloCypressBaselineProject, Metacello >>>> will think that your package versions are 'cypress.1' and Metacello will >>>> not load packages with the same version .... when the #projectClass is >>>> MetacelloCypressBaselineProject, Metacello will always load the package and >>>> let Monticello filter out the changes ... >>>> >>>> Dale >>>> >>>> On Mon, Apr 25, 2022 at 2:39 PM Esteban Lorenzano <estebanlm(a)netc.eu> >>>> wrote: >>>> >>>>> mmm, you may be having another problem elsewhere, because what I typed >>>>> should be working (is how we enforce the load of new versions to run the >>>>> tests, for example). >>>>> >>>>> Esteban >>>>> >>>>> On Apr 25 2022, at 11:30 pm, Emilio Oca <emiliooca(a)gmail.com> wrote: >>>>> >>>>> Hi Esteban >>>>> >>>>> Thanks for the hint. >>>>> It is still not working. >>>>> Even if I remove BaselineOfMyProject and MyProject. >>>>> When it reloads, it doesn't loads the last version of head at github >>>>> but the one that was already at the image. >>>>> >>>>> I just want to update up to what is at gibhub head. Is there another >>>>> way? >>>>> >>>>> Best >>>>> >>>>> Emilio >>>>> >>>>> On Sat, Apr 23, 2022 at 1:56 AM Esteban Lorenzano <estebanlm(a)netc.eu> >>>>> wrote: >>>>> >>>>> Hi Emilio, >>>>> >>>>> You need something like this: >>>>> >>>>> Metacello new >>>>> repository: 'github://pharo-spec/Spec:Pharo10'; >>>>> baseline: 'Spec2'; >>>>> onConflict: [ :e | e useIncoming ]; >>>>> onUpgrade: [ :e | e useIncoming ]; >>>>> ignoreImage; >>>>> load >>>>> >>>>> ignoreImage, onConflict, onUpgrade. >>>>> >>>>> BUT if your image already has a baseline for your project then >>>>> Metacello will not reload it (hence your project may not be loaded >>>>> correctly, since baseline may have changed). >>>>> >>>>> In that case, I always execute before something like: >>>>> >>>>> #( 'BaselineOfSpec2' 'BaselineOfSpecCore' ) do: [ :each | >>>>> (RPackageOrganizer default packageNamed: each ifAbsent: [ nil ]) >>>>> ifNotNil: [ :aPackage | aPackage removeFromSystem ] ] >>>>> >>>>> >>>>> I ack this is hacky, but it works :) >>>>> >>>>> Esteban >>>>> >>>>> On Apr 23 2022, at 3:21 am, Emilio Oca <emiliooca(a)gmail.com> wrote: >>>>> >>>>> Hi List >>>>> >>>>> I need some help with Metacello, and may be git too >>>>> >>>>> I would like to be able to, in a running headless image, load the last >>>>> commit of a git repo >>>>> >>>>> Something like >>>>> Metacello new baseline:'MyProject'; >>>>> repository: 'github://myUser/MyProject:main/myProject'; >>>>> load. >>>>> works just once and may open some dialogs >>>>> >>>>> Something like this >>>>> [ >>>>> [ >>>>> Metacello new baseline:'MyProject'; >>>>> repository: 'github://myUser/MyProject:main/myProject'; >>>>> onConflictUseIncoming; >>>>> load. >>>>> ] on: MetacelloSkipDirtyPackageLoad do: [ :ex | ex resume: false ]. >>>>> ] on: MCMergeOrLoadWarning do: [ :ex | ex load ]. >>>>> Avoids the dialogs and alerts but the code is still not updated. >>>>> >>>>> My intention is to be able to 'refresh' a running seaside image with >>>>> its latest development version from a git repo (avoiding to personally >>>>> reach the server and rebuild the docker image) >>>>> What am I missing? >>>>> >>>>> Best >>>>> >>>>> Emilio >>>>> >>>>>

April 29, 2022

Re: Loading from a git repository with Metacello on a running seaside image

by Emilio Oca

Hi Dale Thanks again, still not working. After updating github I am unable to pull the changes into the image. So far the only way is to hit Pull button at the "Working copy of MyProyect" repo window. I wish I could reproduce what that button does. Even this: Metacello new repository: 'github://...'; baseline: 'MyProyect'; get does not update my file system at iceberg/ Best Emilio On Thu, Apr 28, 2022 at 3:29 PM Dale Henrichs < dale.henrichs(a)gemtalksystems.com> wrote: > Emilio, > > I wasn't quite sure whether or not you were concerned about having the > BaselineOf refreshed or a reload of the packages managed by the BaselineOf > and as Gabriel mentions, the missing #projectClass method is the most > common problem ... > > By default Metacello does not refresh a BaselieOf in your image if it is > already present, however, you can force a refresh of a BaselineOf by using > the the Metcello #get command: > >> Metacello new baseline:'MyProject'; >> repository: 'github://myUser/MyProject:main/myProject'; >> get; >> load. > > This would be a good pattern to follow when reloading projects after > updating from github ... and I am a bit surprised that this question is not > asked more often :) > > Dale > > On Mon, Apr 25, 2022 at 6:06 PM Emilio Oca <emiliooca(a)gmail.com> wrote: > >> Hi Gabriel, Dale! >> >> My BaselineOf had only #baseline: >> Added #projectClass >> But is still not working. >> It seems to be doing the load, but not the pull before the load. >> >> I had implemented no more than #baseLine: and now projectClass. >> >> If I go through the UI and do the pull it works perfectly. >> Can I replicate that with a script? >> >> Best >> >> Emilio >> >> On Mon, Apr 25, 2022 at 6:49 PM Dale Henrichs < >> dale.henrichs(a)gemtalksystems.com> wrote: >> >>> Emilio, >>> >>> Are you using a repository without Monticello meta data? If so, then you >>> need to change the #projectClass of you your baseline to: >>> >>>> projectClass >>>> Smalltalk at: #'MetacelloCypressBaselineProject' ifPresent: [ :cl | ^ >>>> cl ]. >>>> ^ super projectClass >>> >>> >>> unless the #projectClass is MetacelloCypressBaselineProject, Metacello >>> will think that your package versions are 'cypress.1' and Metacello will >>> not load packages with the same version .... when the #projectClass is >>> MetacelloCypressBaselineProject, Metacello will always load the package and >>> let Monticello filter out the changes ... >>> >>> Dale >>> >>> On Mon, Apr 25, 2022 at 2:39 PM Esteban Lorenzano <estebanlm(a)netc.eu> >>> wrote: >>> >>>> mmm, you may be having another problem elsewhere, because what I typed >>>> should be working (is how we enforce the load of new versions to run the >>>> tests, for example). >>>> >>>> Esteban >>>> >>>> On Apr 25 2022, at 11:30 pm, Emilio Oca <emiliooca(a)gmail.com> wrote: >>>> >>>> Hi Esteban >>>> >>>> Thanks for the hint. >>>> It is still not working. >>>> Even if I remove BaselineOfMyProject and MyProject. >>>> When it reloads, it doesn't loads the last version of head at github >>>> but the one that was already at the image. >>>> >>>> I just want to update up to what is at gibhub head. Is there another >>>> way? >>>> >>>> Best >>>> >>>> Emilio >>>> >>>> On Sat, Apr 23, 2022 at 1:56 AM Esteban Lorenzano <estebanlm(a)netc.eu> >>>> wrote: >>>> >>>> Hi Emilio, >>>> >>>> You need something like this: >>>> >>>> Metacello new >>>> repository: 'github://pharo-spec/Spec:Pharo10'; >>>> baseline: 'Spec2'; >>>> onConflict: [ :e | e useIncoming ]; >>>> onUpgrade: [ :e | e useIncoming ]; >>>> ignoreImage; >>>> load >>>> >>>> ignoreImage, onConflict, onUpgrade. >>>> >>>> BUT if your image already has a baseline for your project then >>>> Metacello will not reload it (hence your project may not be loaded >>>> correctly, since baseline may have changed). >>>> >>>> In that case, I always execute before something like: >>>> >>>> #( 'BaselineOfSpec2' 'BaselineOfSpecCore' ) do: [ :each | >>>> (RPackageOrganizer default packageNamed: each ifAbsent: [ nil ]) >>>> ifNotNil: [ :aPackage | aPackage removeFromSystem ] ] >>>> >>>> >>>> I ack this is hacky, but it works :) >>>> >>>> Esteban >>>> >>>> On Apr 23 2022, at 3:21 am, Emilio Oca <emiliooca(a)gmail.com> wrote: >>>> >>>> Hi List >>>> >>>> I need some help with Metacello, and may be git too >>>> >>>> I would like to be able to, in a running headless image, load the last >>>> commit of a git repo >>>> >>>> Something like >>>> Metacello new baseline:'MyProject'; >>>> repository: 'github://myUser/MyProject:main/myProject'; >>>> load. >>>> works just once and may open some dialogs >>>> >>>> Something like this >>>> [ >>>> [ >>>> Metacello new baseline:'MyProject'; >>>> repository: 'github://myUser/MyProject:main/myProject'; >>>> onConflictUseIncoming; >>>> load. >>>> ] on: MetacelloSkipDirtyPackageLoad do: [ :ex | ex resume: false ]. >>>> ] on: MCMergeOrLoadWarning do: [ :ex | ex load ]. >>>> Avoids the dialogs and alerts but the code is still not updated. >>>> >>>> My intention is to be able to 'refresh' a running seaside image with >>>> its latest development version from a git repo (avoiding to personally >>>> reach the server and rebuild the docker image) >>>> What am I missing? >>>> >>>> Best >>>> >>>> Emilio >>>> >>>>

April 29, 2022

Re: A question about #beginsWith: and #endsWith:

by Kasper Osterbye

The two methods are changed to do the right thing. We are still waiting for the CI server to check if that broke anything. During the change, 4 places was identified which was simplified by doing it right (aka empty prefix always true). Best, Kasper

April 29, 2022