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

[Pharo 7.0-dev] Build #904: 21884-Dont-use-ZnUtils-for-Base64-encodingdecoding-outside-of-Zn

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

There is a new Pharo build available! The status of the build #904 was: SUCCESS. The Pull Request #1364 was integrated: "21884-Dont-use-ZnUtils-for-Base64-encodingdecoding-outside-of-Zn" Pull request url: https://github.com/pharo-project/pharo/pull/1364 Issue Url: https://pharo.fogbugz.com/f/cases/21884 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 16, 2018

[Pharo 7.0-dev] Build #903: 21810-Cant-show-hexdump-of-compiled-method

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

There is a new Pharo build available! The status of the build #903 was: SUCCESS. The Pull Request #1361 was integrated: "21810-Cant-show-hexdump-of-compiled-method" Pull request url: https://github.com/pharo-project/pharo/pull/1361 Issue Url: https://pharo.fogbugz.com/f/cases/21810 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 15, 2018

[Pharo 7.0-dev] Build #902: 21843 Put ChunkImportTestCase into new test package CodeImport-Tests

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

There is a new Pharo build available! The status of the build #902 was: FAILURE. The Pull Request #1310 was integrated: "21843 Put ChunkImportTestCase into new test package CodeImport-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/1310 Issue Url: https://pharo.fogbugz.com/f/cases/21843 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 15, 2018

[Pharo 7.0-dev] Build #901: backstop

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

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

May 15, 2018

Unstable CI: Issue to collect all the error messages

by Marcus Denker

Hi, The CI is a bit unstable. I added an issue tracker entry so we can record what exactly is going wrong (there seem to be 4-5 undefended issues) https://pharo.fogbugz.com/f/cases/21910/CI-is-unstable

May 15, 2018

[Pharo 7.0-dev] Build #900: 21879-do-we-still-need-basicAddSelectorwithMethod-

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

There is a new Pharo build available! The status of the build #900 was: SUCCESS. The Pull Request #1357 was integrated: "21879-do-we-still-need-basicAddSelectorwithMethod-" Pull request url: https://github.com/pharo-project/pharo/pull/1357 Issue Url: https://pharo.fogbugz.com/f/cases/21879 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 15, 2018

Re: [Pharo-dev] [Pharo 7.0-dev] Build #899: 20322-name-sent-to-a-class-SHOULD-NOT-automatically-rename-and-destroy-the-class

by Sean P. DeNigris

ci-pharo-ci-jenkins2 wrote > â¦name-sent-to-a-class-SHOULD-NOT-automatically-rename-and-destroy-the-classâ¦ Hooray! One less newbie* gotcha :) * Although I had fallen into this trap a few times even when not so new ;) ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

May 15, 2018

[Pharo 7.0-dev] Build #899: 20322-name-sent-to-a-class-SHOULD-NOT-automatically-rename-and-destroy-the-class

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

There is a new Pharo build available! The status of the build #899 was: FAILURE. The Pull Request #1356 was integrated: "20322-name-sent-to-a-class-SHOULD-NOT-automatically-rename-and-destroy-the-class" Pull request url: https://github.com/pharo-project/pharo/pull/1356 Issue Url: https://pharo.fogbugz.com/f/cases/20322 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 15, 2018

[Pharo 7.0-dev] Build #898: 21899-MetacelloCommonPlatformcopyClassasinCategory-uses-old-Compiler-API

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

There is a new Pharo build available! The status of the build #898 was: SUCCESS. The Pull Request #1355 was integrated: "21899-MetacelloCommonPlatformcopyClassasinCategory-uses-old-Compiler-API" Pull request url: https://github.com/pharo-project/pharo/pull/1355 Issue Url: https://pharo.fogbugz.com/f/cases/21899 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 15, 2018

Re: [Pharo-dev] Sign Windows VMs

by Esteban Lorenzano

we are working on this, but for some weird reasons (including the fact Iâm not so fluent on windows anymore ;) ) we havenât fixed the problem :P but well, the idea is to sign PharoVM for windows as we do it for macOS (we already have a certificate for Pharo provided by INRIASoft) soâ¦ it will be thereâ¦ sooner than later :) cheers, Esteban > On 15 May 2018, at 01:14, <Vincent.Blondeau(a)lamresearch.com> <Vincent.Blondeau(a)lamresearch.com> wrote: > > Hi! > > I am using Pharo in a company network under a firewall, an antivirus, and windows, and each day I have an issue with some parts of the Pharo application that are recognized as a threat. So, I cannot download it or execute it straightforwardly. > > Today was this one: > > [https://cdn.discordapp.com/attachments/365850577340727296/44568885694850662…] > Another day was the Cairo Dll where a "Veil Evasion Payload" has been detected. > > And some people has encounter the same kind of issues: > > * https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/152 > * https://pharo.fogbugz.com/f/cases/20500/WindowsDefender-consider-SqueakSSL-… > > It seems that the solution is to sign the VM with Authenticode, but for this, one needs to acquire a certificate (which is, of course, not free). > Has the community such a certificate? Maybe the same that for MacOS? > Would someone configure the VM builds to automatically sign them? (I can spend some time for this if needed) > > TIA, > > Cheers, > Vincent > > <winmail.dat>

May 15, 2018