February 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] On things we do when our stack overflows

by Sven Van Caekenberghe

The VM could sure use stack overflow protection, it would/could help catch numerous 'hangs' due to infinite loops. On 18 Feb 2014, at 13:08, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > Hi there, > > Toyota shoot its foot and learnt how not to anymore. > > This is a nice read on the things our software do when the stack overflows. > Are We Shooting Ourselves in the Foot with Stack Overflow? > http://embeddedgurus.com/state-space/2014/02/are-we-shooting-ourselves-in-t… > > The question on the table is > > are we following time proven safety rules when the same thing happen to our VM? > > Nice reading > > sebastian > > o/ > > > > >

Feb. 18, 2014

Re: [Pharo-dev] ./pharo .st argument and quit/no quit

by Sebastian Sastre

true Tudor. Do you know why the default behaviour is inverted for that case? sebastian o/ On Feb 18, 2014, at 11:47 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > You can find the answer to your question in the class comment: > > Usage: st [--help] [ --quit ] <FILE> > --help list this help message > --quit if specified, the image exits without saving after evaluating FILE > --save if specified, save the image after evaluating FILE > <FILE> a file containing valid Pharo expressions > > Documentation: > The ST command line handler runs Pharo code stored in a file without quiting. > > Example: > > pharo Pharo.image st code.st > > # By default files ending in .st are recognized and evaluated > pharo Pharo.image code.st > > Doru > > > > On Tue, Feb 18, 2014 at 3:27 PM, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > Hi there, > > can someone clarify this for me? > > lets say you execute in the terminal: > > pharo-vm-nox some.image save awesome.image âdelete-old > > it starts, saves the image and deletes the old one and quits returning control to terminal > > but if you do: > > pharo-vm-nox some.image ImageBuilder.st save awesome.image âdelete-old > > it stays forever open > > I was taking a look at this but what is âquitâ option? can someone explain the behaviour of this please? > > STCommandLineHandler>>end > | quit | > > quit := self commandLine hasOption: 'quit'. > > (self commandLine hasOption: 'save') > ifTrue: [ Smalltalk snapshot: true andQuit: quit ]. > > quit > ifTrue: [ self exitSuccess ]. > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Feb. 18, 2014

Re: [Pharo-dev] ./pharo .st argument and quit/no quit

by Sebastian Sastre

ok just found out that when you send an .st file in the arguments the default behaviour is inverted Beware! It seems we have our very own Smalltalk Experience Gremlins messing around =/ sebastian o/ PD: this works as one would expect: pharo-vm-nox some.image ImageBuilder.st âquit=true save awesome.image âdelete-old On Feb 18, 2014, at 11:27 AM, Sebastian Sastre <SEBASTIAN(a)FLOWINGCONCEPT.COM> wrote: > Hi there, > > can someone clarify this for me? > > lets say you execute in the terminal: > > pharo-vm-nox some.image save awesome.image âdelete-old > > it starts, saves the image and deletes the old one and quits returning control to terminal > > but if you do: > > pharo-vm-nox some.image ImageBuilder.st save awesome.image âdelete-old > > it stays forever open > > I was taking a look at this but what is âquitâ option? can someone explain the behaviour of this please? > > STCommandLineHandler>>end > | quit | > > quit := self commandLine hasOption: 'quit'. > > (self commandLine hasOption: 'save') > ifTrue: [ Smalltalk snapshot: true andQuit: quit ]. > > quit > ifTrue: [ self exitSuccess ].

Feb. 18, 2014

Re: [Pharo-dev] ./pharo .st argument and quit/no quit

by Tudor Girba

You can find the answer to your question in the class comment: Usage: st [--help] [ --quit ] <FILE> --help list this help message --quit if specified, the image exits without saving after evaluating FILE --save if specified, save the image after evaluating FILE <FILE> a file containing valid Pharo expressions Documentation: The ST command line handler runs Pharo code stored in a file without quiting. Example: pharo Pharo.image st code.st # By default files ending in .st are recognized and evaluated pharo Pharo.image code.st Doru On Tue, Feb 18, 2014 at 3:27 PM, Sebastian Sastre < sebastian(a)flowingconcept.com> wrote: > Hi there, > > can someone clarify this for me? > > lets say you execute in the terminal: > > pharo-vm-nox some.image save awesome.image --delete-old > > it starts, saves the image and deletes the old one and quits returning > control to terminal > > but if you do: > > pharo-vm-nox some.image ImageBuilder.st save awesome.image --delete-old > > it stays forever open > > I was taking a look at this but what is 'quit' option? can someone explain > the behaviour of this please? > > STCommandLineHandler>>end > | quit | > > quit := self commandLine hasOption: 'quit'. > > (self commandLine hasOption: 'save') > ifTrue: [ Smalltalk snapshot: true andQuit: quit ]. > > quit > ifTrue: [ self exitSuccess ]. > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 18, 2014

Re: [Pharo-dev] installing opendbx for postgres on mac

by Sven Van Caekenberghe

On 18 Feb 2014, at 13:24, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Well, I wanted to test DBXTalk, and this is why I wanted to go through the pain of hooking to a DB, and the only way I know is to install the OpenDBX libraries. Yes, I understood that is your main objective. > Do you mean to suggest to try with using the binding from http://smalltalkhub.com/#!/~PharoExtras/PostgresV2/ to hook directly to a Postgres installation? I could try that. Yes, that is indeed what I meant as an alternative: it even works perfectly under Glorp.

Feb. 18, 2014

./pharo .st argument and quit/no quit

by Sebastian Sastre

Hi there, can someone clarify this for me? lets say you execute in the terminal: pharo-vm-nox some.image save awesome.image âdelete-old it starts, saves the image and deletes the old one and quits returning control to terminal but if you do: pharo-vm-nox some.image ImageBuilder.st save awesome.image âdelete-old it stays forever open I was taking a look at this but what is âquitâ option? can someone explain the behaviour of this please? STCommandLineHandler>>end | quit | quit := self commandLine hasOption: 'quit'. (self commandLine hasOption: 'save') ifTrue: [ Smalltalk snapshot: true andQuit: quit ]. quit ifTrue: [ self exitSuccess ].

Feb. 18, 2014

Re: [Pharo-dev] Connection closed while waiting for data in bootstrapped image

by Pavel Krivanek

They seem to be ok. I tried to look at the sockets during waiting in other thread and signal their semaphores but no change. Socket loopbackTest WORKS. -- Pavel 2014-02-17 11:18 GMT+01:00 Guillermo Polito <guillermopolito(a)gmail.com>: > ExternalSemaphores table may be not well initialized? I can help having a > look this afternoon :) > > > On Mon, Feb 17, 2014 at 11:11 AM, Sven Van Caekenberghe <sven(a)stfx.eu>wrote: > >> Hi Pavel, >> >> I just tried on a machine of mine. >> >> I changed testNetwork.st to >> >> Transcript show: (ZnClient new logToTranscript; get: ' >> http://zn.stfx.eu/zn/numbers.txt'); cr. >> >> That way you get a bit more progress info. As I suspected the request is >> written and the failure is while reading the response. I tried connecting >> to a local Zinc server which confirmed this as well: the request comes in >> on the server and it writes the response. >> >> This is the output now: >> >> root@stfx:~# ./pharo PharoKernel.image testNetwork.st >> >> 2014-02-17 10:00:59 463573 I Wrote a ZnRequest(GET /random) >> 2014-02-17 10:00:59 463573 D Sent headers >> >> User-Agent: Zinc HTTP Components 1.0 >> >> Accept: */* >> >> Host: localhost:1701 >> >> >> >> =============================================================================== >> Notice: Errors in script loaded from /root/testNetwork.st >> >> =============================================================================== >> Errors in script loaded from /root/testNetwork.st >> ==== Startup Error: ConnectionClosed: Connection closed while waiting for >> data. >> Socket>>waitForDataFor: in Block: [ ConnectionClosed signal: 'Connection >> closed whil...etc... >> Socket>>waitForDataFor:ifClosed:ifTimedOut: >> Socket>>waitForDataFor: >> Socket>>receiveDataSignallingTimeout:into:startingAt: >> SocketStream>>receiveData >> SocketStream>>next >> ZnLineReader>>processNext >> ZnLineReader>>nextLine >> ZnStatusLine>>readFrom: >> ZnStatusLine class>>readFrom: >> ZnResponse>>readHeaderFrom: >> ZnResponse(ZnMessage)>>readFrom: >> ZnResponse class(ZnMessage class)>>readFrom: >> ZnClient>>executeRequestResponse >> ZnClient>>getConnectionAndExecute in Block: [ self executeRequestResponse >> ] >> BlockClosure>>ensure: >> ZnClient>>getConnectionAndExecute >> ZnClient>>executeWithRedirectsRemaining: >> ZnClient>>executeWithRetriesRemaining: in Block: [ self >> executeWithRedirectsRemaining: self maxNumb...etc... >> BlockClosure>>on:do: >> ZnClient>>executeWithRetriesRemaining: >> ZnClient>>executeWithTimeout in Block: [ self >> executeWithRetriesRemaining: self numberOfR...etc... >> BlockClosure>>on:do: >> ZnClient>>executeWithTimeout in Block: [ ... >> ZnClient>>withTimeoutDo: in Block: [ ^ block value ] >> ZnConnectionTimeout(DynamicVariable)>>value:during: in Block: >> >> You are using regular socket streams, which is good. For now I can't >> think of a reasons why the reading would fail, if I think of something, I >> will let you know. >> >> It is pretty hard to debug this way ;-) >> >> Sven >> >> On 17 Feb 2014, at 10:22, Pavel Krivanek <pavel.krivanek(a)gmail.com> >> wrote: >> >> > (NetNameResolver addressForName: 'www.esug.org') returns good value... >> > >> > -- Pavel >> > >> > >> > 2014-02-17 9:32 GMT+01:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: >> > Hi, >> > >> > thank you for the tip. It seems that it is not directly Zinc related. >> But if you want something to play with, do: >> > >> > - load the bootstrapped image: >> > >> https://ci.inria.fr/pharo-contribution/view/Pharo-Kernel-3.0/job/PharoKerne… >> > >> > ./pharo PharoKernel.image fix.st >> > ./pharo PharoKernel.image loadNetwork.st >> > ./pharo PharoKernel.image testNetwork.st >> > >> > The CI slaves revolt now so I cannot make it more comfortable :-) >> > >> > Cheers, >> > -- Pavel >> > >> > >> > >> > >> > 2014-02-16 22:58 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >> > >> > Hi Pavel, >> > >> > On 16 Feb 2014, at 22:23, Pavel Krivanek <pavel.krivanek(a)gmail.com> >> wrote: >> > >> > > Hi Sven, >> > > >> > > we can successfully load network packages to the bootstrapped image >> but when we try to test it using: >> > > >> > > ZnClient new get: 'http://zn.stfx.eu/zn/numbers.txt'. >> > > >> > > we get "ConnectionClosed: Connection closed while waiting for data" >> error after few seconds. Do you have some idea, what may be wrong? Probably >> something is not initialized well but I have no clue what. >> > > >> > > Cheers, >> > > -- Pavel >> > >> > Hard to say. I would guess that you are already on the point of waiting >> for a server response, so you already successfully initialised networking, >> resolved DNS, opened a TCP socket and wrote the request over it. On the >> other hand, one of those steps might not have been done right, since you >> get no response. >> > >> > Any chance of a stack trace ? Or an image ? But that would be a >> headless one I guess ;-) >> > >> > Sven >> > >> > >> > >> > >> > >> >> >> >

Feb. 18, 2014

Re: [Pharo-dev] installing opendbx for postgres on mac

by Tudor Girba

I certainly will :). I will also provide support for DB manipulation inside the GTInspector. Doru On Tue, Feb 18, 2014 at 2:56 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi Tudor, > > if possible you should sum it all up in a short video or tutorial/blog > post for others to know about the "how to". > > Thx > T. > > *Gesendet:* Dienstag, 18. Februar 2014 um 07:33 Uhr > *Von:* "Tudor Girba" <tudor(a)tudorgirba.com> > *An:* dbxtalk(a)googlegroups.com, "Discusses Development of Pharo" < > pharo-dev(a)lists.pharo.org> > *Betreff:* [Pharo-dev] installing opendbx for postgres on mac > Hi, > > After successfully getting DBXTalk to work with Oracle on Windows, I would > like to try to use it with Postgres on Mac. > > However, I have difficulties in obtaining the binaries for OpenDBX for Mac > (Mountain Lion). > Does any of you know how to do this? > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 18, 2014

Re: [Pharo-dev] installing opendbx for postgres on mac

by Torsten Bergmann

Feb. 18, 2014

Re: [Pharo-dev] installing opendbx for postgres on mac

by Tudor Girba

Hi, Well, I wanted to test DBXTalk, and this is why I wanted to go through the pain of hooking to a DB, and the only way I know is to install the OpenDBX libraries. Do you mean to suggest to try with using the binding from http://smalltalkhub.com/#!/~PharoExtras/PostgresV2/ to hook directly to a Postgres installation? I could try that. Doru On Tue, Feb 18, 2014 at 8:12 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Doru, > > I know this doesn't answer your question, but did you also try the native > PostgreSQL driver, which should work unmodified without plugins or > libraries on all platforms ? > > Sven > > PS: I never tried the DBX ones ;-) > > On 18 Feb 2014, at 07:33, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > Hi, > > > > After successfully getting DBXTalk to work with Oracle on Windows, I > would like to try to use it with Postgres on Mac. > > > > However, I have difficulties in obtaining the binaries for OpenDBX for > Mac (Mountain Lion). > > Does any of you know how to do this? > > > > Cheers, > > Doru > > > > > > -- > > www.tudorgirba.com > > > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 18, 2014