- Pharo-dev - lists.pharo.org

PrimitiveFailed: primitive #primLocalAddress in NetNameResolver class failed [FreeBSD]

by Petr Fischer

Hello, just tested latest 32b Linux spur VM "stable-threaded-20170503" with latest 6.0 image "60494" (from files.pharo.com) under FreeBSD with linux compatibility layer switched on. Good part - now, it's running wihtout need of real time threads (no need to run under root, oh yes!) and it runs near 2x speed in some tests, just wow! But, this exception occurs often: PrimitiveFailed: primitive #primLocalAddress in NetNameResolver class failed details: https://pastebin.com/raw/bdjDW6YR Whats wrong? Some news/changes in SocketPlugin? Thanks! pf

May 18, 2017

Chrome DevTools Protocol and Pharo

by Torsten Bergmann

Hi, I played around with remote controlling Google Chrome from Pharo using Chrome DevTools Protocol [1] (based on WebSockets). The video shows an example using latest Pharo 6 on Mac: https://www.youtube.com/watch?v=9F5FrQTEJWY Initial Code is on GitHub [2] if someone is interested, requires OSOSX and Zinc Websockets to be loaded. Have fun T. [1] https://chromedevtools.github.io/devtools-protocol [2] https://github.com/astares/Pharo-Chrome

May 18, 2017

Re: [Pharo-dev] Need help with Pillar

by Damien Pollet

On 18 May 2017 at 01:34, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > curl https://raw.githubusercontent.com/pillar-markup/pillar/ > master/download.sh | bash > > I had to copy PharoV50.sources in the folder pharo-vm/ apparently. > Hmm strange I got that this morning as well with ClÃ©ment's book. The script installs a PharoV60.sources so most probably it installs the latest VM; might be a problem if Pillar really relies on Pharo 5â¦ > Getting the archetype book gives me an error: > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > /tmp/pillar> ./pillar archetype book > > Which website is it trying to get access to? > That would be Inria CI, they're having problems with CloudStack currently -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

May 18, 2017

Adding a CommandLineArgument>>#options: aName do: aBlock?

by Holger Freyther

Hi, I want to implement something like -vvvv[1] but currently the optionAt variants will pick the first option only. Would there be general interest in an implementation that allows to iterate through all variants? Would an above >>#do: like approach be preferred or to return a list of options? With >>#ifAbsent: or not? Enjoy the PharoDays and I wish traveling would have allowed me to attend. holger [1] Count the number of occurrences for -v. In fact I want something like the below to add two hosts to a list --add-host=mongodb://one:port --add-host=mongodb://two:port

May 18, 2017

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60494 Home: https://github.com/pharo-project/pharo-core

May 18, 2017

[pharo-project/pharo-core] 177e42: 60494

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 177e42e4c650ce26e9a138abf75aa21df535cd64 https://github.com/pharo-project/pharo-core/commit/177e42e4c650ce26e9a138ab… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-05-18 (Thu, 18 May 2017) Changed paths: M Kernel-Tests.package/ClassTest.class/instance/testing - navigation/testMethodsReferencingClass.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60493.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60494.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60493.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60494.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60494 20064 ClassTest>>#testMethodsReferencingClass uses non-existing BehaviorTests https://pharo.fogbugz.com/f/cases/20064 http://files.pharo.org/image/60/60494.zip

May 18, 2017

Need help with Pillar

by Alexandre Bergel

Hi! I have installed Pillar on MacOSX using: curl https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh | bash I had to copy PharoV50.sources in the folder pharo-vm/ apparently. Getting the archetype book gives me an error: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= /tmp/pillar> ./pillar archetype book ConnectionTimedOut: Data receive timed out. [ ConnectionTimedOut signal: 'Data receive timed out.' ] in Socket>>waitForDataFor: in Block: [ ConnectionTimedOut signal: 'Data receive timed o...etc... Socket>>waitForDataFor:ifClosed:ifTimedOut: Socket>>waitForDataFor: ZdcSecureSocketStream(ZdcAbstractSocketStream)>>socketWaitForData [ self socketWaitForData ] in ZdcSecureSocketStream(ZdcSimpleSocketStream)>>fillReadBuffer in Block: [ self socketWaitForData ] BlockClosure>>on:do: ZdcSecureSocketStream(ZdcSimpleSocketStream)>>fillReadBuffer ZdcSecureSocketStream(ZdcAbstractSocketStream)>>next ZnLineReader>>processNext ZnLineReader>>nextLine ZnStatusLine>>readFrom: ZnStatusLine class>>readFrom: ZnResponse>>readHeaderFrom: ZnResponse(ZnMessage)>>readStreamingFrom: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Which website is it trying to get access to? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 17, 2017

Re: [Pharo-dev] Current working directory

by Stephane Ducasse

This super important! We should be able to use Pharo to write script!!! On Wed, May 17, 2017 at 1:38 PM, Rajula Vineet <Vineet.Reddy(a)iiitb.org> wrote: > Hi all, > > I am working on improving pharo command line as a part of my GSoC project. > I > have been looking at different current working directory implementations. I > have written a blog post > <https://vineetreddy.wordpress.com/2017/05/17/pwd-vs-getcwd/> on it. It > would be of great help, if you can take a look and give your feedback. > > Rajula > > > > -- > View this message in context: http://forum.world.st/Current- > working-directory-tp4947453.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

May 17, 2017

Re: [Pharo-dev] Current working directory

by Eliot Miranda

Hi Phil, Hi Rajula, > On May 17, 2017, at 5:56 AM, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > > Definitely. > > I read that you had a crash and you didn't know why. > > It is a good idea to run pharo under gdb so you can do a bt (backtrace) and see where it bombed. > You can inspect parameters etc. Usually this is revealing of the problem when I do like that. > > Check http://stackoverflow.com/questions/6121094/how-do-i-run-a-program-with-comm… > > Like > > gdb -ex=r --args pharo-vm/pharo Pharo.image > > (not sure this is all right, but you'll figure it out). Newer versions of the launch script take --gdb as an argument so you can simply say pharo-vm/pharo -gdb Pharo.image > I also like to use a debug or assert VM so that I get all debugging symbols information. +1 > Alternatively, connect to a running Pharo with gdb -p PID > > I usually do that from something like Code::Blocks with an assert VM + source code around for whatever library I am trying to use from UFFI. Works nicely. Especially when you put a breakpoint before a crashing site, allowing you to see the stackframes etc. > > With gdb command line, it is worth knowing about frames: http://www.delorie.com/gnu/docs/gdb/gdb_44.html > > Namaste, > > Phil > > > > > > > > >> On Wed, May 17, 2017 at 2:08 PM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >> Thanks Rajula :) >> >> This is cool! >> >>> On Wed, May 17, 2017 at 1:38 PM, Rajula Vineet <Vineet.Reddy(a)iiitb.org> wrote: >>> Hi all, >>> >>> I am working on improving pharo command line as a part of my GSoC project. I >>> have been looking at different current working directory implementations. I >>> have written a blog post >>> <https://vineetreddy.wordpress.com/2017/05/17/pwd-vs-getcwd/> on it. It >>> would be of great help, if you can take a look and give your feedback. >>> >>> Rajula >>> -- >>> View this message in context: http://forum.world.st/Current-working-directory-tp4947453.html >>> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> -- >> >> Guille Polito >> >> Research Engineer >> French National Center for Scientific Research - http://www.cnrs.fr >> >> >> Web: http://guillep.github.io >> Phone: +33 06 52 70 66 13

May 17, 2017

Re: [Pharo-dev] Command line save and quit

by K K Subbu

On Wednesday 17 May 2017 06:53 PM, Damien Pollet wrote: > > | quit | > quit := self commandLine hasOption: 'quit'. > (self commandLine hasOption: 'save') > ifTrue: [ Smalltalk snapshot: true andQuit: quit ]. > quit > ifTrue: [ self exitSuccess ]. > > Here I'm guessing if you --save --quit then the image will get saved, > and next time it wakes up, enters the second conditional and > #exitSuccessâ¦ confusing :/ Thank you for making it clear. This is what intrigued me. I see many instances in pharo-project/pharo git where "--save --quit" is used. e.g. scripts/export.sh:./pharo Pharo.image --save --quit ${PWD}/export.st Regards .. Subbu

May 17, 2017