- Pharo-users - lists.pharo.org

Re: ReStore and storing mixed dictionaries

by Offray Vladimir Luna CÃ¡rdenas

Hi John, Thanks. With the improved error message I was able to pin the cause of error better. The issue was that I was declaring the user picture URL as a ZnURL instead of as a string in the reStoreDefinition, but I was not telling ReStore how to store ZnUrl objects. So I made the returning method to give me a string instead of a ZnUrl, which is kind of counterintuitive for the my model, but returned something that ReStore knew how to serialize. I wonder if there is a way, maybe using something like derived keys, to tell reStoreDefinition: execute this block instead of calling the current method to store the value in the database. So, the #profileImageUrl returns a ZnUrl object inside the image model, but is stored as a string in the database without adding more reStoreDefinition for particular objects (like a ZnUrl). Could be this possible in someway? Am I missing something? The objects storing is advancing now and hopefully we will have results soon to share, instead of troubleshooting (but we'll share both anyway ;-P). Cheers, Offray On 7/04/22 16:19, John Aspinall wrote: > Hi Offray - could you try modifying > SSWReStore>>createProxyForNewObject: as follows: > > ... > Â Â Â table := self tableForClass: anObject class. > "Add this ->â Â table isNil ifTrue: [ self error: 'cannot find table > for ', anObject class name ]. > Â Â Â id := table idDataField ifNotNil: [ :idDataField | idDataField > accessor valueIn: anObject]. > Â Â Â â¦ > > This should change the error message to show the class of object which > doesnât have a valid table. > > Thanks. > > John > > >> On 7 Apr 2022, at 20:29, Offray Vladimir Luna CÃ¡rdenas >> <offray.luna(a)mutabit.com> wrote: >> >> Hi John, >> >> Effectively ReStore didn't was storing the table object for the >> Nitter class. But after following your advice, i'm now able to debug >> both the TwitterUser and the NitterUser and obtain the same result >> (which makes sense as the later is inherited from the former). I >> think that my error was related with the definition of the >> synchronized tables, as I was not includingÂ explicitly the >> NitterUser (as I thought it would suffice with the TwitterUser one). >> Now it looks like this: >> >> === >> ReStore connection: (SSWSQLite3Connection on: privateDatabase fullName); >> Â Â Â connect; >> Â Â Â addClasses: { Tweet. "TwitterUser." NitterUser }; >> Â Â Â synchronizeAllClasses. >> === >> >> Now I can get a non nil idDataField that has the same shape when >> #tableForClass: and "reStoreDefinition asTableIn: ReStore" are send >> to TwitterUser and NitterUser. Despite of that I still get the >> pre-commit error: "#idDataField was send to nil". Here is a >> screenshot of the trace of the error and the idDataFiled seems right >> (or at least equal to the same field inÂ the TwitterUser): >> >> https://i.imgur.com/F3UDC93.png >> >> For the moment, I'm planing to use an extra/temporal >> TwitterStoreHelper object that stores via ReStore/SQLite the objects >> I'm unable to store so far, but as dictionaries of key/value helper >> objects, where the value is just the STON serialization of the object >> (with the inconveniences of not being able to query it properly). For >> example, a 'profiles' dictionary in TwitterStoreHelper would have a >> Twitter/Nitter user id as a key and its Ston representation as a >> value. It's a temporal workaround, while I debug the above error further. >> >> I'll keep you posted on the advances and regarding the booklet, I >> answered you in a direct message. >> >> Cheers, >> >> Offray >> >> On 7/04/22 2:59, John Aspinall wrote: >>> Hi Offray, >>> >>> Regarding the error, Iâm guessing that ReStore doesnât have a table >>> object for your NitterUser class for some reason. Could you try: >>> >>> Â Â myReStore tableForClass: NitterUser >>> >>> â¦and check if this is returning nil? If so thereâs an issue with >>> creating the table for the class; you could try stepping through >>> >>> Â Â NitterUser reStoreDefinition asTableIn: myReStore >>> >>> ...to get an idea of whatâs wrong. >>> >>> If this isnât the issue please let me know. >>> >>> Regarding the manual, Iâll send this to you by mail. >>> >>> Cheers. >>> >>> John >>> >>> >>> >>>> On 6 Apr 2022, at 19:48, Offray Vladimir Luna CÃ¡rdenas >>>> <offray.luna(a)mutabit.com> wrote: >>>> >>>> Thanks Jhon, it definitively helps. >>>> >>>> What I did was to extract some important metadata as slots of the >>>> Tweet object and made explicit the authorId, which allows me to >>>> trace tweets authorship: >>>> >>>> === >>>> Tweet>>class #reStoreDefinition >>>> ^ super reStoreDefinition >>>> Â Â Â defineAsID: #id; >>>> Â Â Â define: #text as: String; >>>> Â Â Â define: #created as: String; >>>> Â Â Â define: #authorId as: String; >>>> Â Â Â define: #timelines as: (Dictionary of: String -> String); yourself >>>> >>>> === >>>> >>>> Also I'm going to put in the radar the idea of storing STON strings >>>> for metadata residues. >>>> >>>> On a related matter, I'm still unable to store properly the >>>> NitterUser, which inherits from TwitterUserÂ into SQLite and always >>>> get a pre-commit error: "#idDataField was send to nil" when I ran >>>> "myNitterUser store". Here is my TwitterUser storing definition: >>>> >>>> === >>>> TwitterUser>>class #reStoreDefinition >>>> >>>> Â Â Â ^ super reStoreDefinition >>>> Â Â Â Â Â Â Â Â Â defineAsID: #id; >>>> Â Â Â Â Â Â Â Â Â define: #userName as: String; >>>> Â Â Â Â Â Â Â Â Â define: #profileImageUrl as: String; >>>> Â Â Â Â Â Â Â Â Â define: #profileBio as: String; >>>> Â Â Â Â Â Â Â Â Â "define: #createdAt as: String;" >>>> Â Â Â Â Â Â Â Â Â yourself. >>>> >>>> === >>>> >>>> What I'm missing? And more importantly: how can I debug the >>>> message, so I can asign the proper non nil object as receiver of >>>> #idDataField ? >>>> >>>> Finally (for now ;-) ), the ReStore manual has been and important >>>> learning resource. Are you the author? And if so, would you be so >>>> kind to upload the Word source code to the Documentation/ folder in >>>> the repository under a permissive license that allow at least some >>>> format changes? We would like to add some table of contents and >>>> translate it to other formats, as we have done before with other >>>> free/libre cultural works (see [1] [2]). >>>> >>>> [1] https://mutabit.com/repos.fossil/datafem >>>> [2] https://mutabit.com/repos.fossil/mapeda/ >>>> >>>> Thanks, >>>> >>>> Offray >>>> >>>> On 6/04/22 2:52, John Aspinall wrote: >>>>> Hi Offray, >>>>> >>>>> Youâre correct that ReStore canât store that kind of mixed >>>>> dictionary directly. You could store the entire STON text as one >>>>> string and reify it on read, though that would mean you canât >>>>> easily query on the metadata. >>>>> >>>>> A compromise solution would be to define objects and slots for the >>>>> key data youâd need to query on and a STON string for the residue. >>>>> This could be a better solution anyway as excessive/complex >>>>> Dictionaries can be a sign that you need to define a new >>>>> class/classes. For your particular project this would depend on >>>>> how similar the metadata is between tweets - if thereâs not much >>>>> commonality then a Dictionary approach may be more appropriate. >>>>> >>>>> Hope this helps, >>>>> >>>>> John >>>>> >>>>> >>>>> >>>>>> On 5 Apr 2022, at 20:07, Offray Vladimir Luna CÃ¡rdenas >>>>>> <offray.luna(a)mutabit.com> wrote: >>>>>> >>>>>> Hi all, >>>>>> >>>>>> First of all, despite of being on a non-directly related matter >>>>>> with my question, congrats of Pharo 10. >>>>>> >>>>>> We (as now we have 2 active Smalltalkers in my country... Yay!) >>>>>> are creating a civic tech project with Pharo/Lepiter and we would >>>>>> like to store some Tweet metadata coming from Nitter[1]. As we're >>>>>> dealing with the differences between the official Twitter API and >>>>>> the unofficial Nitter one, we put the metadata we need in a >>>>>> dictionary that has several kinds of objects, from ordered >>>>>> collections to other dictionaries. >>>>>> >>>>>> [1] https://nitter.net/about >>>>>> >>>>>> Currently if we serialize a Tweet object in STON, we get this: >>>>>> >>>>>> Tweet { #created : 'Tue, 05 Apr 2022 12:37:56 GMT', #text : ' >>>>>> >>>>>> [ANN] Pharo 10 Released: pharo.org/news/pharo10-releaâ¦ >>>>>> <https://pharo.org/news/pharo10-released> >>>>>> >>>>>> \n', #id : '1511322244353597443', #user : NitterUser { #userName >>>>>> : 'pharoproject', #profileImageUrl : URL [ >>>>>> 'http://nitter.42l.fr/pic/pbs.twimg.com/profile_images/541743734/icone-pharo…' >>>>>> ] }, #metadata : { 'queries' : OrderedCollection [ { 'date' : >>>>>> DateAndTime [ '2022-04-05T13:36:58.546011-05:00' ], 'parameters' >>>>>> : 'https://nitter.42l.fr/pharoproject' } ], 'timelines' : { >>>>>> 'pharoproject' : '1511048498703126529' } } } >>>>>> >>>>>> As you can see, the metadata slot contains a dictionary with >>>>>> mixed classes of objects. But I read in the ReStore manual[2] (pg >>>>>> 14): >>>>>> >>>>>> """ >>>>>> >>>>>> Like other collections, the class of elements for both key and >>>>>> value can be any other >>>>>> persistent class, and will be the same for all elements of that >>>>>> collection (except in the case of >>>>>> inheritance). >>>>>> >>>>>> """ >>>>>> >>>>>> So, is ReStore unable to store metadata dictionaries like the one >>>>>> described in the previous STON code? if this is possible, how can >>>>>> I define it in the Tweet class>>reStoreDefinition? >>>>>> >>>>>> For the moment, I'm going to create a explicit "timelines" slot >>>>>> to store what was being stored at the #timelines key of the >>>>>> metadata dictionary. But, as metadata increases, instead of >>>>>> moving variables previously inside of a dictionary as explicit >>>>>> slots of an object, I think that having a explicit way of storing >>>>>> dictionaries with different kinds of objects, in contrast with >>>>>> only uniform ones, would be needed (but I don't know if this is >>>>>> in the design scope of ReStore). >>>>>> >>>>>> BTW, Lepiter has allow us to build a pretty fluent interface to >>>>>> browser Twitter/Nitter profiles and messages. Here it is how such >>>>>> UI looks for browsing last @pharoproject tweets: >>>>>> >>>>>> https://i.imgur.com/bxFze1g.png >>>>>> >>>>>> Any help on how to use ReStore in storing mixed dictionaries is >>>>>> appreciated. >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Offray >>>>>> >>>>> >>> >

April 12, 2022

Re: Intended behaviour of flatten and flatCollect:

by Konrad Hinsen

Hi Kasper, Thanks for your reply! > Sorry, but which version of Pharo are we talking about. Sorry, I forgot to say that I am still using Pharo 9. > I just tried with Pharo 10, which has no flatten method for arrays at Interesting. So I double-checked - and found that the "flatten" in my image actually comes from an add-on package called CollectionExtensions (https://github.com/pharo-contributions/CollectionExtensions/blob/master/src…) So I will complain there :-) > I am not going to comment on naming of such core api methods - they tend to have > a 40 year history of forgotten arguments and random âclean upsâ. I agree, I didn't expect any level of homogeneous naming. Just an agreement between code and documentation. Cheers, Konrad

April 12, 2022

Re: Intended behaviour of flatten and flatCollect:

by Kasper Osterbye

Hi Konrad Sorry, but which version of Pharo are we talking about. I just tried with Pharo 10, which has no flatten method for arrays at all, somewhere along the version I believe the method was renamed to flattened. #(1 #(2 #(a b) 3) 4) flattened >>> #(1 2 #a #b 3 4) as one would expect. flatCollect: does not flatten the collection it is called on, but the result produced by the block #(1 3) flatCollect: [ :e | {e. e * 10} ] >>> #(1 10 3 30), and #(1 #(2 3 #(4 5)) 6) flatCollect: [ :e | {e. e * 10} ] >>> #(1 10 #(2 3 #(4 5)) #(20 30 #(40 50)) 6 60) I am not going to comment on naming of such core api methods - they tend to have a 40 year history of forgotten arguments and random âclean upsâ. Best, Kasper > On 12 Apr 2022, at 11.51, Konrad Hinsen <konrad.hinsen(a)fastmail.net> wrote: > > Hi everyone, > > I am getting surprising results trying to flatten nested arrays. So I > read the docstrings. And now I understand even less how flatten and > flatCollect are supposed to work. > > flatten says: > > "Recursively collect each non-collection element of the receiver and > its descendant collections. Please note, this implementation > assumes that strings are to be treated as objects rather than as > collection." > > That suggests that > > #(1 2 3) flatten > > should yield #(1 2 3). But it raises an exception, trying to send do: to > an integer. > > A quick look at the code shows that flatten is just flatCollect: [ > :each | each ]. flatCollect: says: > > "Evaluate aBlock for each of the receiver's elements and answer the > list of all resulting values flatten one level. Assumes that aBlock > returns some kind of collection for each element. Equivalent to the > lisp's mapcan" > > "Flatten one level" is different from flatten's "recursively". The > assumption that aBlock returns a collection is also incompatible with > what flatten is supposed to do (and explains my exception). > > I don't find the reference to a Lisp function very helpful. Assuming > "Lisp" means "Common Lisp", this confirms the docstring of flatCollect:, > this confirms the assumption of aBlock returning a collection, and that > only one level of nesting is flattened. > > Since flatCollect does what it says, the problem seems to be in > flatten. Either its docstring or its implementation are wrong. > > Or is it me misunderstanding something? > > Cheers, > Konrad

April 12, 2022

Intended behaviour of flatten and flatCollect:

by Konrad Hinsen

Hi everyone, I am getting surprising results trying to flatten nested arrays. So I read the docstrings. And now I understand even less how flatten and flatCollect are supposed to work. flatten says: "Recursively collect each non-collection element of the receiver and its descendant collections. Please note, this implementation assumes that strings are to be treated as objects rather than as collection." That suggests that #(1 2 3) flatten should yield #(1 2 3). But it raises an exception, trying to send do: to an integer. A quick look at the code shows that flatten is just flatCollect: [ :each | each ]. flatCollect: says: "Evaluate aBlock for each of the receiver's elements and answer the list of all resulting values flatten one level. Assumes that aBlock returns some kind of collection for each element. Equivalent to the lisp's mapcan" "Flatten one level" is different from flatten's "recursively". The assumption that aBlock returns a collection is also incompatible with what flatten is supposed to do (and explains my exception). I don't find the reference to a Lisp function very helpful. Assuming "Lisp" means "Common Lisp", this confirms the docstring of flatCollect:, this confirms the assumption of aBlock returning a collection, and that only one level of nesting is flattened. Since flatCollect does what it says, the problem seems to be in flatten. Either its docstring or its implementation are wrong. Or is it me misunderstanding something? Cheers, Konrad

April 12, 2022

[ANN] Stargate-Consul v4.0.0 [v4.0.0] released!

by Buenos Aires Smalltalk

April 11, 2022

[ANN] Superluminal v4.0.0 [v4.0.0] released!

by Buenos Aires Smalltalk

April 11, 2022

Re: list archive search broken

by Marcus Denker

It is fixed! The provider provider fixed it quickly. Marcus > On 6 Apr 2022, at 09:08, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > Thanks, I will open a Ticket with the provider. > > All in all, I am not that happy with Empathyâ¦ maybe we should start looking for an alternative > hosting provider for the mailing lists. > > Marcus > >> On 6 Apr 2022, at 00:01, PAUL DEBRUICKER <pdebruic(a)gmail.com> wrote: >> >> the Empathy search box here: https://lists.pharo.org/empathy/list/pharo-users.lists.pharo.org >> >> Doesn't work. Not sure if thats something everyone knows and is working on or not as I can't search the list to see because doing in the normal way with google also doesn't work or comes up empty.... e.g. googling >> >> >> search box site:https://lists.pharo.org/empathy/list/pharo-users.lists.pharo.org >> >> search box site:https://lists.pharo.org/ >> >> >> >> Thanks >> >> >

April 11, 2022

[ANN] Stargate v8.0.0 [v8.0.0] released!

by Buenos Aires Smalltalk

April 8, 2022

Re: Installing code in a running image

by Davide Varvello

Thanks Tim, that's a valid question, I don't love git so much, we have the code repository versioned on mercurial and we are also trying to have no more that a single baseline in production. On customers' machines should run only a small portion of code so I guess CodeImporter is enough, but I'll feedback the list within some days with my results ;-) Thanks for helpingCheersDavide On Monday, April 4, 2022, 03:31:42 PM GMT+2, Tim Mackinnon <tim(a)testit.works> wrote: From memory - the Excercism project does this too (can't recall if it uses CodeImporter, but it does get source from Exercism and load it into the image). Having said this - are you sure you don't want to have some versioned packed in git that your image can load up when needed? It would add a version control element for you which might make sense. Tim On Mon, 4 Apr 2022, at 2:15 PM, Davide Varvello via Pharo-users wrote: Thanks Markus It seems CodeImporter is the right tool Davide On Monday, April 4, 2022, 11:41:50 AM GMT+2, Marcus Denker <marcus.denker(a)inria.fr> wrote: On 1 Apr 2022, at 18:35, Davide Varvello via Pharo-users <pharo-users(a)lists.pharo.org> wrote: Hi Folks! For a customer of mine I want to download a bunch of new code from my webserver and installing it in a running Pharo image, is there a feasible way to do it? Maybe you could just have file-outs on the server and then just load it with CodeImporter? Reading from a URL: ZnClient new get: âsomeURLâ. Loading file outs from a String: CodeImporter class>>#evaluateString: Marcus

April 8, 2022

Re: [ANN] Pharo 10 released!

by vinref＠gmail.com

Looking forward to doing some serious work with Pharo. Thanks for all the hard work that has gone into Pharo over the years. Marcus Denker wrote: > I added an issue tracker entry as I have no idea where/how to fix itâ¦ > > ``` > PharoLauncher: List Pharo10 as stable #11102 > https://github.com/pharo-project/pharo/issues/11102 > ``` This is the page that has to be updated: https://files.pharo.org/pharo-launcher/sources.list Vince

April 8, 2022