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

[Pharo 7.0-dev] Build #1396: 22659-generated-artifacts-should-have-the-version-tag (addendum to the addendum)
by ci-pharo-ci-jenkins2＠inria.fr Nov. 14, 2018

Nov. 14, 2018

There is a new Pharo build available! The status of the build #1396 was: FAILURE. The Pull Request #1991 was integrated: "22659-generated-artifacts-should-have-the-version-tag (addendum to the addendum)" Pull request url: https://github.com/pharo-project/pharo/pull/1991 Issue Url: https://pharo.fogbugz.com/f/cases/22659 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1395: 22659-generated-artifacts-should-have-the-version-tag (addendum)
by ci-pharo-ci-jenkins2＠inria.fr Nov. 14, 2018

Nov. 14, 2018

There is a new Pharo build available! The status of the build #1395 was: FAILURE. The Pull Request #1990 was integrated: "22659-generated-artifacts-should-have-the-version-tag (addendum)" Pull request url: https://github.com/pharo-project/pharo/pull/1990 Issue Url: https://pharo.fogbugz.com/f/cases/22659 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1394: 22659-generated-artifacts-should-have-the-version-tag (definitive compilation)
by ci-pharo-ci-jenkins2＠inria.fr Nov. 14, 2018

Nov. 14, 2018

There is a new Pharo build available! The status of the build #1394 was: FAILURE. The Pull Request #1989 was integrated: "22659-generated-artifacts-should-have-the-version-tag (definitive compilation)" Pull request url: https://github.com/pharo-project/pharo/pull/1989 Issue Url: https://pharo.fogbugz.com/f/cases/22659 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Debugger "Through" acting like "Into"
by Martin McClure Nov. 14, 2018

Nov. 14, 2018

In the latest Pharo 7 (Pharo-7.0.0+rc1.build.1384.sha.c34d6a69d9d01a2816df1f9fdc7388580163df29 (32 Bit)) it seems like clicking "Through" in the debugger often (but not always) has the effect of "Into", which seems wrong and makes stepping through code difficult. I don't know how new this behavior is. Is this a known behavior? If not, I'll characterize it further. Regards, -Martin

2 1

How do I create a binary stream
by Stephane Ducasse Nov. 13, 2018

Nov. 13, 2018

Hi I'm checking some of the mooc code in Pharo 70. The Pharo 50/60 version is PNGReadWriter createAFormFrom: 'Sprites.png' asFileReference binaryReadStream upToEnd I came up with PNGReadWriter formFromStream: (File named: 'Sprites.png') readStream And we can also have PNGReadWriter formFromStream: 'Sprites.png' asFileReference binaryReadStream I will add this in the comment of the formFromStream: method. Stef

4 11

[Pharo 7.0-dev] Build #1393: 22659-generated-artifacts-should-have-the-version-tag (V5)
by ci-pharo-ci-jenkins2＠inria.fr Nov. 13, 2018

Nov. 13, 2018

There is a new Pharo build available! The status of the build #1393 was: FAILURE. The Pull Request #1987 was integrated: "22659-generated-artifacts-should-have-the-version-tag (V5)" Pull request url: https://github.com/pharo-project/pharo/pull/1987 Issue Url: https://pharo.fogbugz.com/f/cases/22659 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1392: 22659-generated-artifacts-should-have-the-version-tag (V4)
by ci-pharo-ci-jenkins2＠inria.fr Nov. 13, 2018

Nov. 13, 2018

There is a new Pharo build available! The status of the build #1392 was: FAILURE. The Pull Request #1986 was integrated: "22659-generated-artifacts-should-have-the-version-tag (V4)" Pull request url: https://github.com/pharo-project/pharo/pull/1986 Issue Url: https://pharo.fogbugz.com/f/cases/22659 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1391: 22659-generated-artifacts-should-have-the-version-tag (V3)
by ci-pharo-ci-jenkins2＠inria.fr Nov. 13, 2018

Nov. 13, 2018

There is a new Pharo build available! The status of the build #1391 was: FAILURE. The Pull Request #1984 was integrated: "22659-generated-artifacts-should-have-the-version-tag (V3)" Pull request url: https://github.com/pharo-project/pharo/pull/1984 Issue Url: https://pharo.fogbugz.com/f/cases/22659 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1390: 22659-generated-artifacts-should-have-the-version-tag (V2)
by ci-pharo-ci-jenkins2＠inria.fr Nov. 13, 2018

Nov. 13, 2018

There is a new Pharo build available! The status of the build #1390 was: FAILURE. The Pull Request #1983 was integrated: "22659-generated-artifacts-should-have-the-version-tag (V2)" Pull request url: https://github.com/pharo-project/pharo/pull/1983 Issue Url: https://pharo.fogbugz.com/f/cases/22659 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1389: 22659-generated-artifacts-should-have-the-version-tag (V2)
by ci-pharo-ci-jenkins2＠inria.fr Nov. 13, 2018

Nov. 13, 2018

There is a new Pharo build available! The status of the build #1389 was: FAILURE. The Pull Request #1983 was integrated: "22659-generated-artifacts-should-have-the-version-tag (V2)" Pull request url: https://github.com/pharo-project/pharo/pull/1983 Issue Url: https://pharo.fogbugz.com/f/cases/22659 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0