- Pharo-users - lists.pharo.org

Understanding DateTime and Locale and formatting times in a locale?

by Tim Mackinnon

Hi - Iâm really confused about DateAndTime support in Pharo? If I have a server app running in the EU, and a user makes a request from Canada, and I want to format the time they see to be in their timezone - how do I do that with the classes in Pharo? I can ask for a DataAndTime nowUTC, and if I know the user is in en-CA, I can create a Locale for them - but then how do I get the correct time offset, or how to I format that UTC date in their locale? Tim

July 14, 2017

Re: [Pharo-users] VoyageMongo not working in Pharo 6?

by Esteban Lorenzano

mmm yes, seems that we forget to update the catalog version. I will do it soon, but for the moment, please install using this: Metacello new repository: 'github://pharo-nosql/voyage:1.5/mc'; baseline: 'Voyage'; load: 'mongo tests'. cheers! Esteban > On 14 Jul 2017, at 15:00, kmo <voxkmp(a)gmail.com> wrote: > > Is this what you wanted? > > ConfigurationOfVoyageMongo>>stable: > > stable: spec > <symbolicVersion: #'stable'> > > spec for: #'common' version: '1.4'. > spec for: #'pharo1.4.x' version: '1.1.1'. > spec for: #'pharo2.0.x' version: '1.2.7'. > spec for: #'pharo3.x' version: '1.3.1'. > spec for: #'pharo4.x' version: '1.3.3'. > spec for: #'pharo5.x' version: '1.4'. > > > > -- > View this message in context: http://forum.world.st/VoyageMongo-not-working-in-Pharo-6-tp4954843p4954869.… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

July 14, 2017

Re: [Pharo-users] VoyageMongo not working in Pharo 6?

by kmo

Thanks -- View this message in context: http://forum.world.st/VoyageMongo-not-working-in-Pharo-6-tp4954843p4954893.… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 14, 2017

Re: [Pharo-users] VoyageMongo not working in Pharo 6?

by kmo

Is this what you wanted? ConfigurationOfVoyageMongo>>stable: stable: spec <symbolicVersion: #'stable'> spec for: #'common' version: '1.4'. spec for: #'pharo1.4.x' version: '1.1.1'. spec for: #'pharo2.0.x' version: '1.2.7'. spec for: #'pharo3.x' version: '1.3.1'. spec for: #'pharo4.x' version: '1.3.3'. spec for: #'pharo5.x' version: '1.4'. -- View this message in context: http://forum.world.st/VoyageMongo-not-working-in-Pharo-6-tp4954843p4954869.… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 14, 2017

Re: [Pharo-users] Peristence with SandStone or Voyage -> Bypassing the saving of a variable.

by sergio ruiz

Oh! good idea.. iâll take a look..Â i ended up throwing them into a temp variable.. then saving.. then bringing it back.. thanks! On July 14, 2017 at 2:20:42 AM, Sabine Manaa (manaa.sabine(a)gmail.com) wrote: have a look at VOTransientDescription I also have attributes which are not persistent. I define them at class side like this: mongoAccountingRecords Â Â Â Â <mongoDescription>Â Â Â Â Â ^ VOTransientDescription newÂ Â Â Â Â Â Â Â Â attributeName: 'accountingRecords';Â Â Â Â Â Â Â Â Â yourselfÂ Regards Sabine ---- peace, sergio photographer, journalist, visionary Public Key:Â http://bit.ly/29z9fG0 #BitMessageÂ BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.Village-Buzz.com http://www.ThoseOptimizeGuys.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

July 14, 2017

Re: [Pharo-users] Seamless - send collections by value

by Denis Kudriashov

Hi Petr. There are few solutions to your problem. 1) You can specify #value strategy for any collections for your network instance: network transferByValue: (Kind of: Collection) For your example you need to apply this strategy on server side. In that case client will continue send collections by reference but it will receive collections by value from server. 2) You can specify value strategy for BlockClosure. It will perform #select: (for example) on server side without requests to client. network transferByValue: (Instance of: BlockClosure) Here you will need to apply strategy on client because blocks will be sent from client to server. 3) You can explicitly pass objects with value strategy: YourService>>getPersons "on server side" ^retrievePersons asTransferredByValue 4) If persons collection is instance variable of other transferred by value object then you can specify what value means for this container: PersonContainer>>prepareValueTransferBy: aSeamlessObjectTransporter aSeamlessObjectTransporter transferByValue: contents 5) You can ask any proxy to load local copy of remote object: proxy asLocalObject. Important notice: - Seamless has no distributed garbage collection. So if you will transfer by reference temporary objects they will be not collected as garbage. For example server could compute something and return it by reference. Nobody will kill it. But if you share only long lived service then it is not problem for you. - there is no security in the level of Seamless. You should organize secure channel by external tools like VPN. These features are in todo. Best regards, Denis 2017-07-13 18:21 GMT+02:00 Petr Fischer <petr.fischer(a)me.com>: > Hello, I am testing Seamless project (https://github.com/ > dionisiydk/Seamless) but I did not understand one thing: > > I have (for example) a Person class in my server and client image. Person > class implements: > > Person>>sseamlessDefaultTransferStrategy > ^SeamlessTransferStrategy defaultByValue > > so all Person instances are serialized from server to client image. Good. > > But when I have server method, for example, getPersons, that returns a > collection (OrderedCollection) of Person instances, this collection is > passed by reference (or not?). > OrderedCollection inherits transfer strategy from Object, which is "by > reference". > > So in client image, when I iterate this collection, too many (thousands) > requests occurs. > > How to manage only this specific collection (returned from getPersons) to > pass by value from server to client (to be completely serialized and copied > to the client image), so when I iterate this collection in client image to > avoid additional network requests (proxying)? > > Thanks! pf > >

July 14, 2017

Re: [Pharo-users] Is there a 64bit minimal image for either 6.0 or 7.0?

by Tim Mackinnon

Hi Guille - thanks for replying and giving me some insight into all of this. I have managed to get something working but there are definitely some issues that may need a bug report? As I initially mentioned - if I download the Linux 64bit VM (curl get.pharo.org/64/ | bash) and then use the minimal image suggested by Pavel (https://ci.inria.fr/pharo/job/Pharo-6.0-Update-Step-3.2-Minimal/lastSuccess… <https://ci.inria.fr/pharo/job/Pharo-6.0-Update-Step-3.2-Minimal/lastSuccess…>) I immediately hit a problem: This minimal image supports Metacello, and the ST command line handler - however it us unable to process a script like the following (which is attempting to load a local filetree git package) Metacello new repository: 'filetree://../src'; baseline: 'Lambda'; load. It fails because Metacello wants to use STON class>>readFromStream (in its #repositoryProperties method)- this minimal image does not contain STON (which is an error? Too much has been removed). If I try to workaround this by loading STON as follows using the CONFIG command line handler: ./pharo Pharo.image config http://ss3.gemstone.com/ss/STON ConfigurationOfSton --install=stable âsave this then highlights several other issues: 1) ConfigurationOfSton doesnât have a group load will load it without Tests, and so loading it provides a series of errors due to TestCase not being in the min image (and there doesnât appear to be a Configuration for loading SUnit by itelsf?) - I think this should be solved by either keeping STON in the image and/or having a config of Ston that loads without tests 2) Having loaded STON into that min image (albeit with broken Test cases), the minimal image doesnât seem to use the Undeclared mechanism you describe and so the following classes (which have references to STON) - all need to be force recompiled like this: { MCFileTreeRepository. MCFileTreeStCypressReader. MCFileTreeAbstractReader } do: [:c | c compileAll ]. Otherwise I get an Undefined talkback when I try my metacello load, which I do using the ST command handler. Having dealt with 1 & 2, I am then able to run my Metacello load (as shown at the top). So it appears that there are a few related problems here. I have a running example of this in Gitlab that demonstrates this - and can be used to replicate this problem if that helps (although the description is pretty clear I think). Tim > On 14 Jul 2017, at 11:14, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Two different things: > > 1) yes, the minimal image is indeed minimal. Actually, the minimal image is around 20% of the full image. Two working directions that are looking for active contributions are: > - reduce that 20% so bootstrap times are smaller > - modularise the other 80% so that we can easily load new stuff. > About this last point, there are already there in the repository a couple of metacello configurations made by Pavel that allow us to reload the 80% into the 20% image. But we should modularise them because so far they are too big. > > 2) About the second point. You should not need to recompile everything. In the image there is the Undeclared mechanism that should rebind new classes as soon as they are loaded. Can you provide more insight on the bug? Why do you need to recompile? > > Tx, > Guille > > On Thu, Jul 13, 2017 at 7:55 PM, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: > I think there is something wrong with the minimal image - but it looks like the following has nudged me a bit closer (rather inelegantly but I think the minimal images may need checking for errors): > > MCFileTreeRepository methods do: [ :m | m recompile ]. > MCFileTreeStCypressReader methods do: [:m | m recompile ]. > MCFileTreeAbstractReader methods do: [:m | m recompile ]. > Tim > >> On 13 Jul 2017, at 18:18, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >> >> Thinking about this a bit more - if the minimal image is too minimal, and I load in some required classes - do I need to force methods to recompile to pick up the now loaded classes? >> >> Is there an easy way to do that? >> >> Tim >> >>> On 13 Jul 2017, at 17:40, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >>> >>> Hmmm - its very, very minimalâ¦ I am trying to load in my local code (checked out from git) with: >>> >>> Metacello new >>> repository: 'filetree://../src <>'; >>> baseline: 'Lambda'; >>> load. >>> >>> However I get an error: MCFileTreeRepository>>repositoryProperties (STON is Undeclared) >>> >>> As Iâm guessing that STON is not in that minimal image - I have tried to load ConfigurationOfSton into the image first by doing: >>> ./pharo Pharo.image config http://ss3.gemstone.com/ss/STON <http://ss3.gemstone.com/ss/STON> ConfigurationOfSton --install=stable â-save >>> >>> It looks like this does load it, however when I then run my commands to load my code into the new image with: >>> ./pharo Pharo.image --no-default-preferences --save --quit st loadLocal.st <http://loadlocal.st/> >>> (loadLocal.st <http://loadlocal.st/> has the Metacello expression I first mentioned) - I still seem to be getting an error as if STON is not in the image, >>> E.g. >>> UndefinedObject class>>fromStream: >>> And PharoDebug has lines confirming this (pointing at the method #repositoryProperties): >>> 27 MessageNotUnderstood(Exception)>>signal >>> 28 UndefinedObject class(Object)>>doesNotUnderstand: #fromStream: >>> 29 repositoryProperties >>> repositoryProperties >>> ifNil: [ >>> >>> At this point, I am having trouble loading this minimal image with a ui, but if I use the command line and use the âevalâ command line handler, and do something like: >>> ./pharo Pharo.image eval "(Smalltalk at: #STONReader) class methods" >>> {STONReader class>>#on:} >>> It is showing me methods as if the class is there. Can anyone think of what I might be doing wrong? Or could try? >>> >>> Tim >>> >>>> On 13 Jul 2017, at 08:47, Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>> wrote: >>>> >>>> For Pharo 6: https://ci.inria.fr/pharo/job/Pharo-6.0-Update-Step-3.2-Minimal/lastSuccess… <https://ci.inria.fr/pharo/job/Pharo-6.0-Update-Step-3.2-Minimal/lastSuccess…> >>>> For Pharo 7: https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit-Conversion/lastSu… <https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit-Conversion/lastSu…> >>>> >>>> -- Pavel >>>> >>>> 2017-07-13 8:10 GMT+02:00 Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>>: >>>> That would be great. I'm keen to see if I can reproduce what Sven seemed to measure where he seemed to get image launch times down. >>>> >>>> Currently on Lambda I am seeing an avg 3.5s to return a simple result. >>>> >>>> I know that 700ms of this is the overhead of a nodejs shim (the golang Sparta project has reported this aspect). >>>> >>>> So I'm curious if a smaller image (& no sources) could get me into a sub 2s range) >>>> >>>> Tim >>>> >>>> Sent from my iPhone >>>> >>>> >>>> >>>> Sent from my iPhone >>>> On 13 Jul 2017, at 06:51, Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>> wrote: >>>> >>>>> Hi Tim, >>>>> >>>>> I will prepare jobs that will convert them to 64bits. >>>>> >>>>> -- Pavel >>>>> >>>>> 2017-07-12 23:14 GMT+02:00 Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>>: >>>>> Hi - I would like to try a minimal image on AWS lambda (so I need a 64 bit version). >>>>> >>>>> Is there a 64bit image for either 6.0 or 7.0 that is easy to download? >>>>> >>>>> I can see - http://get.pharo.org/60-minimal <http://get.pharo.org/60-minimal> but it doesnât say its 64 bit, so I assume its 32bit? >>>>> >>>>> Tim >>>>> >>>> >>> >> > > > > > -- > > Guille Polito > > Research Engineer > French National Center for Scientific Research - http://www.cnrs.fr <http://www.cnrs.fr/> > > > Web: http://guillep.github.io <http://guillep.github.io/> > Phone: +33 06 52 70 66 13

July 14, 2017

Re: [Pharo-users] VoyageMongo not working in Pharo 6?

by Esteban Lorenzano

> On 14 Jul 2017, at 11:31, kmo <voxkmp(a)gmail.com> wrote: > > I just had a quick tryout of VoyageMongo in Pharo 6 and > VOMongoRepository>>save:anObject fails because UUIDGenerator does not have > the method makeSeed. > > UUIDGenerator >> makeSeed was present in pharo 5. It's not there in pharo 6. > > I installed from the Catalog browser where VoyageMongo is listed as being OK > for pharo 6. yes, this should not happen. can you share which version of VoyageMongo are you installing? (is on ConfigurationOfVoyageMongo>>stable: method) Esteban > > > > > -- > View this message in context: http://forum.world.st/VoyageMongo-not-working-in-Pharo-6-tp4954843.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

July 14, 2017

Re: [Pharo-users] Is there a 64bit minimal image for either 6.0 or 7.0?

by Guillermo Polito

Two different things: 1) yes, the minimal image is indeed minimal. Actually, the minimal image is around 20% of the full image. Two working directions that are looking for active contributions are: - reduce that 20% so bootstrap times are smaller - modularise the other 80% so that we can easily load new stuff. About this last point, there are already there in the repository a couple of metacello configurations made by Pavel that allow us to reload the 80% into the 20% image. But we should modularise them because so far they are too big. 2) About the second point. You should not need to recompile everything. In the image there is the Undeclared mechanism that should rebind new classes as soon as they are loaded. Can you provide more insight on the bug? Why do you need to recompile? Tx, Guille On Thu, Jul 13, 2017 at 7:55 PM, Tim Mackinnon <tim(a)testit.works> wrote: > I think there is something wrong with the minimal image - but it looks > like the following has nudged me a bit closer (rather inelegantly but I > think the minimal images may need checking for errors): > > MCFileTreeRepository methods do: [ :m | m recompile ]. > MCFileTreeStCypressReader methods do: [:m | m recompile ]. > MCFileTreeAbstractReader methods do: [:m | m recompile ]. > > Tim > > On 13 Jul 2017, at 18:18, Tim Mackinnon <tim(a)testit.works> wrote: > > Thinking about this a bit more - if the minimal image is too minimal, and > I load in some required classes - do I need to force methods to recompile > to pick up the now loaded classes? > > Is there an easy way to do that? > > Tim > > On 13 Jul 2017, at 17:40, Tim Mackinnon <tim(a)testit.works> wrote: > > Hmmm - its very, very minimalâ¦ I am trying to load in my local code > (checked out from git) with: > > Metacello new > repository: 'filetree://../src'; > baseline: 'Lambda'; > load. > > > However I get an error: MCFileTreeRepository>>repositoryProperties (STON > is Undeclared) > > As Iâm guessing that STON is not in that minimal image - I have tried to > load ConfigurationOfSton into the image first by doing: > > ./pharo Pharo.image config http://ss3.gemstone.com/ss/STON ConfigurationOfSton --install=stable â-save > > It looks like this does load it, however when I then run my commands to load my code into the new image with: > > ./pharo Pharo.image --no-default-preferences --save --quit st loadLocal.st <http://loadlocal.st/> > > (loadLocal.st <http://loadlocal.st/> has the Metacello expression I first mentioned) - I still seem to be getting an error as if STON is not in the image, > > E.g. > > UndefinedObject class>>fromStream: > > And PharoDebug has lines confirming this (pointing at the method #repositoryProperties): > > 27 MessageNotUnderstood(Exception)>>signal > > 28 UndefinedObject class(Object)>>doesNotUnderstand: #fromStream: > 29 repositoryProperties > repositoryProperties > ifNil: [ > > > At this point, I am having trouble loading this minimal image with a ui, but if I use the command line and use the âevalâ command line handler, and do something like: > > ./pharo Pharo.image eval "(Smalltalk at: #STONReader) class methods" > {STONReader class>>#on:} > > It is showing me methods as if the class is there. Can anyone think of what I might be doing wrong? Or could try? > > > Tim > > > On 13 Jul 2017, at 08:47, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > For Pharo 6: https://ci.inria.fr/pharo/job/Pharo-6.0-Update-Step-3.2- > Minimal/lastSuccessfulBuild/artifact/Pharo-minimal-64.zip > For Pharo 7: https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap- > 32bit-Conversion/lastSuccessfulBuild/artifact/latest-minimal-64.zip > > -- Pavel > > 2017-07-13 8:10 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: > >> That would be great. I'm keen to see if I can reproduce what Sven seemed >> to measure where he seemed to get image launch times down. >> >> Currently on Lambda I am seeing an avg 3.5s to return a simple result. >> >> I know that 700ms of this is the overhead of a nodejs shim (the golang >> Sparta project has reported this aspect). >> >> So I'm curious if a smaller image (& no sources) could get me into a sub >> 2s range) >> >> Tim >> >> Sent from my iPhone >> >> >> >> Sent from my iPhone >> On 13 Jul 2017, at 06:51, Pavel Krivanek <pavel.krivanek(a)gmail.com> >> wrote: >> >> Hi Tim, >> >> I will prepare jobs that will convert them to 64bits. >> >> -- Pavel >> >> 2017-07-12 23:14 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: >> >>> Hi - I would like to try a minimal image on AWS lambda (so I need a 64 >>> bit version). >>> >>> Is there a 64bit image for either 6.0 or 7.0 that is easy to download? >>> >>> I can see - http://get.pharo.org/60-minimal but it doesnât say its 64 >>> bit, so I assume its 32bit? >>> >>> Tim >>> >> >> > > > > -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

July 14, 2017

VoyageMongo not working in Pharo 6?

by kmo

I just had a quick tryout of VoyageMongo in Pharo 6 and VOMongoRepository>>save:anObject fails because UUIDGenerator does not have the method makeSeed. UUIDGenerator >> makeSeed was present in pharo 5. It's not there in pharo 6. I installed from the Catalog browser where VoyageMongo is listed as being OK for pharo 6. -- View this message in context: http://forum.world.st/VoyageMongo-not-working-in-Pharo-6-tp4954843.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 14, 2017