- Pharo-dev - lists.pharo.org

IceGenericError: failed to stat file, Pharo LAUNCHER images and long file names on Windows
by Torsten Bergmann April 4, 2019

April 4, 2019

Hi, Windows users of Pharo have been hit by an Iceberg error "IceGenericError: failed to stat file ... The filename or extension is too long" as seen in attached screenshot (for instance when loading Seaside from the original SeasideSt/Seaside master branch). Initially the long filename (who make trouble on Windows according to the message) were blamed - and it was suggested to have Seaside (or other projects) in Tonel format. Johan wanted to try this - but initially it was not possible as Esteban had to provide a fix for the Tonel converter first. This is now available. Following this fix today Johan provided a "tonel" branch of Seaside to check. Roelof Wobben and Mike Davis tried with me on Discord a few combinations and it seems there is a different cause. It seems to be more related to having the image or image path including spaces AND dots. So for instance Pharo Launcher suggests the download of Pharo 7 from the official distribution to be named "Pharo 7.0 - 32bit (stable)". When you just accept the name the Pharo Launcher suggests then you may hit the problem. When you start such an image and try to load the FileTree (master) or Tonel version (tonel branch) of Seaside using Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:master/repository'; load or Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:tonel/repository'; load you will get the error. If you use "Foo" as the name for image it seems to work. Requires some more testing but I guess it is related to the naming in Pharo Launcher with "dots" AND "spaces" instead of the long filenames. "pharo 7.0 (stable)" fails "seaside.test" works "seaside test" works also "seaside. test" works also "seaside-test" works also "seaside(test)" works also Maybe more people can try other combinations on their Windows machines too. If our finding is true it would be good if Laucher on Windows could nuke the dot/space combinations for instance by using underlines. Thanks T. (aka astares)

3 3

[Pharo 8.0] Build #215: 3049-MemoryDirectoryEntry is not compatible to DiskDirectoryEntry regarding #size
by ci-pharo-ci-jenkins2＠inria.fr April 4, 2019

April 4, 2019

There is a new Pharo build available! The status of the build #215 was: SUCCESS. The Pull Request #3052 was integrated: "3049-MemoryDirectoryEntry is not compatible to DiskDirectoryEntry regarding #size" Pull request url: https://github.com/pharo-project/pharo/pull/3052 Issue Url: https://github.com/pharo-project/pharo/issues/3049 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Green tests
by Guillermo Polito April 3, 2019

April 3, 2019

Hi all, In a couple of minutes I've made some (not complicated) fixes to make Rubric tests green again: https://github.com/pharo-project/pharo/pull/3129 This is of course not a super Rubric enhancement (for which I've opened another issue requesting some missing feature https://github.com/pharo-project/pharo/issues/3128) but this allows us to move on with a better infrastructure :). There are still some some tests that fail from time to time, related to system announcers and finalization. See https://github.com/pharo-project/pharo/issues/2471. Though I've spent half a day yesterday and half today trying to track it down, I don't yet have a clear way of reproducing it. I've read the entire code that touches this part of the system and I really bet this is a race condition :). So any second pair of eyes here would really be helpful! Guille

6 9

[Pharo 8.0] Build #214: [test] added a regression test for RBProgramNode >> #propertyAt:ifPresent:ifAbsent:.
by ci-pharo-ci-jenkins2＠inria.fr April 3, 2019

April 3, 2019

There is a new Pharo build available! The status of the build #214 was: FAILURE. The Pull Request #3134 was integrated: "[test] added a regression test for RBProgramNode >> #propertyAt:ifPresent:ifAbsent:. " Pull request url: https://github.com/pharo-project/pharo/pull/3134 Issue Url: https://github.com/pharo-project/pharo/issues/temp Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #213: Simplifying DebugSession>>isContextPostMortem:
by ci-pharo-ci-jenkins2＠inria.fr April 3, 2019

April 3, 2019

There is a new Pharo build available! The status of the build #213 was: FAILURE. The Pull Request #2928 was integrated: "Simplifying DebugSession>>isContextPostMortem:" Pull request url: https://github.com/pharo-project/pharo/pull/2928 Issue Url: https://github.com/pharo-project/pharo/issues/2927 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #212: Improving the performance of SourceFileArray in Pharo8
by ci-pharo-ci-jenkins2＠inria.fr April 2, 2019

April 2, 2019

There is a new Pharo build available! The status of the build #212 was: FAILURE. The Pull Request #3127 was integrated: "Improving the performance of SourceFileArray in Pharo8" Pull request url: https://github.com/pharo-project/pharo/pull/3127 Issue Url: https://github.com/pharo-project/pharo/issues/fixing Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #211: 3119-Failing-test-on-CI-MorphicTextInputFieldAdapterTesttestMaxLengthIsSetInWidget
by ci-pharo-ci-jenkins2＠inria.fr April 2, 2019

April 2, 2019

There is a new Pharo build available! The status of the build #211 was: FAILURE. The Pull Request #3129 was integrated: "3119-Failing-test-on-CI-MorphicTextInputFieldAdapterTesttestMaxLengthIsSetInWidget" Pull request url: https://github.com/pharo-project/pharo/pull/3129 Issue Url: https://github.com/pharo-project/pharo/issues/3119 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #210: 2722-Symbol-should-not-implement-pragmas
by ci-pharo-ci-jenkins2＠inria.fr April 2, 2019

April 2, 2019

There is a new Pharo build available! The status of the build #210 was: FAILURE. The Pull Request #2723 was integrated: "2722-Symbol-should-not-implement-pragmas" Pull request url: https://github.com/pharo-project/pharo/pull/2723 Issue Url: https://github.com/pharo-project/pharo/issues/2722 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #209: 3125-Cleanups-and-improved-ComputedSlot
by ci-pharo-ci-jenkins2＠inria.fr April 2, 2019

April 2, 2019

There is a new Pharo build available! The status of the build #209 was: SUCCESS. The Pull Request #3126 was integrated: "3125-Cleanups-and-improved-ComputedSlot" Pull request url: https://github.com/pharo-project/pharo/pull/3126 Issue Url: https://github.com/pharo-project/pharo/issues/3125 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Pharo Workshops in Switzerland: April 30 to May 3rd
by Marcus Denker April 2, 2019

April 2, 2019

Hi, Kertyx is organising a Workshop Series, the Digital Healthcare Innovation Workshops Part of this series will be a workshop around Pharo: Interactive and efficient ways to build technology stacks for experienced developers. - Where? Lavigny/Switzerland - When? April 30 to May 3 - Event web site: http://kertyx.events â¢ Workshop 1 â Introduction to Pharo (Marcus Denker) â¢ Workshop 2 â Web development using Seaside (Cyril Ferlicot) â¢ Workshop 3 â New Integrated Development Environment (IDE) â Glamorous Toolkit (Tudor Girba) Registration via eventbrite is available for all 3 workshops independently at http://kertyx.events Marcus

1 0