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

Re: [Pharo-dev] Loading GitHub/Tonel/BaselineOf code in Pharo 6.0

by Esteban Lorenzano

> On 3 Oct 2018, at 14:12, Norbert Hartl <norbert(a)hartl.name> wrote: > > > >> Am 03.10.2018 um 14:02 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >> >> So I am trying to load GitHub/Tonel/BaselineOf code in Pharo 6.0. >> >> I got a fresh 6.0 and I installed Tonel into it using >> >> Metacello new >> repository: 'github://pharo-vcs/tonel'; >> baseline: 'Tonel'; >> load. >> >> Which went OK >> >> Fetched -> BaselineOfTonel-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master >> Loaded -> BaselineOfTonel-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master >> Loading baseline of BaselineOfTonel... >> Fetched -> MonticelloTonel-Core-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master >> Fetched -> MonticelloTonel-FileSystem-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master >> Fetched -> MonticelloTonel-Tests-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master >> Loaded -> MonticelloTonel-Core-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache >> Loaded -> MonticelloTonel-FileSystem-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache >> Loaded -> MonticelloTonel-Tests-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache >> ...finished baseline >> >> Then I try to load some code from me that has been converted to GitHub/Tonel/BaselineOf and that works fine in 6.1/7.0 and contains all meta info >> >> Metacello new >> repository: 'github://svenvc/ztimestamp'; >> baseline: 'ZTimestamp'; >> load. >> >> This fails >> >> ...RETRY->BaselineOfZTimestamp >> ...RETRY->BaselineOfZTimestamp >> ...FAILED->BaselineOfZTimestamp >> >> Could not resolve: BaselineOfZTimestamp [BaselineOfZTimestamp] in /Users/sven/Tmp/pharo6/pharo-local/package-cache github://svenvc/ztimestamp:master >> >> What am I doing wrong here ? >> > That is the behaviour I was talking about. Tonel in my case had read problem at the end of the stream. But I couldnât figure out what it is This is not Tonel. This is Metacello that still does not knows how to handle tonel (thatâs why you need latest version) Esteban > > Norbert >> Thx, >> >> Sven

Oct. 3, 2018

Re: [Pharo-dev] Loading GitHub/Tonel/BaselineOf code in Pharo 6.0

by Esteban Lorenzano

Hi Sven, You still need latest metacello. This is the list of requirements to use metacello and tonel. 1. Latest metacello: Metacello new baseline: 'Metacello'; repository: 'github://metacello/metacello:pharo-6.1_dev/repository'; onConflict: [ :ex | ex useIncoming ]; load. 2. Tonel Metacello new repository: 'github://pharo-vcs/tonel'; baseline: 'Tonel'; load. Both can be loaded in any order, but you need both :) Esteban > On 3 Oct 2018, at 14:02, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > So I am trying to load GitHub/Tonel/BaselineOf code in Pharo 6.0. > > I got a fresh 6.0 and I installed Tonel into it using > > Metacello new > repository: 'github://pharo-vcs/tonel'; > baseline: 'Tonel'; > load. > > Which went OK > > Fetched -> BaselineOfTonel-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master > Loaded -> BaselineOfTonel-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master > Loading baseline of BaselineOfTonel... > Fetched -> MonticelloTonel-Core-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master > Fetched -> MonticelloTonel-FileSystem-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master > Fetched -> MonticelloTonel-Tests-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master > Loaded -> MonticelloTonel-Core-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache > Loaded -> MonticelloTonel-FileSystem-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache > Loaded -> MonticelloTonel-Tests-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache > ...finished baseline > > Then I try to load some code from me that has been converted to GitHub/Tonel/BaselineOf and that works fine in 6.1/7.0 and contains all meta info > > Metacello new > repository: 'github://svenvc/ztimestamp'; > baseline: 'ZTimestamp'; > load. > > This fails > > ...RETRY->BaselineOfZTimestamp > ...RETRY->BaselineOfZTimestamp > ...FAILED->BaselineOfZTimestamp > > Could not resolve: BaselineOfZTimestamp [BaselineOfZTimestamp] in /Users/sven/Tmp/pharo6/pharo-local/package-cache github://svenvc/ztimestamp:master > > What am I doing wrong here ? > > Thx, > > Sven > >

Oct. 3, 2018

Re: [Pharo-dev] Loading GitHub/Tonel/BaselineOf code in Pharo 6.0

by Norbert Hartl

> Am 03.10.2018 um 14:02 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > So I am trying to load GitHub/Tonel/BaselineOf code in Pharo 6.0. > > I got a fresh 6.0 and I installed Tonel into it using > > Metacello new > repository: 'github://pharo-vcs/tonel'; > baseline: 'Tonel'; > load. > > Which went OK > > Fetched -> BaselineOfTonel-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master > Loaded -> BaselineOfTonel-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master > Loading baseline of BaselineOfTonel... > Fetched -> MonticelloTonel-Core-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master > Fetched -> MonticelloTonel-FileSystem-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master > Fetched -> MonticelloTonel-Tests-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master > Loaded -> MonticelloTonel-Core-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache > Loaded -> MonticelloTonel-FileSystem-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache > Loaded -> MonticelloTonel-Tests-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache > ...finished baseline > > Then I try to load some code from me that has been converted to GitHub/Tonel/BaselineOf and that works fine in 6.1/7.0 and contains all meta info > > Metacello new > repository: 'github://svenvc/ztimestamp'; > baseline: 'ZTimestamp'; > load. > > This fails > > ...RETRY->BaselineOfZTimestamp > ...RETRY->BaselineOfZTimestamp > ...FAILED->BaselineOfZTimestamp > > Could not resolve: BaselineOfZTimestamp [BaselineOfZTimestamp] in /Users/sven/Tmp/pharo6/pharo-local/package-cache github://svenvc/ztimestamp:master > > What am I doing wrong here ? > That is the behaviour I was talking about. Tonel in my case had read problem at the end of the stream. But I couldnât figure out what it is Norbert > Thx, > > Sven > >

Oct. 3, 2018

Loading GitHub/Tonel/BaselineOf code in Pharo 6.0

by Sven Van Caekenberghe

So I am trying to load GitHub/Tonel/BaselineOf code in Pharo 6.0. I got a fresh 6.0 and I installed Tonel into it using Metacello new repository: 'github://pharo-vcs/tonel'; baseline: 'Tonel'; load. Which went OK Fetched -> BaselineOfTonel-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master Loaded -> BaselineOfTonel-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master Loading baseline of BaselineOfTonel... Fetched -> MonticelloTonel-Core-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master Fetched -> MonticelloTonel-FileSystem-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master Fetched -> MonticelloTonel-Tests-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master Loaded -> MonticelloTonel-Core-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache Loaded -> MonticelloTonel-FileSystem-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache Loaded -> MonticelloTonel-Tests-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache ...finished baseline Then I try to load some code from me that has been converted to GitHub/Tonel/BaselineOf and that works fine in 6.1/7.0 and contains all meta info Metacello new repository: 'github://svenvc/ztimestamp'; baseline: 'ZTimestamp'; load. This fails ...RETRY->BaselineOfZTimestamp ...RETRY->BaselineOfZTimestamp ...FAILED->BaselineOfZTimestamp Could not resolve: BaselineOfZTimestamp [BaselineOfZTimestamp] in /Users/sven/Tmp/pharo6/pharo-local/package-cache github://svenvc/ztimestamp:master What am I doing wrong here ? Thx, Sven

Oct. 3, 2018

[Pharo 7.0-dev] Build #1292: 22094-Scrollbars-need-to-take-displayScaleFactor-into-account

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

There is a new Pharo build available! The status of the build #1292 was: FAILURE. The Pull Request #1852 was integrated: "22094-Scrollbars-need-to-take-displayScaleFactor-into-account" Pull request url: https://github.com/pharo-project/pharo/pull/1852 Issue Url: https://pharo.fogbugz.com/f/cases/22094 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 3, 2018

[Pharo 7.0-dev] Build #1291: 22513-Update-ProfStef-and-fix-spelling-mistakes

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

There is a new Pharo build available! The status of the build #1291 was: SUCCESS. The Pull Request #1853 was integrated: "22513-Update-ProfStef-and-fix-spelling-mistakes" Pull request url: https://github.com/pharo-project/pharo/pull/1853 Issue Url: https://pharo.fogbugz.com/f/cases/development Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 3, 2018

Re: [Pharo-dev] [ANN] 22477 DelayScheduler cleanup and refactoring [was: Where do we go now ?]

by Guillermo Polito

Yes +1 on the thanks! Also it's great to read your emails to learn new stuff :) On Tue, Oct 2, 2018 at 8:30 PM Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Ben I would like to thank you! > Simply. > > Stef > On Tue, Oct 2, 2018 at 5:58 AM Ben Coman <btc(a)openinworld.com> wrote: > > > > On Fri, 13 Apr 2018 at 13:56, Benoit St-Jean via Pharo-users < > pharo-users(a)lists.pharo.org> wrote: > >> > >> Do we really need 8 delay schedulers (DelayMicrosecondScheduler, > DelayMillisecondScheduler, DelayNullScheduler, > DelayExperimentalSpinScheduler, DelaySpinScheduler, DelayTicklessScheduler, > DelayExperimentalCourageousScheduler, DelayExperimentalSemaphoreScheduler) ? > > > > > > I've cleaned the delay scheduling subsystem [1] to condense these > alternatives and separate orthogonal functionality. After a couple of > reviews this was integrated and made active in last week's Build 1273. > Could anyone with test scenarios from previous issues with delays have a > bash at stressing the latest build. > > > > The old(existing) DelaySpinScheduler remains in the system so it can be > activated as a point of comparison (System > Settings > System > Delay > Scheduler). Pending any adverse reports the final step will be to remove > the old hierarchy next week. > > > > There remain separate mutex and semaphore based schedulers since: > > * they differ by only a couple of overridden methods > > * their slightly different implementations help highlight the core > algorithm > > * they provide a simple in-Image example of different synchronisation > mechanisms. > > * in isolating edge cases its useful to be able to compare results > between implementations > > > > I've retained both microsecond and millisecond operation, > > but extracted into "ticker" classes orthogonal to the "scheduling" > classes since: > > * it makes the core scheduling algorithm independent of time base > > * millisecond (or other custom) timebase might(?) be more efficient on > smaller 32-bit embedded systems > > * tests can now simulate ticker time to avoid tests interfering with > system's-active-scheduler VM interaction (which may be the source of some > random CI failures) > > * delay scheduler tests are now independent of real-time (which may be > the source of some random CI failures where delays are affected by varying > CI server loads) > > * when multi-threaded FFI callbacks become available, may facilitate > experimenting with: > > * wake-up from native timers > > * wake-up of embedded Pharo from the encompassing system > > > > > > Other refactors: > > * during system snapshot, save/restore of resumption times was happening > at user priority which risks a race condition reported at [2]. *All* > modification of resumption times now occurs at timing/highest priority. > > > > > > [1] > https://pharo.manuscript.com/f/cases/22477/DelayScheduler-cleanup-and-refac… > > [2] https://pharo.manuscript.com/f/cases/18359/ > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Oct. 3, 2018

Re: [Pharo-dev] Pharo Downloads are sluggish

by Marcus Denker

Ok, so the upgrade of the server contract did not help. There is a CDN included, I will try to enable that next (but CDNs cache by name, so we need to make sure we invalidate the cacheâ¦) I will do a calculation what S3 would cost, too. Marcus > On 3 Oct 2018, at 00:59, Esteban Maringolo <emaringolo(a)gmail.com> wrote: > > I'm reviving this because I can't finish the download of an image using the latest Pharo launcher. > > I'm timeout errors when attempting to download it. Tried 5 times at different intervals. > > > <image.png> > > Any idea of what could be happening? > > Esteban A. Maringolo > > > El mar., 18 sept. 2018 a las 21:03, Esteban Maringolo (<emaringolo(a)gmail.com <mailto:emaringolo@gmail.com>>) escribiÃ³: > Is there a reason why the latest version of the builds linked from the website are not hosted in some CDN, Amazon S3 or similar? > > Maybe in Europe the speed is fast, but where I am (Argentina) it is really slow, the screenshot shows 3.5KB/s, it averages 10KB/s, with peaks of 40KB/s. > > This is an pitiful boarding experience, that will make many cancel it even before getting to open the downloaded launcher. > > <node-pharo.png> > > The screenshot shows that is not a problem with my home connection, which isn't the fastest but is "normal" for my use cases. > > Regards, > > Esteban A. Maringolo > > ps: When I finished writing this email, this was the progress... > <image.png>

Oct. 3, 2018

[Pharo 7.0-dev] Build #1290: 22511-TestValueWithinFix-is-failing-randomly

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

There is a new Pharo build available! The status of the build #1290 was: SUCCESS. The Pull Request #1851 was integrated: "22511-TestValueWithinFix-is-failing-randomly" Pull request url: https://github.com/pharo-project/pharo/pull/1851 Issue Url: https://pharo.fogbugz.com/f/cases/22511 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 3, 2018

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/

by monty

It would also prefer an SS3-based STHub, at least as an alternative to GitHub. ___ montyos.wordpress.com > Sent: Saturday, September 29, 2018 at 6:43 AM > From: "Stephane Ducasse" <stepharo.self(a)gmail.com> > To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Subject: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/ > > Hi Sven > > SmalltalkHub is dying. And we will turn it readonly by January. > Esteban has something else to do that to take care of it. It is a legacy. > We are about to announce that we cannot create account and projects anymore. > We are waiting to do that after the mooc. > Now you want to use Squeaksource or SS3 I do not want. > I want to use github and I guess that I do not have to explain why for real. > > Stef > > On Sat, Sep 29, 2018 at 11:27 AM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > I think that would be monty, email addresses (CC-ed) > > > > monty2(a)programmer.net > > > > I should note that he has been very good at maintaining the XML packages (the specs of which are super complex), and as far as I know, the code works under Pharo 7 ... > > > > What does not work for you ? > > > > Sven > > > > > On 29 Sep 2018, at 10:38, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > > > > > Hi > > > > > > I contacted the maintainer (but I'm not sure in fact who it is :) ) > > > about the XML related packages in Pharo extras. > > > > > > XMLParser > > > XMLParserHTML > > > XMLParserStAX > > > XMLSupport > > > XMLWriter > > > XPath > > > > > > I did not get any answer so may be I sent a mail to the wrong email address. > > > Probably. > > > Now the question still remains: who is planning to migrate the XML packages. > > > I was planning to do it but I will not consider history because I do > > > not know how to do it and I do not have the time to do it (sorry). And > > > yes I work the weekends and this is bad and this is not even on Pharo. > > > > > > I was planning to spend some time on the baseline and making sure that > > > we can load everything and run the tests. > > > So let me know. > > > > > > Stef > > > > > > > > >

Oct. 3, 2018