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

Re: [Pharo-users] Pharo 6 / VM crashes

by volkert

ok. when the next crash happens i try to create a reproducible case and will open in case the pharo issue tracker. thanks for all the valuable work on the VM ... Volkert Am 30.04.2017 um 14:00 schrieb ClÃ©ment Bera: > Hi, > > About the best way to help... > > A reproducible case that we (VM developers) can reproduce easily is > the best way to help. If we do not have a way to reproduce your bug, > we cannot do anything about it. The best is an image which crashes > immediately after start-up or a do-it that reliably crash the system, > combined with all the version numbers (OS version, vm version, pharo > version) or a crash dump file which includes all those version numbers. > > Trying another version of Pharo (like 5 instead of 6 like you did) and > the latest VM over the stable is another thing you can do. If you can > prove that the bug comes from recent images or recent VMs it helps us > as we know where to look (in the VM or in the image). > > As Oleks said the bug you mentioned should be fixed in the latest VM. > The latest VM will be promoted to stable in the incoming weeks for the > Pharo 6 release. Sorry for the inconvenience. > > Best, > > > On Sun, Apr 30, 2017 at 1:10 PM, Oleks <olk.zaytsev(a)gmail.com > <mailto:olk.zaytsev@gmail.com>> wrote: > > Hello, > > The same happened to me about a week ago. Apparently, the latest > 'stable' > (Feb 22) version of VR has some compactor bug which makes it crash. > > Try this: > curl get.pharo.org/60+vmLatest <http://get.pharo.org/60+vmLatest> > | bash > It should download the latest (Apr 18) VM, which works just fine. > > Oleks > > > > -- > View this message in context: > http://forum.world.st/Pharo-6-VM-crashes-tp4944939p4944946.html > <http://forum.world.st/Pharo-6-VM-crashes-tp4944939p4944946.html> > Sent from the Pharo Smalltalk Users mailing list archive at > Nabble.com. > >

April 30, 2017

Process scheduling

by raffaello.giulietti＠lifeware.ch

Hi, I can't find a description on how ProcessorScheduler in Pharo (i.e., Cog) is supposed to do context switches in absence of other synchronization points. Is it following the BlueBook spec? Just to recall that model, the VM, when about to execute the current bytecode instruction of the current Process, checks whether a strictly higher priority Process is ready to run and if so, switches to (one of) the highest priority among them. Thanks in advance for clarifications. Greetings Raffaello

April 30, 2017

Re: [Pharo-users] Voyage - collecting data from Mongo

by Sabine Manaa

Khrystyna , I also use a new version of mongo with authentication (but only old version) and wired Tiger. I am not sure but possibly you can try to overwrite the following method to fix the problem: MongoDatabase>>collections | reply names | reply := self command: {(#listCollections -> 1)} asDictionary. names := ((reply at: 'cursor') at: 'firstBatch') collect: [ :each | each at: #name ]. ^ names collect: [ :each | MongoCollection database: self name: each ] 2017-04-30 12:24 GMT+02:00 Mark Rizun [via Smalltalk] < ml+s1294792n4944944h59(a)n4.nabble.com>: > > Mark >> once you have a solution could you post it because I would like to add >> your question to the voyage chapter. >> stef >> > > Sure thing, Stef. > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > http://forum.world.st/Voyage-collecting-data-from-Mongo- > tp4944784p4944944.html > To start a new topic under Pharo Smalltalk Users, email > ml+s1294792n1310670h65(a)n4.nabble.com > To unsubscribe from Pharo Smalltalk Users, click here > <http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&no…> > . > NAML > <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> > -- View this message in context: http://forum.world.st/Voyage-collecting-data-from-Mongo-tp4944784p4944953.h… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 30, 2017

Re: [Pharo-users] Pharo 6 / VM crashes

by Esteban Lorenzano

> On 30 Apr 2017, at 13:10, Oleks <olk.zaytsev(a)gmail.com> wrote: > > Hello, > > The same happened to me about a week ago. Apparently, the latest 'stable' > (Feb 22) version of VR has some compactor bug which makes it crash. > > Try this: > curl get.pharo.org/60+vmLatest | bash > It should download the latest (Apr 18) VM, which works just fine. this is correct :) in particular, in linux we recommend to use curl get.pharo.org/60+vmTLatest <http://get.pharo.org/60+vmTLatest> (the threaded hearbeat) Esteban > > Oleks > > > > -- > View this message in context: http://forum.world.st/Pharo-6-VM-crashes-tp4944939p4944946.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

April 30, 2017

Re: [Pharo-users] Pharo 6 / VM crashes

by volkert

Oleks, much better :-) Thank you, Volkert Am 30.04.2017 um 13:10 schrieb Oleks: > Hello, > > The same happened to me about a week ago. Apparently, the latest 'stable' > (Feb 22) version of VR has some compactor bug which makes it crash. > > Try this: > curl get.pharo.org/60+vmLatest | bash > It should download the latest (Apr 18) VM, which works just fine. > > Oleks > > > > -- > View this message in context: http://forum.world.st/Pharo-6-VM-crashes-tp4944939p4944946.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

April 30, 2017

Re: [Pharo-users] Pharo 6 / VM crashes

by ClÃ©ment Bera

Hi, About the best way to help... A reproducible case that we (VM developers) can reproduce easily is the best way to help. If we do not have a way to reproduce your bug, we cannot do anything about it. The best is an image which crashes immediately after start-up or a do-it that reliably crash the system, combined with all the version numbers (OS version, vm version, pharo version) or a crash dump file which includes all those version numbers. Trying another version of Pharo (like 5 instead of 6 like you did) and the latest VM over the stable is another thing you can do. If you can prove that the bug comes from recent images or recent VMs it helps us as we know where to look (in the VM or in the image). As Oleks said the bug you mentioned should be fixed in the latest VM. The latest VM will be promoted to stable in the incoming weeks for the Pharo 6 release. Sorry for the inconvenience. Best, On Sun, Apr 30, 2017 at 1:10 PM, Oleks <olk.zaytsev(a)gmail.com> wrote: > Hello, > > The same happened to me about a week ago. Apparently, the latest 'stable' > (Feb 22) version of VR has some compactor bug which makes it crash. > > Try this: > curl get.pharo.org/60+vmLatest | bash > It should download the latest (Apr 18) VM, which works just fine. > > Oleks > > > > -- > View this message in context: http://forum.world.st/Pharo-6- > VM-crashes-tp4944939p4944946.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

April 30, 2017

Re: [Pharo-users] Pharo 6 / VM crashes

by Oleks

Hello, The same happened to me about a week ago. Apparently, the latest 'stable' (Feb 22) version of VR has some compactor bug which makes it crash. Try this: curl get.pharo.org/60+vmLatest | bash It should download the latest (Apr 18) VM, which works just fine. Oleks -- View this message in context: http://forum.world.st/Pharo-6-VM-crashes-tp4944939p4944946.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 30, 2017

Re: [Pharo-users] Geocoder Services in Pharo?

by volkert

See http://catalog.pharo.org/ and search for GADM Am 30.04.2017 um 12:29 schrieb Stephane Ducasse: > may be this is only for pharo40. > Does it have a configurationOf? > Because this is strange > > Stef > > On Sun, Apr 30, 2017 at 10:17 AM, volkert <volkert(a)nivoba.de > <mailto:volkert@nivoba.de>> wrote: > > of course :-) > > yes, i am trying to load the package GADM in Pharo 5, but it > failed ... :-( > > Volkert > > > Am 30.04.2017 um 09:57 schrieb Stephane Ducasse: >> volkert >> >> Then what would be good is to code it as open-source so that >> people can join effort. >> Did you check the packages of geolocalisation developed by Hernan >> Morales? >> Stef >> >> On Sat, Apr 29, 2017 at 4:18 PM, volkert <volkert(a)nivoba.de >> <mailto:volkert@nivoba.de>> wrote: >> >> Hi Sven, >> >> thanks for your fast response and the snippets. I scanned the >> different geocoder classes from "geopy" and also the OSM >> Nominatim docs. Indeed, it is not hard, ..... but if there is >> already a package, why not using it :-) >> >> maybe i start to write such a lib. >> >> Thanks, >> Volkert >> >> >> Am 29.04.2017 um 15:54 schrieb Sven Van Caekenberghe: >> >> Hi Volkert, >> >> On 29 Apr 2017, at 15:01, volkert <volkert(a)nivoba.de >> <mailto:volkert@nivoba.de>> wrote: >> >> Dear all, >> >> do we have a package to access the a geocoder >> service? Something similar to "geopy". >> >> Volkert >> >> As far as I know there is no such library. >> >> We have it internally, but that part is not open source. >> But it is not so hard to do yourself. >> >> Here is an example for forward geocoding (address -> >> coordinates): >> >> ZnClient new >> url: 'http://nominatim.openstreetmap.org/search >> <http://nominatim.openstreetmap.org/search>'; >> queryAt: #format put: 'json'; >> queryAt: #addressdetails put: '1'; >> queryAt: #q put: 'Villerspark 5, 3500 Hasselt'; >> queryAt: #countrycodes put: 'be'; >> accept: ZnMimeType applicationJson; >> contentReader: [ :entity | STONJSON fromString: >> entity contents ]; >> get. >> >> Here is an example for reverse geocoding (coordinates -> >> address): >> >> ZnClient new >> url: 'http://nominatim.openstreetmap.org/reverse >> <http://nominatim.openstreetmap.org/reverse>'; >> queryAt: #format put: 'json'; >> queryAt: #lon put: 5.33732 asString; >> queryAt: #lat put: 50.926 asString; >> accept: ZnMimeType applicationJson; >> contentReader: [ :entity | STONJSON fromString: >> entity contents ]; >> get. >> >> These are against the OpenStreetMap Nomatim service, >> others are similar. >> >> HTH, >> >> Sven >> >> >> >> >> > >

April 30, 2017

Re: [Pharo-users] Voyage - collecting data from Mongo

by Mark Rizun

> Mark > once you have a solution could you post it because I would like to add > your question to the voyage chapter. > stef > Sure thing, Stef.

April 30, 2017

Re: [Pharo-users] Dark theme and white vs. green color

by Stephane Ducasse

I can tell you that for me the green is a lot more difficult to read because it is too saturated. During a long period I could not use the dark one because of the saturated red error color. I could just not read what was written. On Fri, Apr 28, 2017 at 6:42 PM, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > Hi, > > While we were improving the DiffMorph for the dark theme, we conclude that > it is much harder to read the text. > > I personally also often miss a new debugger window on a big screen. > Something I have not experienced before. > > And this discussion reminds me the old computers where the background was > black and text green. There are two screenshot to compare it: > > > > A personally feel that it is much easier to read the green text. > > What do you think? > Juraj > >

April 30, 2017