- Pharo-users - lists.pharo.org

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

by Sabine Manaa

Happy to help. I got this information from Udo Schneider in slack several weeks ago. As far as I know, he works on an update for several things concerning mongo but I don't know when he will release it. chrismihaylyk [via Smalltalk] <ml+s1294792n4944955h0(a)n4.nabble.com> schrieb am So. 30. Apr. 2017 um 16:45: > Sabine, thank you very much! It's very helpful, work fine. > 2017-04-30 17:09 GMT+03:00 Sabine Manaa <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=4944955&i=0>>: > >> 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] <[hidden email] >> <http:///user/SendEmail.jtp?type=node&node=4944953&i=0>>: >> > >>> 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.h… >>> >> To start a new topic under Pharo Smalltalk Users, email [hidden email] >>> <http:///user/SendEmail.jtp?type=node&node=4944953&i=1> >>> >> To unsubscribe from Pharo Smalltalk Users, click here. >>> NAML >>> <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> >>> >> ------------------------------ >> View this message in context: Re: Voyage - collecting data from Mongo >> <http://forum.world.st/Voyage-collecting-data-from-Mongo-tp4944784p4944953.h…> >> >> Sent from the Pharo Smalltalk Users mailing list archive >> <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at >> Nabble.com. >> > If you reply to this email, your message will be added to the discussion > below: > > http://forum.world.st/Voyage-collecting-data-from-Mongo-tp4944784p4944955.h… > 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-tp4944784p4944977.h… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 30, 2017

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

by Ben Coman

On Sun, Apr 30, 2017 at 8:00 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > 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. > The *known* buggy "stable-VM" really needs to be replaced ASAP. I've counted half a dozen reports of people burnt by it and stability concerns can only discourage more people from testing Pharo 6 beta. The answer ever time has been to use vmLatest, so why not someone just log onto the files server and manually rename the current "-latest" to "-stable". Don't take time to determine which "latest" is most stable. Any seems a better choice than the VM with *known* compactor bug. We need a stable-Pre-Release-VM for final beta testing. cheers -ben > > 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] Process scheduling

by Ben Coman

On Sun, Apr 30, 2017 at 10:11 PM, <raffaello.giulietti(a)lifeware.ch> wrote: > 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. > > This topic is probably a bit advanced pharo-users list. You'll likely get better answers in vm-dev list of pharo-dev list. Can you post any follow ups there? ProcessScheduler doesn't have much to do with context switching, except providing the #yield primitive for a user to invoke manually. As you noted, the actual context switching happens in the VM. The charts here [1] might be useful to get an overview of the execution loop. Keep in mind though Its a very rough view of a novice exploring the Cog execution engine and may not be entirely accurate. But it will give you a starting point. For another example, look at CoInterpreterPrimitives>>primitiveEnterCriticalSection in VMMaker (http://source.squeak.org/VMMaker) cheers -ben

April 30, 2017

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

by Ð¥ÑÐ¸ÑÑÐ¸Ð½Ð° ÐÐ¸ÑÐ°Ð¹Ð»ÑÐº

Sabine, thank you very much! It's very helpful, work fine. 2017-04-30 17:09 GMT+03:00 Sabine Manaa <manaa.sabine(a)gmail.com>: > 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] <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=4944953&i=0>>: > >> >> 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-tp49 >> 44784p4944944.html >> To start a new topic under Pharo Smalltalk Users, email [hidden email] >> <http:///user/SendEmail.jtp?type=node&node=4944953&i=1> >> To unsubscribe from Pharo Smalltalk Users, click here. >> NAML >> <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> >> > > > ------------------------------ > View this message in context: Re: Voyage - collecting data from Mongo > <http://forum.world.st/Voyage-collecting-data-from-Mongo-tp4944784p4944953.h…> > > Sent from the Pharo Smalltalk Users mailing list archive > <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at Nabble.com. >

April 30, 2017

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