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

[Pharo 8.0] Build #696: fix/blockprinting

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

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

Sept. 4, 2019

Re: [Pharo-dev] humanReadablePrintString

by Sven Van Caekenberghe

Yes, probably. > On 4 Sep 2019, at 15:32, Hilaire <hilaire(a)drgeo.eu> wrote: > > Hi, > > This code leads to an error: > > "On place 10'000 â¬ Ã un taux de 4 % par annÃ©e. > Au bout de combien d'annÃ©es aura-t-on 20'000 â¬ ?" > | annee | > annee := [ :capital | > ((capital / 10000) log / (1 + 0.04) log) years > humanReadablePrintString ]. > annee value: 20000 . > > #printWithCommasOn: is understood only by integer. > > In my opinion printHumanReadableOn: should be edited as: > > ../.. > > (wholeNanoseconds 'nanosecond')) do: [ :each | > count := (self perform: each first) truncated. > count > 0 > > ../.. > > Opinion? > > Hilaire > > > -- > Dr. Geo > http://drgeo.eu > > >

Sept. 4, 2019

humanReadablePrintString

by Hilaire

Hi, This code leads to an error: "On place 10'000 â¬ Ã un taux de 4 % par annÃ©e. Au bout de combien d'annÃ©es aura-t-on 20'000 â¬ ?" | annee | annee := [ :capital | Â Â Â ((capital / 10000) log / (1 + 0.04) log) years humanReadablePrintStringÂ ]. annee value: 20000 . #printWithCommasOn: is understood only by integer. In my opinion printHumanReadableOn: should be edited as: ../.. Â Â Â Â Â Â (wholeNanoseconds 'nanosecond')) do: [ :each | Â Â Â Â Â Â count := (self perform: each first) truncated. Â Â Â Â Â Â count > 0Â ../.. Opinion? Hilaire -- Dr. Geo http://drgeo.eu

Sept. 4, 2019

[Pharo 8.0] Build #695: FAILURE

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

There is a new Pharo build available! The status of the build #695 was: FAILURE. Could not extract further issue information from commit message: Create weekly-digest.yml another try... Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 4, 2019

Re: [Pharo-dev] possible Windows Update "1903" Iceberg problem

by Tudor Girba

Super cool!! Thanks! We will happily test. Cheers, Doru > On Sep 4, 2019, at 10:04 AM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Hi all, > > Sorry for not communicating better :). > We know this is an important issue and we did move it to top priority even prior to this email ;). > Doru, to answer you, what people can do for the moment is to test what we are going to propose in a couple of hours in your windows machines. > With Pablo we have tested in several Windows 10 machines pre- and post- update 1903. Still we would like people testing on their setups and other windows versions > > We have been working the last couple of days debugging openssh and libgit, and building a version with a more up-to-date version of openssh. > We will come back later this morning / early afternoon with > - a new vm setup using up to date versions of openssh > - a description of workarounds for those tied to old versions of the VM > So people can test. > > Cheers, > Guille and Pablo > >> El 4 sept 2019, a las 8:38, ducasse <stepharo(a)netcourrier.com> escribiÃ³: >> >> I saw everybody super busy and I imagine that they will reply soon. >> Iâm travelling to give Pharo lectures. >> >>> On 3 Sep 2019, at 19:23, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> Hi, >>> >>> Is there a way to speed the work on this one? >>> >>> At this moment, people cannot load any code in Pharo on Windows 10. >>> >>> Cheers, >>> Doru >>> >>> -- >>> www.feenk.com >>> "Every thing has its own flow." >>> >>>> On 28 Aug 2019, at 16:20, ducasse <stepharo(a)netcourrier.com> wrote: >>>> >>>> tx doru >>>> >>>> Stef >>>> >>>>> On 28 Aug 2019, at 16:01, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>>> >>>>> Hi >>>>> >>>>> I opened an issue: https://github.com/pharo-project/pharo/issues/4437 >>>>> >>>>> I believe this should be treated as critical given that we cannot load code in Pharo 7 (or 8) which makes it almost useless for users. >>>>> >>>>> Cheers, >>>>> Doru >>>>> >>>>> >>>>>> On Aug 27, 2019, at 10:54 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> We just encountered this on two different machines. We got this after the update to Windows 1903. For us itâs a critical issue at this point. What can we do to help with this? >>>>>> >>>>>> Cheers, >>>>>> Doru >>>>>> >>>>>> >>>>>> >>>>>>> On Aug 17, 2019, at 12:50 PM, Ben Coman <btc(a)openInWorld.com> wrote: >>>>>>> >>>>>>> hi Stef, >>>>>>> I feel you missed my point. Probably I wasn't clear this has already been tested with latest Pharo 8 launched by PharoLauncher. >>>>>>> The problem occurs with Pharo 7.0.3(64 bit) and with Pharo8.0-SNAPSHOT-build.635(64 bit) >>>>>>> after Microsoft Windows Update 1903... >>>>>>> https://www.computerworld.com/article/3409621/microsoft-starts-windows-10s-… >>>>>>> >>>>>>> If indeed 1903 is the cause, with this update now being *forced* down on people, this will potentially soon impact more and more Windows users. >>>>>>> But my guess that 1903 is the culprit needs to be confirmed. >>>>>>> So I am requesting someone with access to multiple Windows machines directly compare a 1903 machine with a pre-1903 machine. >>>>>>> >>>>>>> cheers -ben >>>>>>> >>>>>>> On Sat, 17 Aug 2019 at 12:58, ducasse <stepharo(a)netcourrier.com> wrote: >>>>>>> Hi ben >>>>>>> >>>>>>> in the pharo launcher if you click on P8.0 (development version) you get access to all the builds. >>>>>>> >>>>>>> Stef >>>>>>> >>>>>>>> On 16 Aug 2019, at 16:02, Ben Coman <btc(a)openinworld.com> wrote: >>>>>>>> >>>>>>>> IThis morning the May 2019 Windows Update "1903" forced itself onto my computer and now 64-bits Pharo seems to have a problem with git_remote_fetch() FFI callout. I no longer have a non-1903 machine to directly compare behaviour before "1903". Can someone familiar with this area with both "pre-1903" and "1903" machines triage whether "1903" is indeed the cause? >>>>>>>> >>>>>>>> A few other recent reports are noted here... >>>>>>>> https://github.com/pharo-project/pharo/issues/3418 >>>>>>>> >>>>>>>> cheers -ben >>>>>>> >>>>>> >>>>>> -- >>>>>> feenk.com >>>>>> >>>>>> "Not knowing how to do something is not an argument for how it cannot be done." >>>>>> >>>>> >>>>> -- >>>>> feenk.com >>>>> >>>>> âLive like you mean it." >>>>> >>>>> >>>> >>>> >>>> >>> >> >> >> > > -- feenk.com "Innovation comes in the least expected form. That is, if it is expected, it already happened."

Sept. 4, 2019

Re: [Pharo-dev] possible Windows Update "1903" Iceberg problem

by Guillermo Polito

Hi all, Sorry for not communicating better :). We know this is an important issue and we did move it to top priority even prior to this email ;). Doru, to answer you, what people can do for the moment is to test what we are going to propose in a couple of hours in your windows machines. With Pablo we have tested in several Windows 10 machines pre- and post- update 1903. Still we would like people testing on their setups and other windows versions We have been working the last couple of days debugging openssh and libgit, and building a version with a more up-to-date version of openssh. We will come back later this morning / early afternoon with - a new vm setup using up to date versions of openssh - a description of workarounds for those tied to old versions of the VM So people can test. Cheers, Guille and Pablo > El 4 sept 2019, a las 8:38, ducasse <stepharo(a)netcourrier.com> escribiÃ³: > > I saw everybody super busy and I imagine that they will reply soon. > Iâm travelling to give Pharo lectures. > >> On 3 Sep 2019, at 19:23, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> Is there a way to speed the work on this one? >> >> At this moment, people cannot load any code in Pharo on Windows 10. >> >> Cheers, >> Doru >> >> -- >> www.feenk.com >> "Every thing has its own flow." >> >>> On 28 Aug 2019, at 16:20, ducasse <stepharo(a)netcourrier.com> wrote: >>> >>> tx doru >>> >>> Stef >>> >>>> On 28 Aug 2019, at 16:01, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>> >>>> Hi >>>> >>>> I opened an issue: https://github.com/pharo-project/pharo/issues/4437 >>>> >>>> I believe this should be treated as critical given that we cannot load code in Pharo 7 (or 8) which makes it almost useless for users. >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>>> On Aug 27, 2019, at 10:54 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>>> >>>>> Hi, >>>>> >>>>> We just encountered this on two different machines. We got this after the update to Windows 1903. For us itâs a critical issue at this point. What can we do to help with this? >>>>> >>>>> Cheers, >>>>> Doru >>>>> >>>>> >>>>> >>>>>> On Aug 17, 2019, at 12:50 PM, Ben Coman <btc(a)openInWorld.com> wrote: >>>>>> >>>>>> hi Stef, >>>>>> I feel you missed my point. Probably I wasn't clear this has already been tested with latest Pharo 8 launched by PharoLauncher. >>>>>> The problem occurs with Pharo 7.0.3(64 bit) and with Pharo8.0-SNAPSHOT-build.635(64 bit) >>>>>> after Microsoft Windows Update 1903... >>>>>> https://www.computerworld.com/article/3409621/microsoft-starts-windows-10s-… >>>>>> >>>>>> If indeed 1903 is the cause, with this update now being *forced* down on people, this will potentially soon impact more and more Windows users. >>>>>> But my guess that 1903 is the culprit needs to be confirmed. >>>>>> So I am requesting someone with access to multiple Windows machines directly compare a 1903 machine with a pre-1903 machine. >>>>>> >>>>>> cheers -ben >>>>>> >>>>>> On Sat, 17 Aug 2019 at 12:58, ducasse <stepharo(a)netcourrier.com> wrote: >>>>>> Hi ben >>>>>> >>>>>> in the pharo launcher if you click on P8.0 (development version) you get access to all the builds. >>>>>> >>>>>> Stef >>>>>> >>>>>>> On 16 Aug 2019, at 16:02, Ben Coman <btc(a)openinworld.com> wrote: >>>>>>> >>>>>>> IThis morning the May 2019 Windows Update "1903" forced itself onto my computer and now 64-bits Pharo seems to have a problem with git_remote_fetch() FFI callout. I no longer have a non-1903 machine to directly compare behaviour before "1903". Can someone familiar with this area with both "pre-1903" and "1903" machines triage whether "1903" is indeed the cause? >>>>>>> >>>>>>> A few other recent reports are noted here... >>>>>>> https://github.com/pharo-project/pharo/issues/3418 >>>>>>> >>>>>>> cheers -ben >>>>>> >>>>> >>>>> -- >>>>> feenk.com >>>>> >>>>> "Not knowing how to do something is not an argument for how it cannot be done." >>>>> >>>> >>>> -- >>>> feenk.com >>>> >>>> âLive like you mean it." >>>> >>>> >>> >>> >>> >> > > >

Sept. 4, 2019

[Pharo 8.0] Build #694: writeScanOn-is-dead-code

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

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

Sept. 4, 2019

Re: [Pharo-dev] possible Windows Update "1903" Iceberg problem

by ducasse

I saw everybody super busy and I imagine that they will reply soon. Iâm travelling to give Pharo lectures. > On 3 Sep 2019, at 19:23, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > Is there a way to speed the work on this one? > > At this moment, people cannot load any code in Pharo on Windows 10. > > Cheers, > Doru > > -- > www.feenk.com > "Every thing has its own flow." > >> On 28 Aug 2019, at 16:20, ducasse <stepharo(a)netcourrier.com> wrote: >> >> tx doru >> >> Stef >> >>> On 28 Aug 2019, at 16:01, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> Hi >>> >>> I opened an issue: https://github.com/pharo-project/pharo/issues/4437 >>> >>> I believe this should be treated as critical given that we cannot load code in Pharo 7 (or 8) which makes it almost useless for users. >>> >>> Cheers, >>> Doru >>> >>> >>>> On Aug 27, 2019, at 10:54 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>> >>>> Hi, >>>> >>>> We just encountered this on two different machines. We got this after the update to Windows 1903. For us itâs a critical issue at this point. What can we do to help with this? >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> >>>>> On Aug 17, 2019, at 12:50 PM, Ben Coman <btc(a)openInWorld.com> wrote: >>>>> >>>>> hi Stef, >>>>> I feel you missed my point. Probably I wasn't clear this has already been tested with latest Pharo 8 launched by PharoLauncher. >>>>> The problem occurs with Pharo 7.0.3(64 bit) and with Pharo8.0-SNAPSHOT-build.635(64 bit) >>>>> after Microsoft Windows Update 1903... >>>>> https://www.computerworld.com/article/3409621/microsoft-starts-windows-10s-… >>>>> >>>>> If indeed 1903 is the cause, with this update now being *forced* down on people, this will potentially soon impact more and more Windows users. >>>>> But my guess that 1903 is the culprit needs to be confirmed. >>>>> So I am requesting someone with access to multiple Windows machines directly compare a 1903 machine with a pre-1903 machine. >>>>> >>>>> cheers -ben >>>>> >>>>> On Sat, 17 Aug 2019 at 12:58, ducasse <stepharo(a)netcourrier.com> wrote: >>>>> Hi ben >>>>> >>>>> in the pharo launcher if you click on P8.0 (development version) you get access to all the builds. >>>>> >>>>> Stef >>>>> >>>>>> On 16 Aug 2019, at 16:02, Ben Coman <btc(a)openinworld.com> wrote: >>>>>> >>>>>> IThis morning the May 2019 Windows Update "1903" forced itself onto my computer and now 64-bits Pharo seems to have a problem with git_remote_fetch() FFI callout. I no longer have a non-1903 machine to directly compare behaviour before "1903". Can someone familiar with this area with both "pre-1903" and "1903" machines triage whether "1903" is indeed the cause? >>>>>> >>>>>> A few other recent reports are noted here... >>>>>> https://github.com/pharo-project/pharo/issues/3418 >>>>>> >>>>>> cheers -ben >>>>> >>>> >>>> -- >>>> feenk.com >>>> >>>> "Not knowing how to do something is not an argument for how it cannot be done." >>>> >>> >>> -- >>> feenk.com >>> >>> âLive like you mean it." >>> >>> >> >> >> >

Sept. 4, 2019

Fund rising for the new Spec20 book.

by StÃ©phane Ducasse

Hello Pharoers and Smalltalk Friends Often you or other complain that there is not enough documentation, tutorialsâ¦. (even if we have a mooc worth 155 K euros http://mooc.pharo.org, several great books http://book.pharo.org) but yes we should update them. Now I started to work on a new book on Spec 20 with Cyril Ferlicot and I decided that I will not write it for free because it will take me at least 6 months. So I decided that if this community wants more books and documentation, it should prove its will :) I created a fundraising campaign to check if people can align their wishes and their means. So feel free to sponsor this great book. Building user interfaces with spec 20 â https://www.okpal.com/building-user-interfaces-with-spec/?utm_campaign=01DK… Organisations can also do it. BTW: the crowd funding system and other cost will cost us 10% and after we will pay taxes on this. So I prefer not to count our hour cost because else I would really not write a book at all. Stef -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Sept. 3, 2019

Re: [Pharo-dev] possible Windows Update "1903" Iceberg problem

by Tudor Girba

Hi, Is there a way to speed the work on this one? At this moment, people cannot load any code in Pharo on Windows 10. Cheers, Doru -- www.feenk.com "Every thing has its own flow." > On 28 Aug 2019, at 16:20, ducasse <stepharo(a)netcourrier.com> wrote: > > tx doru > > Stef > >> On 28 Aug 2019, at 16:01, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi >> >> I opened an issue: https://github.com/pharo-project/pharo/issues/4437 >> >> I believe this should be treated as critical given that we cannot load code in Pharo 7 (or 8) which makes it almost useless for users. >> >> Cheers, >> Doru >> >> >>> On Aug 27, 2019, at 10:54 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> Hi, >>> >>> We just encountered this on two different machines. We got this after the update to Windows 1903. For us itâs a critical issue at this point. What can we do to help with this? >>> >>> Cheers, >>> Doru >>> >>> >>> >>>> On Aug 17, 2019, at 12:50 PM, Ben Coman <btc(a)openInWorld.com> wrote: >>>> >>>> hi Stef, >>>> I feel you missed my point. Probably I wasn't clear this has already been tested with latest Pharo 8 launched by PharoLauncher. >>>> The problem occurs with Pharo 7.0.3(64 bit) and with Pharo8.0-SNAPSHOT-build.635(64 bit) >>>> after Microsoft Windows Update 1903... >>>> https://www.computerworld.com/article/3409621/microsoft-starts-windows-10s-… >>>> >>>> If indeed 1903 is the cause, with this update now being *forced* down on people, this will potentially soon impact more and more Windows users. >>>> But my guess that 1903 is the culprit needs to be confirmed. >>>> So I am requesting someone with access to multiple Windows machines directly compare a 1903 machine with a pre-1903 machine. >>>> >>>> cheers -ben >>>> >>>> On Sat, 17 Aug 2019 at 12:58, ducasse <stepharo(a)netcourrier.com> wrote: >>>> Hi ben >>>> >>>> in the pharo launcher if you click on P8.0 (development version) you get access to all the builds. >>>> >>>> Stef >>>> >>>>> On 16 Aug 2019, at 16:02, Ben Coman <btc(a)openinworld.com> wrote: >>>>> >>>>> IThis morning the May 2019 Windows Update "1903" forced itself onto my computer and now 64-bits Pharo seems to have a problem with git_remote_fetch() FFI callout. I no longer have a non-1903 machine to directly compare behaviour before "1903". Can someone familiar with this area with both "pre-1903" and "1903" machines triage whether "1903" is indeed the cause? >>>>> >>>>> A few other recent reports are noted here... >>>>> https://github.com/pharo-project/pharo/issues/3418 >>>>> >>>>> cheers -ben >>>> >>> >>> -- >>> feenk.com >>> >>> "Not knowing how to do something is not an argument for how it cannot be done." >>> >> >> -- >> feenk.com >> >> âLive like you mean it." >> >> > > >

Sept. 3, 2019