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

[Pharo 8.0] Build #710: 4370-Trait-composition-slots-method-contains-duplication

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

There is a new Pharo build available! The status of the build #710 was: SUCCESS. The Pull Request #4371 was integrated: "4370-Trait-composition-slots-method-contains-duplication" Pull request url: https://github.com/pharo-project/pharo/pull/4371 Issue Url: https://github.com/pharo-project/pharo/issues/4370 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 7, 2019

[Pharo 8.0] Build #709: 4447-[CI] Wget log is too verbose

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

There is a new Pharo build available! The status of the build #709 was: FAILURE. The Pull Request #4448 was integrated: "4447-[CI] Wget log is too verbose" Pull request url: https://github.com/pharo-project/pharo/pull/4448 Issue Url: https://github.com/pharo-project/pharo/issues/4447 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 7, 2019

[Pharo 8.0] Build #708: 4088-Commit-should-have-been-implemented-in-IceUnknownCommit

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

There is a new Pharo build available! The status of the build #708 was: SUCCESS. The Pull Request #4423 was integrated: "4088-Commit-should-have-been-implemented-in-IceUnknownCommit" Pull request url: https://github.com/pharo-project/pharo/pull/4423 Issue Url: https://github.com/pharo-project/pharo/issues/4088 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 6, 2019

[Pharo 8.0] Build #707: 4499-Reducing-the-amount-of-hardcoded-reference-to-RBParser-Part2-

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

There is a new Pharo build available! The status of the build #707 was: FAILURE. The Pull Request #4500 was integrated: "4499-Reducing-the-amount-of-hardcoded-reference-to-RBParser-Part2-" Pull request url: https://github.com/pharo-project/pharo/pull/4500 Issue Url: https://github.com/pharo-project/pharo/issues/4499 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 6, 2019

[Pharo 8.0] Build #706: Update licence

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

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

Sept. 6, 2019

[Pharo 8.0] Build #705: FAILURE

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

There is a new Pharo build available! The status of the build #705 was: FAILURE. Could not extract further issue information from commit message: Update FUNDING.yml fixes https for consortium page, updating link Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 6, 2019

[Pharo 8.0] Build #704: SUCCESS

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

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

Sept. 6, 2019

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

by Tudor Girba

Hi, I also confirm that it works both on a Windows 10 with the 1903 and without that update. Thanks! Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow" > On 5 Sep 2019, at 19:03, George Ganea <georgeganea(a)gmail.com> wrote: > > Hi all, > > I just tested the dlls and it looks like itâs working. I say "looks likeâ only because my internet connection is a bit dodgy as Iâm on a train. > But it did start downloading and loading the github repos, so the fix works from my point of view. > > Cheers, > George > >> Thank you both! >> >> We will test and come back with feedback. >> >> Cheers, >> Doru >> >> >> >> > On Sep 5, 2019, at 2:47 PM, Guillermo Polito <guillermopolito at gmail.com> wrote: >> > >> > Hi all, >> > >> > First, please, we would love if you can test what Pablo proposed and give us some feedback. >> > It will be super helpful to evaluate if it is worth to generate a new vm release!!! >> > >> > Also, besides what Pablo said in the previous email, I wanted to share some more precisions. >> > >> > === Precisions on the problem === >> > >> > First, just to clarify, we isolated the issue happening only on Windows10 #1903 on Pharo64 bits. >> > Pharo32 bits does work well on that update number does work well. >> > >> > The origin of the problem seems to be a bad integration between libssh2 1.7.0 and the windows CNG crypto layer, which seemingly changed in this update. >> > >> > === The path to the solution === >> > >> > The solution was theoretically super straight forward (upgrade to openssh 1.9.0 + openssl for crypto instead of windows CNG). >> > >> > It was however super time consuming. >> > - installing the windows update #1903 to test, reproduce and understand the issue took for us a couple of hours, reconfiguring the virtual machines to enlarge disks to download it, then install it... >> > - compiling openssl took literally the entire afternoon yesterday in Pabloâs machine. >> > - then we found several bugs in cmake openssl integration when compiling libssh2 on Cigwin + mingw, because life cannot be easy ^^ >> > >> > And fortunately, we found no incompatibilities between the different versions of these libraries (and libgit2 too!) so it could have been more time consuming :P. >> > >> > === Alternative solutions and workarounds === >> > >> > Alternatively for testing the libraries that Pablo sent in the previous email, there are some other workarounds that people could try in the meantime: >> > >> > 1) Use Pharo32 bits, which as I said above, does not have the problem. >> > >> > 2) Use Iceberg in HTTPS (and specifically set the Iceberg-Metacello integration to HTTP by default). >> > >> > <PastedGraphic-3.png> >> > >> > We are also evaluating setting HTTPS by default in Iceberg as it is simpler to setup. >> > Github, Gitkraken do use HTTPS as a sensible default too. >> > >> > Cheers > >

Sept. 6, 2019

[Pharo 8.0] Build #703: FAILURE

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

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

Sept. 6, 2019

[Pharo 8.0] Build #702: 2372-Add-scanTokens-to-RBScanner

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

There is a new Pharo build available! The status of the build #702 was: SUCCESS. The Pull Request #4504 was integrated: "2372-Add-scanTokens-to-RBScanner" Pull request url: https://github.com/pharo-project/pharo/pull/4504 Issue Url: https://github.com/pharo-project/pharo/issues/2372 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 6, 2019