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

Re: [Pharo-dev] Problem with zinc 2.9.2

by Norbert Hartl

> Am 04.07.2018 um 17:52 schrieb Max Leske <maxleske(a)gmail.com>: > > Hi Norbert, > > Where can I get my hands on that image that you say has no sender of #newBinaryFileNamed:do: in it? > I cannot give away the image, sorry. I can try to reproduce it somehow. Do you expect the method to be there? Norbert > Max > >> On 4 Jul 2018, at 17:30, Norbert Hartl wrote: >> >> I tried to see how hard it would be to load my current project in pharo7. Cyril helped me to see that I load an old version of zinc and it does not work that way. Upgrading to zinc 2.9.2 made it work in pharo 7 but my jenkins build do not work anymore. I donât fully understand what is happening. I see in the log >> >> Loading baseline of BaselineOfMobilityMap... >> ...RETRY->BaselineOfParasol >> ...RETRY->BaselineOfParasol[31mMessageNotUnderstood: ZnFileSystemUtils class>>newBinaryFileNamed:do: >> [0mZnFileSystemUtils class(Object)>>doesNotUnderstand: #newBinaryFileNamed:do: >> ZnClient>>downloadEntityTo: >> ZnClient>>downloadTo: >> IceMetacelloPharoPlatform(MetacelloPharoPlatform)>>downloadZipArchive:to: >> >> The strange thing about it is that when I download that image where the error occurred I cannot find a sender of #newBinaryFileNamed:do: and the #downloadEntityTo: does not seem to use it. Downgrading to zinc 2.8.10 makes it work again. >> >> I feel a little bit stupid because the image does not load any new package on startup and still there is this error message which does not make sense to me at all. >> >> Any ideas? >> >> Norbert >

July 4, 2018

Re: [Pharo-dev] Problem with zinc 2.9.2

by Sven Van Caekenberghe

How exactly did you load ? On macOS Pharo-7.0+alpha.build.1099.sha.bcfa81fa7b35214eede30962d35d1d547c199989 (64 Bit) I went to the Catalog and loaded the default stable version. Fetched -> ConfigurationOfZincHTTPComponents-SvenVanCaekenberghe.115 --- http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo70/main/ --- http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo70/main/ Loaded -> ConfigurationOfZincHTTPComponents-SvenVanCaekenberghe.115 --- http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo70/main/ --- http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo70/main/ Loading 2.9.2 of ConfigurationOfZincHTTPComponents... Fetched -> Zodiac-Core-TorstenBergmann.48 --- http://mc.stfx.eu/Zodiac --- http://mc.stfx.eu/Zodiac Fetched -> Zodiac-Tests-SvenVanCaekenberghe.22 --- http://mc.stfx.eu/Zodiac --- http://mc.stfx.eu/Zodiac Fetched -> Zodiac-Extra-SvenVanCaekenberghe.8 --- http://mc.stfx.eu/Zodiac --- http://mc.stfx.eu/Zodiac Fetched -> Zinc-Character-Encoding-Core-SvenVanCaekenberghe.64 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents Fetched -> Zinc-Character-Encoding-Tests-SvenVanCaekenberghe.43 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents Fetched -> Zinc-Resource-Meta-Core-SvenVanCaekenberghe.68 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents Fetched -> Zinc-Resource-Meta-Tests-SvenVanCaekenberghe.38 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents Fetched -> Zinc-FileSystem-SvenVanCaekenberghe.15 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents Fetched -> Zinc-HTTP-SvenVanCaekenberghe.474 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents Fetched -> Zinc-Tests-SvenVanCaekenberghe.245 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents Fetched -> Zinc-Zodiac-SvenVanCaekenberghe.44 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents Fetched -> Zinc-Resource-Meta-FileSystem-SvenVanCaekenberghe.9 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents Loaded -> Zodiac-Core-TorstenBergmann.48 --- http://mc.stfx.eu/Zodiac --- /Users/sven/Develop/Pharo/Pharo-Daily/2018-06-29/pharo-local/package-cache Loaded -> Zodiac-Tests-SvenVanCaekenberghe.22 --- http://mc.stfx.eu/Zodiac --- /Users/sven/Develop/Pharo/Pharo-Daily/2018-06-29/pharo-local/package-cache Loaded -> Zodiac-Extra-SvenVanCaekenberghe.8 --- http://mc.stfx.eu/Zodiac --- /Users/sven/Develop/Pharo/Pharo-Daily/2018-06-29/pharo-local/package-cache Loaded -> Zinc-Character-Encoding-Core-SvenVanCaekenberghe.64 --- http://mc.stfx.eu/ZincHTTPComponents --- cache Loaded -> Zinc-Character-Encoding-Tests-SvenVanCaekenberghe.43 --- http://mc.stfx.eu/ZincHTTPComponents --- cache Loaded -> Zinc-Resource-Meta-Core-SvenVanCaekenberghe.68 --- http://mc.stfx.eu/ZincHTTPComponents --- cache Loaded -> Zinc-Resource-Meta-Tests-SvenVanCaekenberghe.38 --- http://mc.stfx.eu/ZincHTTPComponents --- cache Loaded -> Zinc-FileSystem-SvenVanCaekenberghe.15 --- http://mc.stfx.eu/ZincHTTPComponents --- cache Loaded -> Zinc-HTTP-SvenVanCaekenberghe.474 --- http://mc.stfx.eu/ZincHTTPComponents --- cache Loaded -> Zinc-Tests-SvenVanCaekenberghe.245 --- http://mc.stfx.eu/ZincHTTPComponents --- cache Loaded -> Zinc-Zodiac-SvenVanCaekenberghe.44 --- http://mc.stfx.eu/ZincHTTPComponents --- cache Loaded -> Zinc-Resource-Meta-FileSystem-SvenVanCaekenberghe.9 --- http://mc.stfx.eu/ZincHTTPComponents --- cache ...finished 2.9.2 All unit tests 411 were green. #newBinaryFileNamed:do: can be found on the class side of ZnFileSystemUtils and is used by ZnClient>>#downloadEntityTo: > On 4 Jul 2018, at 17:30, Norbert Hartl <norbert(a)hartl.name> wrote: > > I tried to see how hard it would be to load my current project in pharo7. Cyril helped me to see that I load an old version of zinc and it does not work that way. Upgrading to zinc 2.9.2 made it work in pharo 7 but my jenkins build do not work anymore. I donât fully understand what is happening. I see in the log > > Loading baseline of BaselineOfMobilityMap... > ...RETRY->BaselineOfParasol > ...RETRY->BaselineOfParasol[31mMessageNotUnderstood: ZnFileSystemUtils class>>newBinaryFileNamed:do: > [0mZnFileSystemUtils class(Object)>>doesNotUnderstand: #newBinaryFileNamed:do: > ZnClient>>downloadEntityTo: > ZnClient>>downloadTo: > IceMetacelloPharoPlatform(MetacelloPharoPlatform)>>downloadZipArchive:to: > > > The strange thing about it is that when I download that image where the error occurred I cannot find a sender of #newBinaryFileNamed:do: and the #downloadEntityTo: does not seem to use it. Downgrading to zinc 2.8.10 makes it work again. > > I feel a little bit stupid because the image does not load any new package on startup and still there is this error message which does not make sense to me at all. > > Any ideas? > > Norbert

July 4, 2018

Re: [Pharo-dev] Problem with zinc 2.9.2

by Max Leske

Hi Norbert, Where can I get my hands on that image that you say has no sender of #newBinaryFileNamed:do: in it? Max On 4 Jul 2018, at 17:30, Norbert Hartl wrote: > I tried to see how hard it would be to load my current project in > pharo7. Cyril helped me to see that I load an old version of zinc and > it does not work that way. Upgrading to zinc 2.9.2 made it work in > pharo 7 but my jenkins build do not work anymore. I donât fully > understand what is happening. I see in the log > > Loading baseline of BaselineOfMobilityMap... > ...RETRY->BaselineOfParasol > ...RETRY->BaselineOfParasol[31mMessageNotUnderstood: > ZnFileSystemUtils class>>newBinaryFileNamed:do: > [0mZnFileSystemUtils class(Object)>>doesNotUnderstand: > #newBinaryFileNamed:do: > ZnClient>>downloadEntityTo: > ZnClient>>downloadTo: > IceMetacelloPharoPlatform(MetacelloPharoPlatform)>>downloadZipArchive:to: > > The strange thing about it is that when I download that image where > the error occurred I cannot find a sender of #newBinaryFileNamed:do: > and the #downloadEntityTo: does not seem to use it. Downgrading to > zinc 2.8.10 makes it work again. > > I feel a little bit stupid because the image does not load any new > package on startup and still there is this error message which does > not make sense to me at all. > > Any ideas? > > Norbert

July 4, 2018

[ANN] New Academic Partner: University of YaoundÃ© 1

by Marcus Denker

The Pharo Consortium is very happy to announce that University of YaoundÃ© 1 has joined as a Academic Partner. About - University of YaoundÃ© 1: http://www.uy1.uninet.cm - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: http://association.pharo.org

July 4, 2018

Problem with zinc 2.9.2

by Norbert Hartl

I tried to see how hard it would be to load my current project in pharo7. Cyril helped me to see that I load an old version of zinc and it does not work that way. Upgrading to zinc 2.9.2 made it work in pharo 7 but my jenkins build do not work anymore. I donât fully understand what is happening. I see in the log Loading baseline of BaselineOfMobilityMap... ...RETRY->BaselineOfParasol ...RETRY->BaselineOfParasol[31mMessageNotUnderstood: ZnFileSystemUtils class>>newBinaryFileNamed:do: [0mZnFileSystemUtils class(Object)>>doesNotUnderstand: #newBinaryFileNamed:do: ZnClient>>downloadEntityTo: ZnClient>>downloadTo: IceMetacelloPharoPlatform(MetacelloPharoPlatform)>>downloadZipArchive:to: The strange thing about it is that when I download that image where the error occurred I cannot find a sender of #newBinaryFileNamed:do: and the #downloadEntityTo: does not seem to use it. Downgrading to zinc 2.8.10 makes it work again. I feel a little bit stupid because the image does not load any new package on startup and still there is this error message which does not make sense to me at all. Any ideas? Norbert

July 4, 2018

Re: [Pharo-dev] Promote new Pharo 7 VM?

by Esteban Lorenzano

> On 4 Jul 2018, at 17:06, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Esteban, > > On Wed, 4 Jul 2018 at 10:08, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> youâre right :) > > Thanks for promoting the VM! > > Just a question about the release process: > > The VM I requested be promoted two weeks ago was dated June 17, hash 140ff02. > > The VM you promoted is dated June 28, hash a8a1dc1. So it obviously > hasn't been there for the two week period. > > Is this what you intended, or should 140ff02 have been released now, > and a8a1dc1 next week? > > I'm not suggesting you pull the VM, I've been using it for the last 6 > days without any problems, and there have been successful CI builds > today, I'm just trying to confirm my understanding. ouch. I made a mistake, obviously (I was distracted when checking the reference) but ok, let's roll with it. :P stable for 6.1 will be this one too (when validated). cheers, Esteban > > Thanks again, > Alistair > > > > >>> On 3 Jul 2018, at 13:55, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>> >>> Hi Esteban, >>> >>> On Mon, 18 Jun 2018 at 23:15, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> >>>> yes, why not :) >>>> but, remember the cycle: >>>> >>>> 1. two weeks in latest (that starts today) >>> >>> Just a friendly reminder that the two weeks is done... :-) >>> >>> Thanks, >>> Alistair >>> >>> >>>> 2. one month in stable 7.0 >>>> 3. promote to stable 6.1 >>>> >>>> yes, is annoying, but is the scheme has worked the better to avoid problems. >>>> >>>> cheers, >>>> Esteban >>>> >>>>> On 18 Jun 2018, at 14:20, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>>>> >>>>> Hi Esteban, >>>>> >>>>> Would you consider promoting a new Pharo 7 VM? >>>>> >>>>> 140ff02 should finally solve an issue I've had with time zones and DST >>>>> on Windows in the FileAttributesPlugin. >>>>> >>>>> Testing I've done on this VM: >>>>> >>>>> - Loaded up and used my normal dev environment. >>>>> - Run the full automated test suite on: >>>>> -- Linux 64 bit >>>>> -- Linux 32 bit >>>>> -- Win 32 bit >>>>> >>>>> In each case the set of failures in my environment roughly aligns with >>>>> the current stable VM and the proposed one. >>>>> >>>>> I guess if anyone else has any objections they'll reply to this. :-) >>>>> >>>>> Of course, if you've got any questions or concerns, please let me know. >>>>> >>>>> In case it is useful for anyone, download links are: >>>>> >>>>> Linux 64 bit: http://files.pharo.org/vm/pharo-spur64/linux/pharo-linux-x86_64threaded-201… >>>>> Linux 32 bit: http://files.pharo.org/vm/pharo-spur32/linux/pharo-linux-i386threaded-20180… >>>>> Mac 64 bit: >>>>> - http://files.pharo.org/vm/pharo-spur64/mac/pharo-mac-x86_64-201806171702-14… >>>>> - http://files.pharo.org/vm/pharo-spur64/mac/pharo-mac-x86_64-201806171702-14… >>>>> Mac 32 bit: >>>>> - http://files.pharo.org/vm/pharo-spur32/mac/pharo-mac-i386-201806171702-140f… >>>>> - http://files.pharo.org/vm/pharo-spur32/mac/pharo-mac-i386-201806171702-140f… >>>>> Win 32 bit: http://files.pharo.org/vm/pharo-spur32/win/pharo-win-i386-201806171702-140f… >>>>> >>>>> >>>>> Thanks! >>>>> Alistair >>>>> >>>> >>>> >>> >> >> >

July 4, 2018

Re: [Pharo-dev] Promote new Pharo 7 VM?

by Alistair Grant

Hi Esteban, On Wed, 4 Jul 2018 at 10:08, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > youâre right :) Thanks for promoting the VM! Just a question about the release process: The VM I requested be promoted two weeks ago was dated June 17, hash 140ff02. The VM you promoted is dated June 28, hash a8a1dc1. So it obviously hasn't been there for the two week period. Is this what you intended, or should 140ff02 have been released now, and a8a1dc1 next week? I'm not suggesting you pull the VM, I've been using it for the last 6 days without any problems, and there have been successful CI builds today, I'm just trying to confirm my understanding. Thanks again, Alistair > > On 3 Jul 2018, at 13:55, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > > > Hi Esteban, > > > > On Mon, 18 Jun 2018 at 23:15, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> > >> yes, why not :) > >> but, remember the cycle: > >> > >> 1. two weeks in latest (that starts today) > > > > Just a friendly reminder that the two weeks is done... :-) > > > > Thanks, > > Alistair > > > > > >> 2. one month in stable 7.0 > >> 3. promote to stable 6.1 > >> > >> yes, is annoying, but is the scheme has worked the better to avoid problems. > >> > >> cheers, > >> Esteban > >> > >>> On 18 Jun 2018, at 14:20, Alistair Grant <akgrant0710(a)gmail.com> wrote: > >>> > >>> Hi Esteban, > >>> > >>> Would you consider promoting a new Pharo 7 VM? > >>> > >>> 140ff02 should finally solve an issue I've had with time zones and DST > >>> on Windows in the FileAttributesPlugin. > >>> > >>> Testing I've done on this VM: > >>> > >>> - Loaded up and used my normal dev environment. > >>> - Run the full automated test suite on: > >>> -- Linux 64 bit > >>> -- Linux 32 bit > >>> -- Win 32 bit > >>> > >>> In each case the set of failures in my environment roughly aligns with > >>> the current stable VM and the proposed one. > >>> > >>> I guess if anyone else has any objections they'll reply to this. :-) > >>> > >>> Of course, if you've got any questions or concerns, please let me know. > >>> > >>> In case it is useful for anyone, download links are: > >>> > >>> Linux 64 bit: http://files.pharo.org/vm/pharo-spur64/linux/pharo-linux-x86_64threaded-201… > >>> Linux 32 bit: http://files.pharo.org/vm/pharo-spur32/linux/pharo-linux-i386threaded-20180… > >>> Mac 64 bit: > >>> - http://files.pharo.org/vm/pharo-spur64/mac/pharo-mac-x86_64-201806171702-14… > >>> - http://files.pharo.org/vm/pharo-spur64/mac/pharo-mac-x86_64-201806171702-14… > >>> Mac 32 bit: > >>> - http://files.pharo.org/vm/pharo-spur32/mac/pharo-mac-i386-201806171702-140f… > >>> - http://files.pharo.org/vm/pharo-spur32/mac/pharo-mac-i386-201806171702-140f… > >>> Win 32 bit: http://files.pharo.org/vm/pharo-spur32/win/pharo-win-i386-201806171702-140f… > >>> > >>> > >>> Thanks! > >>> Alistair > >>> > >> > >> > > > >

July 4, 2018

Re: [Pharo-dev] [ANN] New Academic Partner: SQLab

by Ben Coman

On 4 July 2018 at 17:29, Marcus Denker <marcus.denker(a)inria.fr> wrote: > The Pharo Consortium is very happy to announce that SQLab has joined as a > Academic Partner. > > About > - Software Quality Laboratory, Part of University of Novi Sad: > https://sqlab.pmf.uns.ac.rs > - Pharo Consortium: http://consortium.pharo.org > > The goal of the Pharo Consortium is to allow companies and institutions to > support the ongoing development and future of Pharo. > > Individuals can support Pharo via the Pharo Association: > > http://association.pharo.org Great to hear of more academic exposure. cheers -ben

July 4, 2018

[ANN] New window tiling shortcuts

by Pavel Krivanek

Hello, the latest Pharo 7 includes new window tiling shortcuts that should help you to manage windows position and size without the need of using a mouse. In this description, the key â has equivalent in Ctrl on Linux and Windows. I need to notice that some nicer key combinations would be chosen if the VM support of key modifiers would be proper on all platforms but that is a different story... Windows tiling ------------------------ â+Shift+W, A - move the window to the left half of the screen. â+Shift+W, D - right half â+Shift+W, W - top half â+Shift+W, X - bottom half â+Shift+W, Q - move the window to the top left quadrant of the screen â+Shift+W E - top right quadrant â+Shift+W, Z - bottom left quadrant â+Shift+W, C - bottom right quadrant â+Shift+W, S - maximize the window â+Shift+W, Shift+S - minimize the window â+Shift+W, R - centre the window on the screen with a default extent Windows moving ------------------------ â+Shift+W, â - move the window left by half of its width â+Shift+W, â - move the window right by half of its width â+Shift+W, â - move the window up by half of its height â+Shift+W, â - move the window down by half of its height Windows resizing ------------------------ â+Shift+W, hold â+Shift and press: A, A - move left window edge left (by half of the window size) A, S - move left window edge right (by half of the window size) W, W - move top edge up W, S - move top edge down D, D - move right edge right D, S - move right edge left X, X - move bottom edge down X, S - move bottom edge up Cheers, -- Pavel

July 4, 2018

[Pharo 7.0-dev] Build #1113: 22232 the test runner should allow to do code coverage on packages having test in the their name

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

There is a new Pharo build available! The status of the build #1113 was: SUCCESS. The Pull Request #1616 was integrated: "22232 the test runner should allow to do code coverage on packages having test in the their name" Pull request url: https://github.com/pharo-project/pharo/pull/1616 Issue Url: https://pharo.fogbugz.com/f/cases/22232 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 4, 2018