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

[Pharo 7.0-dev] Build #800: 20020-Collectionaverage-throw-a-ZeroDivide-when-the-collection-is-empty
by ci-pharo-ci-jenkins2＠inria.fr April 23, 2018

April 23, 2018

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

1 0

[Pharo 7.0-dev] Build #799: 21597 Deprecate initialColorInSystemWindow: as it has no sender
by ci-pharo-ci-jenkins2＠inria.fr April 23, 2018

April 23, 2018

There is a new Pharo build available! The status of the build #799 was: SUCCESS. The Pull Request #1123 was integrated: "21597 Deprecate initialColorInSystemWindow: as it has no sender" Pull request url: https://github.com/pharo-project/pharo/pull/1123 Issue Url: https://pharo.fogbugz.com/f/cases/21597 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

'Contribute a fix to Pharo' for new Iceberg ?
by Sven Van Caekenberghe April 23, 2018

April 23, 2018

Hi, I got the new Iceberg working on the latest Pharo 7 (used it to commit something to P3) - authentication should be OK then I guess. It feels much better. I would like to try contributing to Pharo again. Has https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo been updated for the new Iceberg ? Have things become simpler ? I also forgot the easy/short git command to bring my fork up to date (if I have to do this myself). Sven

4 6

Using P3 to connect to CockroachDB
by Sven Van Caekenberghe April 23, 2018

April 23, 2018

Hi, Just a quick note: it is possible to use P3 (the lean and mean PostgreSQL client for Pharo using frontend/backend protocol 3.0, https://github.com/svenvc/P3) to connect to CockroachDB (an SQL database for global cloud services, an open source clone of Google Spannner, https://www.cockroachlabs.com) as it supports the same line protocol. Just make sure to load the latest version of P3 (and ZTimestamp when you are on Pharo 7). If you do their tutorial, you can set up your connection as follows: P3Client url: 'psql://root@localhost:26257/bank'. Sven

2 1

[Pharo 7.0-dev] Build #798: 21762-The-System-browser-world-menu-registration-should-be-done-in-Tool-Base-package
by ci-pharo-ci-jenkins2＠inria.fr April 23, 2018

April 23, 2018

There is a new Pharo build available! The status of the build #798 was: SUCCESS. The Pull Request #1242 was integrated: "21762-The-System-browser-world-menu-registration-should-be-done-in-Tool-Base-package" Pull request url: https://github.com/pharo-project/pharo/pull/1242 Issue Url: https://pharo.fogbugz.com/f/cases/21762 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #797: 21744-load-the-Deprecated70-as-the-very-latest-package
by ci-pharo-ci-jenkins2＠inria.fr April 23, 2018

April 23, 2018

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

1 0

[Pharo 7.0-dev] Build #796: 21761-change-asDoItIn-to-asDoItForContext
by ci-pharo-ci-jenkins2＠inria.fr April 23, 2018

April 23, 2018

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

2 1

[Pharo 7.0-dev] Build #795: 21761-change-asDoItIn-to-asDoItForContext
by ci-pharo-ci-jenkins2＠inria.fr April 23, 2018

April 23, 2018

There is a new Pharo build available! The status of the build #795 was: FAILURE. The Pull Request #1241 was integrated: "21761-change-asDoItIn-to-asDoItForContext" Pull request url: https://github.com/pharo-project/pharo/pull/1241 Issue Url: https://pharo.fogbugz.com/f/cases/21761 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #794: 21753-Integrate-Calypso-0112
by ci-pharo-ci-jenkins2＠inria.fr April 23, 2018

April 23, 2018

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

1 0

learning about ClassTestCase
by Ben Coman April 22, 2018

April 22, 2018

I bumped into ClassTestCase for the first time, with class comment... "This class is intended for unit tests of individual classes and their metaclasses. It provides methods to determine the coverage of the unit tests. Subclasses are expected to re-implement: #classesToBeTested and #selectorsToBeIgnored. They should also implement to confirm that all methods have been tested. #testCoverage super testCoverage. " A few questions to improve my knowledge of how to use this... a. there are no implementors of #classesToBeTested but several of #classToBeTested. I presume the class comment is wrong? b. there are no implementors of #testCoverage, so I presume I can ignore that? (and I've no example to work from) c. ClassTestCase is subclassed 73 times, but #selectorsToBeIgnored is only implemented 9 times. So this seems not critical? But btw, every of those at least ignores #printOn:. I'm curious why? These are tagged "private", but is that a good reason not to test it? My purpose was to add a new class MagnitudeTest for a new new method to Magnitude in response to the recent #min:max: discussion. cheers -ben

2 2