August 2013 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Postmark email library

by StÃ©phane Ducasse

> It's work fine! Excellent. > Tested on clean image of pharo 2.0. > > Thank you! Now you have to read the metacello chapter ;D and have success coding in Pharo. And if you see glitches or space for improvements in Postmark, please do not hesitate. > > -- > View this message in context: http://forum.world.st/Postmark-email-library-tp4254680p4705969.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Aug. 31, 2013

Re: [Pharo-users] Postmark email library

by vmusulainen

It's work fine! Tested on clean image of pharo 2.0. Thank you! -- View this message in context: http://forum.world.st/Postmark-email-library-tp4254680p4705969.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 31, 2013

Re: [Pharo-users] Voyage: image freeze/VOMongoError: Lazy reference not found

by Esteban A. Maringolo

2013/8/31 Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com>: > Hi Esteban, > > til now, it did not come back to me. > Can you reproduce it with a fresh image? The image freezed, but fortunately with a LOT of patience I was able to type a character every once in a while. So I could write an smalltalk expression that after being evaluated opened a debugger and caused the image to get responsive again. The expression was a last resort in order to "cause" another error that could give me the control back. VOLazyProxy allInstances do: [:each | each become: String new ] It worked. > Btw I am saving my image now each hour or so... I'm not used to do it, I trust in the changes file, the problem is that I saved the image with the offending proxy. The problem was a modification of a document in a collection. I did a mongo upsert that changed it, and apparently Voyage didn't know how to handle it. Regards!

Aug. 31, 2013

Re: [Pharo-users] Voyage: image freeze/VOMongoError: Lazy reference not found

by Sabine KnÃ¶fel

Hi Esteban, til now, it did not come back to me. Can you reproduce it with a fresh image? Btw I am saving my image now each hour or so... Sabine On Sat, Aug 31, 2013 at 5:46 PM, Esteban A. Maringolo [via Smalltalk] < ml-node+s1294792n4705953h38(a)n4.nabble.com> wrote: > I've been bitten by this too. > This is when the "image" concept get counterproductive if you didn't > commit all your code changes. :-/ > > Esteban A. Maringolo > > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://forum.world.st/Voyage-image-freeze-VOMongoError-Lazy-reference-not-f… > To unsubscribe from Voyage: image freeze/VOMongoError: Lazy reference not > found, 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-image-freeze-VOMongoError-Lazy-reference-not-f… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 31, 2013

Re: [Pharo-users] Voyage: image freeze/VOMongoError: Lazy reference not found

by Esteban A. Maringolo

I've been bitten by this too. This is when the "image" concept get counterproductive if you didn't commit all your code changes. :-/ Esteban A. Maringolo

Aug. 31, 2013

Re: [Pharo-users] Postmark email library

by StÃ©phane Ducasse

> Gofer new > url: 'http://smalltalkhub.com/mc/PharoExtras/Postmark/main' ; > package: 'ConfigurationOfPostMark'; > load. > (ConfigurationOfPostMark project version: '1.0') load: 'Tests' Stef

Aug. 31, 2013

Re: [Pharo-users] Postmark email library

by vmusulainen

StÃ©phane Ducasse wrote > Gofer new > repository: 'http://smalltalkhub.com/mc/PharoExtras/Postmark/main' ; > package: 'ConfigurationOfPostMark'; > load. > (ConfigurationOfPostMark project version: '1.0') load: 'Tests' MessageNotUnderstood: ByteString>>goferReferences -- View this message in context: http://forum.world.st/Postmark-email-library-tp4254680p4705934.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 31, 2013

Re: [Pharo-users] voyage/mongo randomly wrong OIDs

by Sven Van Caekenberghe

On 31 Aug 2013, at 13:47, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Sabine > what we could do is to propose a "subclass of UUID" and to group several UUID generators. > Like that with a couple of classes, we could get a better eco system where people can pick the one they want. > > stef I just made my own, called NeoUUIDGenerator, http://www.smalltalkhub.com/#!/~SvenVanCaekenberghe/Neo/packages/Neo-UUID @Sabine IMHO what I think a local counter does not, is give you uniques over different machines, images, instances - that is why there is also the concept of node identification. In my implementation I combine the millisecond clock, a small random number, a counter and a node id. The node id is based on several elements, it should be different when running multiple images. This is a hack, not something that I can prove mathematically. But it can't be worse than pure random. I think the speed is also acceptable: | generator | generator := NeoUUIDGenerator new. [ generator next ] bench. '408,000 per second.' | generator | generator := UUIDGenerator new. [ generator generateBytes: UUID nilUUID forVersion: 4 ] bench. '13,300 per second.' Sven > On Aug 31, 2013, at 11:49 AM, Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com> wrote: > >> Hi Esteban, >> >> yes, Mongo is not very communicative ;-) >> >> I replaced OID>>nextOID with my own RKAOIDGenerator >> >> nextOID >> ^self value: (RKAOIDGenerator getNextOID) >> >> instead of >> >> nextOID >> ^self value: (UUIDGenerator default makeSeed) >> >> >> RKAOIDGenerator uses Time>>primMillisecondClock at startup and adds +1 each time I getNextOID as you suggested. >> >> This works fine. It seems to be much much much faster than the existing solution. >> >> [4000 timesRepeat: [UUIDGenerator default makeSeed]] timeToRun ==>> 5817 >> [4000 timesRepeat: [RKAOIDGenerator getNextOID]] timeToRun ==> 1 (!!) >> >> Perhaps a solution like this would be a better solution for all because it is faster and guarantees unique IDs? >> >> Sabine >> >> >> >> >> >> On Fri, Aug 30, 2013 at 5:58 PM, EstebanLM [via Smalltalk] <[hidden email]> wrote: >> Hi, >> >> One idea (not sure if it will work) >> >> You can take >> >> Time primUTCMicrosecondsClock >> >> when system start, then increase it sequentially. >> most probably that will ensure uniqueness while providing fast ids. >> >> but of course, that depends, you need to check in your system. >> >> I'm thinking on provide different ID generators for Voyage, and let people plug what is more convenient for them. >> >> (all of this happens because, unlike other db drivers, mongo does not answer the inserted id :( ) >> >> Esteban >> >> On Aug 30, 2013, at 5:41 PM, Sabine KnÃ¶fel <[hidden email]> wrote: >> >> > So, I will wait and till then, use the solution of Jan. >> > Thank you, Jan for the file in. >> > Sabine >> > >> > >> > >> > -- >> > View this message in context: http://forum.world.st/voyage-mongo-randomly-wrong-OIDs-tp4705396p4705821.ht… >> >> > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> > >> >> >> >> >> If you reply to this email, your message will be added to the discussion below: >> http://forum.world.st/voyage-mongo-randomly-wrong-OIDs-tp4705396p4705827.ht… >> To unsubscribe from voyage/mongo randomly wrong OIDs, click here. >> NAML >> >> >> View this message in context: Re: voyage/mongo randomly wrong OIDs >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Aug. 31, 2013

Re: [Pharo-users] Postmark email library

by StÃ©phane Ducasse

So i worked and now can you try on a Pharo2.0 image the following Gofer new repository: 'http://smalltalkhub.com/mc/PharoExtras/Postmark/main' ; package: 'ConfigurationOfPostMark'; load. (ConfigurationOfPostMark project version: '1.0') load: 'Tests' Stef

Aug. 31, 2013

Re: [Pharo-users] Postmark email library

by StÃ©phane Ducasse

Grease is handled by the configuration. So this is already that :) > thanks! > misdeclaring dependencies is the source of future hell :) > I just deleted the wrong repository and I'm having a look now. > > Stef > > On Aug 31, 2013, at 1:55 PM, vmusulainen <vmusulainen(a)mail.ru> wrote: > >> StÃ©phane Ducasse wrote >>> I will fix the configruation and ask you to try. >> >> I found another dependency: >> >> Method PMInterface>>send: uses class GRPharoUtf8Codec. This class exists in >> package "Grease-Pharo-Core" (Seaside framework). >> >> >> >> >> >> -- >> View this message in context: http://forum.world.st/Postmark-email-library-tp4254680p4705915.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> > >

Aug. 31, 2013