[Pharo-users] Voyage hang
>From a production image, built from script with the voyage configuration as: >"External PROJECTS dependencies" >spec project: 'voyage' with: [ > spec > className: 'ConfigurationOfVoyageMongo'; > repository: 'github://pharo-nosql/voyage:master/mc'; > versionString: #stable. >]. The image is first configured and used to populate a MongoDB, but then when doing a simple #selectAll on a persisted class of objets the image hangs! It is really weird because the Mongo browser from the same image let me see my database objects. So the MongoDB connection should be fine. I can alt+. the image, so enclosed the debug log. Any idea or direction to look at? Thanks Hilaire -- Dr. Geo http://drgeo.eu THERE_BE_DRAGONS_HERE User Interrupt 24 Mars 2017 9:07:14.865674 pm VM: unix - i686 - linux-gnu - NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.20 uuid: cf2a-897d-48fd-8251-6789dd21d958 Jun 14 2014 NBCogit NativeBoost-CogPlugin-EstebanLorenzano.20 uuid: cf2a-897d-48fd-8251-6789dd21d958 Jun 14 2014 https://github.com/pharo-project/pharo-vm.git Commit: 0e8bbfbaeb03237fa6bb63ba834773fab18ca307 Date: 2014-06-14 12:20:21 -0300 By: Esteban Lorenzano Jenkins build #14833 Image: Pharo4.0 [Latest update: #40626] [ self schedule. "It is critical that the following has no suspension point so that the test and the wait primitive are atomic. In addition, if the delay is no longer being waited on while entering the way we know that it is expired because the delay has already fired." beingWaitedOn ifTrue: [ delaySemaphore wait ] ifFalse: [ expired := true ] ] in DelayWaitTimeout>>wait Receiver: a DelayWaitTimeout(45000 msecs; 44964 msecs remaining) Arguments and temporary variables: Receiver's instance variables: delaySemaphore: a Semaphore() beingWaitedOn: true millisecondDelayDuration: 45000 scheduler: a DelayMicrosecondScheduler schedulerResumptionTime: 3667838879831494 process: a Process in [ self schedule. "It is critical that the following has ...etc... expired: false BlockClosure>>ensure: Receiver: [ self schedule. "It is critical that the following has no suspension point so that the ...etc... Arguments and temporary variables: aBlock: [ self unschedule ] complete: nil returnValue: nil Receiver's instance variables: outerContext: DelayWaitTimeout>>wait startpc: 41 numArgs: 0 DelayWaitTimeout>>wait Receiver: a DelayWaitTimeout(45000 msecs; 44960 msecs remaining) Arguments and temporary variables: Receiver's instance variables: delaySemaphore: a Semaphore() beingWaitedOn: true millisecondDelayDuration: 45000 scheduler: a DelayMicrosecondScheduler schedulerResumptionTime: 3667838879831494 process: a Process in [ self schedule. "It is critical that the following has ...etc... expired: false Semaphore>>waitTimeoutMSecs: Receiver: a Semaphore() Arguments and temporary variables: anInteger: 45000 d: a DelayWaitTimeout(45000 msecs; 44958 msecs remaining) Receiver's instance variables: firstLink: nil lastLink: nil excessSignals: 0 Socket>>waitForConnectionFor:ifTimedOut: Receiver: a Socket[connected] Arguments and temporary variables: timeout: 45 timeoutBlock: [ ConnectionTimedOut signal: 'Cannot connect to ' , (NetNameResol...etc... startTime: 29583 msecsDelta: 45000 msecsEllapsed: 0 status: 1 Receiver's instance variables: semaphore: a Semaphore() socketHandle: #[250 33 219 88 0 0 0 0 240 126 188 8] readSemaphore: a Semaphore() writeSemaphore: a Semaphore() Socket>>connectTo:port:waitForConnectionFor: Receiver: a Socket[connected] Arguments and temporary variables: hostAddress: #[127 0 0 1] port: 27017 timeout: 45 Receiver's instance variables: semaphore: a Semaphore() socketHandle: #[250 33 219 88 0 0 0 0 240 126 188 8] readSemaphore: a Semaphore() writeSemaphore: a Semaphore() SocketStream class>>openConnectionToHost:port:timeout: Receiver: SocketStream Arguments and temporary variables: hostIP: #[127 0 0 1] portNumber: 27017 timeout: 45 socket: a Socket[connected] Receiver's instance variables: superclass: Object methodDict: a MethodDictionary(#'<<'->SocketStream>>#'<<' #adjustInBuffer:->Soc...etc... format: 154 layout: a FixedLayout instanceVariables: #('recentlyRead' 'socket' 'inBuffer' 'outBuffer' 'inNextToWr...etc... organization: a ClassOrganization subclasses: nil name: #SocketStream classPool: a Dictionary() sharedPools: an OrderedCollection() environment: a SystemDictionary(lots of globals) category: #'Network-Kernel' traitComposition: {} localSelectors: nil SocketStream class>>openConnectionToHost:port: Receiver: SocketStream Arguments and temporary variables: hostIP: #[127 0 0 1] portNumber: 27017 Receiver's instance variables: superclass: Object methodDict: a MethodDictionary(#'<<'->So
Re: [Pharo-users] Voyage Timeout
If I open manualy this image execute the configureMyImage.st code from a playground, then save the image, I don't have a Voyage time error at start up. Are there non friendly interaction between voyage/socket and st command handler? Hilaire Le 22/03/2017 à 20:35, Hilaire a écrit : > Hi, > > When I configure a production image with command st handler as following: > > pharo myImage st --save --quit configureMyImage.st > > I notice at image start up, a Socket timeout error. > > In the configureMyImage.st script, among other things, I open a > singleton Voyage repository. I added a 5s delay at the end of this > script, just wondering if image was shutdown before Voyage establishes > connection with the Mongo DB, but no. > > Any incompatibility issues to be aware of between st command handler > (particularly the --save part) and Voyage repository? > > Thanks, > Hilaire -- Dr. Geo http://drgeo.eu
Re: [Pharo-users] Smalltalk on Stack Overflow Developers Survey 2017
On 24/03/2017 13:33, Offray Vladimir Luna Cárdenas wrote: > Thanks Davorin. Where can we look at the results? > https://stackoverflow.com/insights/survey/2017 > Cheers, > > Offray > > -- Cyril Ferlicot http://www.synectique.eu 2 rue Jacques Prévert 01, 59650 Villeneuve d'ascq France signature.asc Description: OpenPGP digital signature
Re: [Pharo-users] Smalltalk on Stack Overflow Developers Survey 2017
Thanks Davorin. Where can we look at the results? Cheers, Offray On 24/03/17 05:10, Davorin Rusevljan wrote: sorry to abuse pharo list, but I guess it is related enough. Smalltalk made it to SO developer Survey. Unfortunately it did not appear in most used languages list, but it got great place as "Second most loved language"! So for those of you who participated in the survey, it payed off. davorin
[Pharo-users] Smalltalk on Stack Overflow Developers Survey 2017
sorry to abuse pharo list, but I guess it is related enough. Smalltalk made it to SO developer Survey. Unfortunately it did not appear in most used languages list, but it got great place as "Second most loved language"! So for those of you who participated in the survey, it payed off. davorin