October 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Launcher: VM Problem

by Sean P. DeNigris

Aha! I just had to change {imageFolder}/pharo.version to from `06` to `61` ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 20, 2017

Re: [Pharo-dev] Launcher: VM Problem

by Cyril Ferlicot D.

Le 20/10/2017 Ã 20:51, Sean P. DeNigris a Ã©critÂ : > I have a recent working VM in ~/Documents/Pharo/vms/60. Instead of using it, > the last Launcher release downloaded another one to > ~/Documents/Pharo/vms/60-x86. However, this seems to be an older one which > does not support Iceberg (I get a message about outdated libgit). Per the > System Reporter: > > ~/Documents/Pharo/vms/60-x86/Pharo.app/Contents/MacOS/Pharo > CoInterpreter VMMaker.oscog-eem.2231 uuid: > de62947a-7f40-4977-a232-e06a3a80c939 May 31 2017 > StackToRegisterMappingCogit VMMaker.oscog-eem.2227 uuid: > 7ea146b4-39ce-4de7-afa3-a76ed1d1da35 May 31 2017 > VM: 201705310241 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > Date: Tue May 30 19:41:27 2017 -0700 $ Plugins: 201705310241 > https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > Are you sure you launch a Pharo 6.1 image and not a Pharo 6.0 image? Pharo 6.0 -> build number < 60509 Pharo 6.1 -> build number >= 60509 IIRC. > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Oct. 20, 2017

Launcher: VM Problem

by Sean P. DeNigris

I have a recent working VM in ~/Documents/Pharo/vms/60. Instead of using it, the last Launcher release downloaded another one to ~/Documents/Pharo/vms/60-x86. However, this seems to be an older one which does not support Iceberg (I get a message about outdated libgit). Per the System Reporter: ~/Documents/Pharo/vms/60-x86/Pharo.app/Contents/MacOS/Pharo CoInterpreter VMMaker.oscog-eem.2231 uuid: de62947a-7f40-4977-a232-e06a3a80c939 May 31 2017 StackToRegisterMappingCogit VMMaker.oscog-eem.2227 uuid: 7ea146b4-39ce-4de7-afa3-a76ed1d1da35 May 31 2017 VM: 201705310241 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Tue May 30 19:41:27 2017 -0700 $ Plugins: 201705310241 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 20, 2017

Re: [Pharo-dev] Some segfault crashes and freezes when trying to re-run saved pharo 7 images

by ClÃ©ment Bera

Hi, As you can see in the crash dump, this is always due to FreeType. If it's only at start-up it means it's in the FreeType start-up code. You can try to change some free type settings (like not using those fonts at all) or to use more hard-core scripts such as: #(FT2Handle FreeTypeCache FreeTypeSettings) do: [ :each | SessionManager default unregisterClassNamed: each ] On Fri, Oct 20, 2017 at 5:50 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > I've experienced the same thing on Windows 10 yesterday, but normally I do > not work in P7 so I didn't investigate much. > > On Fri, Oct 20, 2017 at 3:57 PM, Thomas Dupriez <thomas.dupriez@ens-paris- > saclay.fr> wrote: > >> Hello, >> >> I've had a few issues with Pharo 7 lately. After downloading pharo 7 >> images, doing some work in them and saving them, the images either >> instantly crashe or freeze when I try to re-run them. >> If that helps, I was working with and on the calypso browser. >> >> Attached are the crash dump files from some of these faulty images. >> >> vm version: 201708271955 >> image version: 6521 >> OS: Ubuntu 16.04 LTS >> >> Cheers, >> Thomas >> >> > -- ClÃ©ment BÃ©ra Pharo consortium engineer https://clementbera.wordpress.com/ BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq

Oct. 20, 2017

[Pharo 7.0-dev] Build #216: 20471-Tests-for-Unicode-Categories-are-missing

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

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

Oct. 20, 2017

Re: [Pharo-dev] Some segfault crashes and freezes when trying to re-run saved pharo 7 images

by Peter UhnÃ¡k

I've experienced the same thing on Windows 10 yesterday, but normally I do not work in P7 so I didn't investigate much. On Fri, Oct 20, 2017 at 3:57 PM, Thomas Dupriez < thomas.dupriez(a)ens-paris-saclay.fr> wrote: > Hello, > > I've had a few issues with Pharo 7 lately. After downloading pharo 7 > images, doing some work in them and saving them, the images either > instantly crashe or freeze when I try to re-run them. > If that helps, I was working with and on the calypso browser. > > Attached are the crash dump files from some of these faulty images. > > vm version: 201708271955 > image version: 6521 > OS: Ubuntu 16.04 LTS > > Cheers, > Thomas > >

Oct. 20, 2017

RES: Anoying bug fond in Artefact running in Windows 10

by casimiro.barreto＠gmail.com

But it seems that the problem is either with OSWindows or OSProcess (I guess Artefact uses OSProcess) because the windows side of things just is not aware that task is complete and it must finish things, close streams, etcâ¦ Because you seeâ¦ in the Pharo side I even closed the file descriptor (explicitly). Best regards, Casimiro De: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] Em nome de olivier auverlot Enviada em: sexta-feira, 20 de outubro de 2017 03:40 Para: Pharo Development List <pharo-dev(a)lists.pharo.org> Assunto: Re: [Pharo-dev] Anoying bug fond in Artefact running in Windows 10 Hi Casimiro, Which version of Pharo do you use ? 6.1 ? Olivier :) 2017-10-19 18:27 GMT+02:00 <casimiro.barreto(a)gmail.com <mailto:casimiro.barreto@gmail.com> >: When you insert a jpeg from a file, for some reason the file descriptor (stream) is kept open (at least in the Windows end of things). Then, if a second page is to be generated, the following error is shown: 'MessageNotUnderstood: receiver of "reset" is nil PDFJpegElement>>stream: JPEGReadWriter aJPEGReadWriter JPEGReadWriter(ImageReadWriter)>>on: nil Sample code: aPage := PDFPage new. imageStream := FileStream fileNamed: 'lsi-tec.jpg'. aPage add: ((PDFJpegElement fromStream: imageStream) from: 15 mm @ 20 mm; dimension: 40 mm @ 40 mm). imageStream close. Generated report is in annex The only way to recover is to close pharo, start it again. Then the file descriptor (stream) is released and it is possible to go on. Has anyone faced this problem? How to solve it? Best regards, Casimiro Barreto

Oct. 20, 2017

RES: Anoying bug fond in Artefact running in Windows 10

by casimiro.barreto＠gmail.com

Interesting enoughâ¦ I have installed Pharo6.1 (Windows). But then I go System>>about it returns Pharo 6.0 Latest update: #60511 De: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] Em nome de olivier auverlot Enviada em: sexta-feira, 20 de outubro de 2017 03:40 Para: Pharo Development List <pharo-dev(a)lists.pharo.org> Assunto: Re: [Pharo-dev] Anoying bug fond in Artefact running in Windows 10 Hi Casimiro, Which version of Pharo do you use ? 6.1 ? Olivier :)

Oct. 20, 2017

[Pharo 7.0-dev] Build #215: 19105-Default-time-limit-for-tests-should-be-really-small

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

There is a new Pharo build available! The status of the build #215 was: SUCCESS. The Pull Request #71 was integrated: "19105-Default-time-limit-for-tests-should-be-really-small" Pull request url: https://github.com/pharo-project/pharo/pull/71 Issue Url: https://pharo.fogbugz.com/f/cases/19105 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 20, 2017

Re: [Pharo-dev] Github API on github

by Sean P. DeNigris

Denis Kudriashov wrote > Thank's Guille. > That's nice. I like small reusable libraries. +1 ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 20, 2017