September 2020 - Pharo-dev - lists.pharo.org

[Pharo 9.0] Build #662: 7265-No-dots-in-OSPlatformenvironment

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #662 was: FAILURE. The Pull Request #7304 was integrated: "7265-No-dots-in-OSPlatformenvironment" Pull request url: https://github.com/pharo-project/pharo/pull/7304 Issue Url: https://github.com/pharo-project/pharo/issues/7265 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 14, 2020

Finalization

by Sean DeNigris

What are the (best?) sources of finalization documentation? I saw posts on the list about wanting some and possibly creating some, but none providing links to actual docs. I want to share an experience report in case it helps anyone elseâ¦ I was implementing a temp file object which should auto delete from the filesystem when it is garbage collected. I did: ```smalltalk Tempfile>>#initializeWithOrigin: aSymbol path: aPath WeakRegistry default add: self. ^ super initializeWithOrigin: aSymbol path: aPath ``` and then: ```smalltalk Tempfile>>#finalize self delete ``` The instVars were nil, so I couldn't delete the file, and I mistakenly assumed that they were nil-ed out during finalization. Eventually, I realized that it was a bug in my code due to a lack of understanding about the initialization mechanism. When an object is added to a weak registry, apparently a shallow copy is what is actually added. In my initialization method, I added the object before it was initialized, so the copy didnât contain the information it needed to finalize the object. Simply reversing the two statements made it work. Lesson learned: objects must treat any state needed during finalization as immutable; at least once the object is added to the weak registry. The main (non-blocking) question remaining is which registry to use. I see other classes that implement `finalize` use their own custom registry - why?

Sept. 14, 2020

[Pharo 9.0] Build #661: merge-spec2-0.7.3

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #661 was: FAILURE. The Pull Request #7255 was integrated: "merge-spec2-0.7.3" Pull request url: https://github.com/pharo-project/pharo/pull/7255 Issue Url: https://github.com/pharo-project/pharo/issues/merge Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 14, 2020

Re: Updating lists.pharo.org: New server, Mailman3 and more

by marcus.denker＠inria.fr

> Migration is Complete! Test reply from the Web interface.

Sept. 14, 2020

Re: Updating lists.pharo.org: New server, Mailman3 and more

by Marcus Denker

Migration is Complete! If you want to login at the website, you need to create a new account with the email address that the lists are now sending emails to. https://lists.pharo.org <https://lists.pharo.org/> > On 14 Sep 2020, at 19:18, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > So: sending emails should now be ok, but the web-interface is still syncing the archives (pharo-dev is there, pharo-users > will be soon). > > But this means that everyone should be fine to send mails again. > > Marcus > >> On 14 Sep 2020, at 19:11, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >> >> Testing if this is send via the new serverâ¦ the new Archive is at https://lists.pharo.org/empathy/list/pharo-dev.lists.pharo.org <https://lists.pharo.org/empathy/list/pharo-dev.lists.pharo.org> >> >> Marcus >> >>> On 14 Sep 2020, at 17:42, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >>> >>> Hi, >>> >>> We are updating the mailinglists (everything https://lists.pharo.org/ <https://lists.pharo.org/>) >>> >>> -> New server, thus: new IPâ¦ >>> -> the server will run Mailman3 (we used Mailman2) >>> -> There will be a better Archive >>> >>> >>> I will do the change of the IP address today. >>> >>> The only thing that could happen is that mails send still via the old server will not be in the >>> new archive, everything else should be transparent. >>> >>> I will send another mail when it is done. >>> >>> Marcus >> >

Sept. 14, 2020

Re: Updating lists.pharo.org: New server, Mailman3 and more

by Marcus Denker

So: sending emails should now be ok, but the web-interface is still syncing the archives (pharo-dev is there, pharo-users will be soon). But this means that everyone should be fine to send mails again. Marcus > On 14 Sep 2020, at 19:11, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Testing if this is send via the new serverâ¦ the new Archive is at https://lists.pharo.org/empathy/list/pharo-dev.lists.pharo.org <https://lists.pharo.org/empathy/list/pharo-dev.lists.pharo.org> > > Marcus > >> On 14 Sep 2020, at 17:42, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >> >> Hi, >> >> We are updating the mailinglists (everything https://lists.pharo.org/ <https://lists.pharo.org/>) >> >> -> New server, thus: new IPâ¦ >> -> the server will run Mailman3 (we used Mailman2) >> -> There will be a better Archive >> >> >> I will do the change of the IP address today. >> >> The only thing that could happen is that mails send still via the old server will not be in the >> new archive, everything else should be transparent. >> >> I will send another mail when it is done. >> >> Marcus >

Sept. 14, 2020

Re: Updating lists.pharo.org: New server, Mailman3 and more

by Marcus Denker

Testing if this is send via the new serverâ¦ the new Archive is at https://lists.pharo.org/empathy/list/pharo-dev.lists.pharo.org <https://lists.pharo.org/empathy/list/pharo-dev.lists.pharo.org> Marcus > On 14 Sep 2020, at 17:42, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > We are updating the mailinglists (everything https://lists.pharo.org/ <https://lists.pharo.org/>) > > -> New server, thus: new IPâ¦ > -> the server will run Mailman3 (we used Mailman2) > -> There will be a better Archive > > > I will do the change of the IP address today. > > The only thing that could happen is that mails send still via the old server will not be in the > new archive, everything else should be transparent. > > I will send another mail when it is done. > > Marcus

Sept. 14, 2020

Updating lists.pharo.org: New server, Mailman3 and more

by Marcus Denker

Hi, We are updating the mailinglists (everything https://lists.pharo.org/ <https://lists.pharo.org/>) -> New server, thus: new IPâ¦ -> the server will run Mailman3 (we used Mailman2) -> There will be a better Archive I will do the change of the IP address today. The only thing that could happen is that mails send still via the old server will not be in the new archive, everything else should be transparent. I will send another mail when it is done. Marcus

Sept. 14, 2020

[Pharo 9.0] Build #660: 7240-PRRichTextComposer-does-not-need-to-use-PragmaCollector

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #660 was: FAILURE. The Pull Request #7246 was integrated: "7240-PRRichTextComposer-does-not-need-to-use-PragmaCollector" Pull request url: https://github.com/pharo-project/pharo/pull/7246 Issue Url: https://github.com/pharo-project/pharo/issues/7240 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 14, 2020

[Pharo 9.0] Build #659: WorldState-no-menuBuilder-cache

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #659 was: FAILURE. The Pull Request #7291 was integrated: "WorldState-no-menuBuilder-cache" Pull request url: https://github.com/pharo-project/pharo/pull/7291 Issue Url: https://github.com/pharo-project/pharo/issues/WorldState Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 13, 2020