March 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [Pharo-dev] New version of Pillar

by stepharong

I made - a new pharo 50 with lightPhaser as version 1.0 and not bleeding edge. - then on pharo 60 now we have 4.0.9 with the fixes of doru next the command line fixes of Maxime. We will finish to get agile :) Stef > :) thanks Stef and Maxime. > > On Wed, Mar 8, 2017 at 10:47 AM, Stephane Ducasse > <stepharo.self(a)gmail.com> wrote: >> Hi >> We are happy to announce a new version of Pillar for Pharo 50 and 60. >> Thanks Maxime Roelandt for the help. >> Features - Now we can rebuild the mooc slides (the metadata is >> correctly handled) >> - The double walking of the tree fixes by Yann Dubois is integrated. >> - We checked and we can produce HTML, books and slides >> >> The version 4.0.7 will be the last stable version for Pharo 50. >> On Pharo 60 we will start a large cleaning. Here is the list: >> >> > -- Using Opera's mail client: http://www.opera.com/mail/

March 8, 2017

Re: [Pharo-users] Seaside memory leaks ?

by stepharong

Annick Hello I hope that you are going well. Let me help you getting an ansver.... which version of seaside? which version of Pharo? which OS? which VM are you using? without such information I think that people will not even try to react. We can accept that from students but not from pro people looking for help. Stef > Hi, > > Has anybody investigated whether Seaside has memory leaks using Jquery ? > I have suspicions about dirty blocks holding variables â¦ > I crashed my server with 170 000 connections... > Annick -- Using Opera's mail client: http://www.opera.com/mail/

March 8, 2017

Re: [Pharo-users] Pharo Spur 64 VM

by raffaello.giulietti＠lifeware.ch

On 08/03/17 18:08, Peter Uhnak wrote: > On Tue, Mar 07, 2017 at 10:20:10AM +0100, Raffaello Giulietti wrote: > >> probably most of the developers related to Pharo use macOS > > Last time (~two years ago) I asked it was about ~1/3 each platform http://www.strawpoll.me/4001583/r > (also I didn't make a distinction between desktop and server, so win/mac would be even higher) > here's the original thread: http://forum.world.st/quick-poll-which-OS-do-you-use-for-Pharo-td4816222.ht… > Interesting! The figures for Windows are rather surprising, although from the overall results it's hard to distinguish between developer's and other kind of usages. > Maybe Marcus knows download rates from files.pharo.org (although this will be heavily skewed by build systems). > Download rates can be misleading, though. How many software products are installed and used just to play around a bit and then never used again? Tons, I guess. > I would argue that its simply easier to find Mac/Linux low-level experts and contributors than Windows as the developer culture (including OSS and contributions) is different. > Yes, I agree that as a developer, for many reasons, chances are that life is usually easier on Unix-like systems than on Windows. > Peter > >> >> >> >> On 2017-03-07 04:58, HernÃ¡n Morales Durand wrote: >>> Just asking, >>> >>> Did someone already tried to get funding to update the Windows VM? >>> Because it's like the 90% of the world still uses Windows... >>> >>> Regards, >>> >>> HernÃ¡n >>> >>> >>> >>> 2017-03-02 12:51 GMT-03:00 ClÃ©ment Bera <bera.clement(a)gmail.com >>> <mailto:bera.clement@gmail.com>>: >>> >>> Hi Raffaello, >>> >>> Reportedly, the VM without the JIT (pure interpreter, also called >>> PharoS or StackVM) works on windows 64 and FFI works with it if >>> the VM compiled with clang but not with gcc. There is no >>> configuration for Pharo right now. It should not be hard to add a >>> pharo configuration to have the image start-up, but I don't think >>> several libraries such as Athens/Cairo or libgit would work out of >>> the box, so it's not clear such a configuration would make a lot >>> of sense. There is no PharoS-spur64 repository on files.pharo.org >>> <http://files.pharo.org> right now either. >>> >>> Windows support is not ready mostly because: >>> - Some C types are different in x64 between Unix and windows >>> - Calling conventions are different in x64 bits between Unix and >>> Windows >>> >>> Calling conventions have impact in switching between the >>> interpreter and the JIT runtime and in FFI. >>> C types being different have impact for the VM compilation and in FFI. >>> >>> If someone looks into it, I guess in a day of work we could have >>> the Stack VM working with Spur 64 for Pharo without support for >>> some librairies. There might be uncommon crashes to fix over the >>> first week of use. With several more weeks of work (maybe a couple >>> months), the StackVM with all libraries should be >>> production-ready. The JIT support will take more time, hopefully >>> it will be done in a year from now. >>> >>> Maybe I should mention that the company who funded 64 bits support >>> is using the VM on Mac for development and Linux for production, >>> so Windows was not a priority and not done. We have to rely on >>> open-source contributors, non paid, to add Windows support and >>> that takes time. Nicolas Cellier added the support for the 64 bits >>> Stack VM on his free time. If someone is investing money, the 64 >>> bits Windows VM could reach production sooner (I guess within 6 >>> months) because someone could work full time on it. >>> >>> Regards, >>> >>> On Thu, Mar 2, 2017 at 4:04 PM, <raffaello.giulietti(a)lifeware.ch >>> <mailto:raffaello.giulietti@lifeware.ch>> wrote: >>> >>> On 07/02/17 07:13, Esteban Lorenzano wrote: >>> > >>> >> On 6 Feb 2017, at 21:41, Cyril Ferlicot D. >>> <cyril.ferlicot(a)gmail.com <mailto:cyril.ferlicot@gmail.com>> >>> wrote: >>> >> >>> >> Le 06/02/2017 Ã 21:31, Benoit St-Jean via Pharo-users a Ã©crit : >>> >> >>> >> >>> >> Hi! >>> >> >>> >> IIRC, the windows VM will need some more time to be ready. >>> Only Linux >>> >> and OSX ones are usable at the moment. >>> > >>> > ^ this. >>> > as Cyril says, win 64bits vm is still not ready (and it will >>> take some more time to be). >>> > >>> > Esteban >>> > >>> >>> >>> Just for general curiosity, what are the main stumbling blocks >>> in the >>> road to a Windows 64 bit Pharo? >>> >>> >>> Raffaello >>> >>> >>> >>> >> >

March 8, 2017

Re: [Pharo-users] Pharo Spur 64 VM

by Peter Uhnak

On Tue, Mar 07, 2017 at 10:20:10AM +0100, Raffaello Giulietti wrote: > probably most of the developers related to Pharo use macOS Last time (~two years ago) I asked it was about ~1/3 each platform http://www.strawpoll.me/4001583/r (also I didn't make a distinction between desktop and server, so win/mac would be even higher) here's the original thread: http://forum.world.st/quick-poll-which-OS-do-you-use-for-Pharo-td4816222.ht… Maybe Marcus knows download rates from files.pharo.org (although this will be heavily skewed by build systems). I would argue that its simply easier to find Mac/Linux low-level experts and contributors than Windows as the developer culture (including OSS and contributions) is different. Peter > > > > On 2017-03-07 04:58, HernÃ¡n Morales Durand wrote: > >Just asking, > > > >Did someone already tried to get funding to update the Windows VM? > >Because it's like the 90% of the world still uses Windows... > > > >Regards, > > > >HernÃ¡n > > > > > > > >2017-03-02 12:51 GMT-03:00 ClÃ©ment Bera <bera.clement(a)gmail.com > ><mailto:bera.clement@gmail.com>>: > > > > Hi Raffaello, > > > > Reportedly, the VM without the JIT (pure interpreter, also called > > PharoS or StackVM) works on windows 64 and FFI works with it if > > the VM compiled with clang but not with gcc. There is no > > configuration for Pharo right now. It should not be hard to add a > > pharo configuration to have the image start-up, but I don't think > > several libraries such as Athens/Cairo or libgit would work out of > > the box, so it's not clear such a configuration would make a lot > > of sense. There is no PharoS-spur64 repository on files.pharo.org > > <http://files.pharo.org> right now either. > > > > Windows support is not ready mostly because: > > - Some C types are different in x64 between Unix and windows > > - Calling conventions are different in x64 bits between Unix and > > Windows > > > > Calling conventions have impact in switching between the > > interpreter and the JIT runtime and in FFI. > > C types being different have impact for the VM compilation and in FFI. > > > > If someone looks into it, I guess in a day of work we could have > > the Stack VM working with Spur 64 for Pharo without support for > > some librairies. There might be uncommon crashes to fix over the > > first week of use. With several more weeks of work (maybe a couple > > months), the StackVM with all libraries should be > > production-ready. The JIT support will take more time, hopefully > > it will be done in a year from now. > > > > Maybe I should mention that the company who funded 64 bits support > > is using the VM on Mac for development and Linux for production, > > so Windows was not a priority and not done. We have to rely on > > open-source contributors, non paid, to add Windows support and > > that takes time. Nicolas Cellier added the support for the 64 bits > > Stack VM on his free time. If someone is investing money, the 64 > > bits Windows VM could reach production sooner (I guess within 6 > > months) because someone could work full time on it. > > > > Regards, > > > > On Thu, Mar 2, 2017 at 4:04 PM, <raffaello.giulietti(a)lifeware.ch > > <mailto:raffaello.giulietti@lifeware.ch>> wrote: > > > > On 07/02/17 07:13, Esteban Lorenzano wrote: > > > > > >> On 6 Feb 2017, at 21:41, Cyril Ferlicot D. > > <cyril.ferlicot(a)gmail.com <mailto:cyril.ferlicot@gmail.com>> > > wrote: > > >> > > >> Le 06/02/2017 Ã 21:31, Benoit St-Jean via Pharo-users a Ã©crit : > > >> > > >> > > >> Hi! > > >> > > >> IIRC, the windows VM will need some more time to be ready. > > Only Linux > > >> and OSX ones are usable at the moment. > > > > > > ^ this. > > > as Cyril says, win 64bits vm is still not ready (and it will > > take some more time to be). > > > > > > Esteban > > > > > > > > > Just for general curiosity, what are the main stumbling blocks > > in the > > road to a Windows 64 bit Pharo? > > > > > > Raffaello > > > > > > > > >

March 8, 2017

Re: [Pharo-users] Pharo TechTalk starting in one hour (16UTC) (LINKS)

by Marcus Denker

Hi, I have cleaned the beginning of the video. It will stay available here: https://www.youtube.com/watch?v=H52MAu_ISgU On Tue, Feb 28, 2017 at 4:01 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > So, techtalk will be here: > > https://www.youtube.com/watch?v=H52MAu_ISgU > > and discussion channel will be through discord, as always, here: > > http://discord.gg/Sj2rhxn > > See you there! > > Esteban > -- -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

March 8, 2017

Working bash command fails with OSSubprocess depending on input file

by Silas Berger

Hi everyone, Iâm currently having problems with executing bash commands through OSSubprocess (version: #stable, as of today) on OS X 10.11.6. Iâm using the command line tools of a program called ParseCit to extract metadata from .txt files. It works well for about 75% of all txt files Iâve tested it with, but fails on the remaining 25%. This isnât due to ParseCit though, since it works on all input files, when I issue the command directly from a bash. Iâve prepared two test txt files â one that works fine (goodExample.txt) and one that doesnât work (badExample.txt) with OSSubprocess. The conversion for both files works fine when issuing the following respective commands in a shell or bash: /Users/silas/Documents/TestWithOSS/tools/mac/parsecit/bin/citeExtract.pl -m extract_all /Users/silas/Documents/TestWithOSS/test_txt/badExample.txt /Users/silas/Documents/TestWithOSS/tools/mac/parsecit/bin/citeExtract.pl -m extract_all /Users/silas/Documents/TestWithOSS/test_txt/goodExample.txt Using OSSubprocess, it works well for goodExample.txt, the result looks like this: Unfortunately, that exact same method/command fails, if the target file is badExample.txt instead. Below, you can find two methods Iâve tried for badExaple.txt, neither of which work. Method 2 (which is the one I used in the above screenshot for goodExample.txt) has a stderr stream, its contents are just above the Method 2 screenshot. It looks like it should be a ParseCit problem, but, as Iâve mentioned above, it works fine when done directly in a bash or shell. In this GitHub repo there are the âtoolsâ folder containing a compiled version of ParseCit, a corresponding INSTALL.md with all the necessary install steps for ParseCit, and a folder âtest_txtâ, which contains goodExample.txt and badExample.txt. The EES-INSTALL.md in the same repo is not relevant in this context. If anyone has an idea what could be the problem or how I could get it to work, Iâd be very happy. Best, Silas *** Methods Iâve tried *** Method 1 Result: Empty stdout, empty stderr, exit status 65280 Method 2 Result: Empty stdout, exit status 65280, Stderr: /Users/silas/Documents/TestWithOSS/tools/mac/parsecit/bin/sectLabel/genericSect/extractFeature.rb:35:in `split': invalid byte sequence in US-ASCII (ArgumentError) from /Users/silas/Documents/TestWithOSS/tools/mac/parsecit/bin/sectLabel/genericSect/extractFeature.rb:35:in `<main>' Die: SectLabel::Controller::getGenericHeaders different in number of headers 8 vs. the number of generic headers 0 *** The commands *** p1 := OSSUnixSubprocess new command: '/Users/silas/Documents/TestWithOSS/tools/mac/parsecit/bin/citeExtract.pl'; arguments: #('-m' 'extract_all' '/Users/silas/Documents/TestWithOSS/test_txt/badExample.txt'); redirectStdout; redirectStderr; runAndWaitOnExitDo: [ :process :outString | outString inspect ]. p3 := OSSUnixSubprocess new shell: '/bin/bash' command: '/Users/silas/Documents/TestWithOSS/tools/mac/parsecit/bin/citeExtract.pl -m extract_all /Users/silas/Documents/TestWithOSS/test_txt/badExample.txt'; redirectStdout; redirectStderr; runAndWaitOnExitDo: [ :process :outString | outString inspect ].

March 8, 2017

Re: [Pharo-users] couchdb integration?

by Tudor Girba

Thanks, Pierce! Cheers, Doru > On Mar 8, 2017, at 1:46 PM, Pierce Ng <pierce(a)samadhiweb.com> wrote: > > On Tue, Mar 07, 2017 at 05:20:46AM +0100, Tudor Girba wrote: >> For example, I would be interested if there is any Pharo implementation for the CouchDB Replication Protocol: >> http://docs.couchdb.org/en/master/replication/protocol.html > > SCouchDB by Igor Stasenko > http://squeaksource.com/SCouchDB/ > > SCouchDBViewServer by Jesus Mari Aguirre ('scuse the ascii), a fork and superset > http://ss3.gemstone.com/ss/SCouchViewServer.html > > I've not used CouchDB myself. No experience with above. > > Pierce > -- www.tudorgirba.com www.feenk.com "If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut."

March 8, 2017

Re: [Pharo-users] couchdb integration?

by Pierce Ng

On Tue, Mar 07, 2017 at 05:20:46AM +0100, Tudor Girba wrote: > For example, I would be interested if there is any Pharo implementation for the CouchDB Replication Protocol: > http://docs.couchdb.org/en/master/replication/protocol.html SCouchDB by Igor Stasenko http://squeaksource.com/SCouchDB/ SCouchDBViewServer by Jesus Mari Aguirre ('scuse the ascii), a fork and superset http://ss3.gemstone.com/ss/SCouchViewServer.html I've not used CouchDB myself. No experience with above. Pierce

March 8, 2017

Seaside memory leaks ?

by Annick Fron

Hi, Has anybody investigated whether Seaside has memory leaks using Jquery ? I have suspicions about dirty blocks holding variables â¦ I crashed my server with 170 000 connections... Annick

March 8, 2017

Re: [Pharo-users] New version of Pillar

by Stephane Ducasse

- integrate AST tokens fixed by Doru. - decouple the installer logic from the command-line work made by Maxime. - remove the DNU tricks for magritte elements. - repackage and minimize dependencies (the core of Pillar should not depend on magritte). - package a minimal core that could be used for class comments. - document architecture and phases. - remove the "optimisation hell" produced by metadata vs. data. (KISS principle please). - make sure that ecstatic can be reexpressed on top of the new system. - make sure citezen components and smart publication ecstatic plugin can work - remove dependency to git script in the book template. If you want to help you are welcome. Pillar can be a really sexy Pharo showcase. On Wed, Mar 8, 2017 at 10:47 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi > > We are happy to announce a new version of Pillar for Pharo 50 and 60. > Thanks Maxime Roelandt for the help. > > Features > - Now we can rebuild the mooc slides (the metadata is correctly > handled) > - The double walking of the tree fixes by Yann Dubois is integrated. > - We checked and we can produce HTML, books and slides > > The version 4.0.7 will be the last stable version for Pharo 50. > > On Pharo 60 we will start a large cleaning. Here is the list: > > >

March 8, 2017