Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

Hi Peter, thanks. But I will wait for next integration level. I would like to try it but I have to organize my time strictly, so I have no time to play around so much ;-( Regards Sabine 2016-05-26 11:33 GMT+02:00 Peter Uhnák : > Hi, > > > To manage on github there are some

Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

Hi, > To manage on github there are some blog around I wrote a guide for moving from SmalltalkHub to Github http://peteruhnak.com/blog/2016/03/02/moving-project-from-smalltalkhub-to-github/ And Uko wrote about versioning

Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

Hi Steph, thank you for your explanation. I was reading a little bit this morning about pharo and github. I am looking forward to the solution you will provide in future and use sthub till then. Regards Sabine -- View this message in context:

Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

Le 25/5/16 à 21:57, Sabine Manaa a écrit : Hi Esteban, do you know a documentation/entry point about moving to github? To manage on github there are some blog around. Now what we want to offer is something else: We want to have one solution where you can publish using git (but that people

Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

Hi Esteban, do you know a documentation/entry point about moving to github? Is it in experimental state or recommended for all Pharo users? How/where to start? Regards Sabine 2016-05-25 21:54 GMT+02:00 EstebanLM [via Smalltalk] < ml-node+s1294792n489739...@n4.nabble.com>: > Hi, > > yes, I

Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

Hi, yes, I recommend you to use the github version, we are moving there. But anyway we are keeping the sthub as mirror… it just got de-sync. And the only reason why I needed the merge, and not a simple copy is because metadataless format got activated and I lost the history, so I rather merge

Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

Hi Esteban, great, now it works. Thank you! In the comments, I see "merged with github". I am curious about using github in future, too. Regards Sabine 2016-05-25 21:01 GMT+02:00 EstebanLM [via Smalltalk] < ml-node+s1294792n4897378...@n4.nabble.com>: > hi Sabine, > > please update to latest

Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

hi Sabine, please update to latest packages of Voyage… there was a de-sync problem with the API change in MongoTalk, that *should* fix your issue. cheers, Esteban > On 25 May 2016, at 16:29, Sabine Manaa wrote: > > note that it only occurs (hanging image) if you

Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

note that it only occurs (hanging image) if you do "VORepository current reset" before. Or have a new Image. 2016-05-25 15:38 GMT+02:00 Sabine Manaa : > I have a non-responding image with the original code (with the signal) > > 2016-05-25 15:14 GMT+02:00 Holger Freyther

Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

I have a non-responding image with the original code (with the signal) 2016-05-25 15:14 GMT+02:00 Holger Freyther [via Smalltalk] < ml-node+s1294792n4897346...@n4.nabble.com>: > > > On 25 May 2016, at 15:42, Esteban Lorenzano <[hidden email] > >

Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

> On 25 May 2016, at 15:42, Esteban Lorenzano wrote: > > Hi, > No I don’t… in part because is not me who make that code, but also because it > is expected: after, you have: > > getCollection: aString > ^ [ self addCollection: aString capped: false size: nil

Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

> On 25 May 2016, at 15:35, Sabine Manaa wrote: > > Hi Esteban, > > can you please have a look again, I think you forgot to remove the signal here > (remove signal in the ifTrue case then it works): No I don’t… in part because is not me who make that code, but also

Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

Hi Esteban, can you please have a look again, I think you forgot to remove the signal here (remove signal in the ifTrue case then it works): addCollection: aString capped: aCapped size: aSize max: aMax | command | command := SmallDictionary new. command at: 'create' put: aString. aCapped

Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

problem is not in Pharo 5 but in latest version of MongoTalk (who is loaded with Pharo 5 and apparently not with Pharo 4). I already submitted a fix for it, but you need to load latest version (still no configuration). Esteban > On 25 May 2016, at 12:18, Sabine Manaa

[Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

Hi, Is anyone already running Pharo5 with mongoDB already? loading my configurationOf in a new pharo5 image results in a problem with mongDB. loading the same in Pharo4 works fine. I reduced the problem to the following steps for reproduction: 1) start Pharo5 and install VoyageMongo from the