- Pharo-dev - lists.pharo.org

VoyageMongo and cache compaction

by Holger Freyther

Hi guys, I started to run a production load with VoyageMongo and every day the maximum latency of it goes up a bit. Today I looked at the production system and the VOMongoRepository and the VOMongoCache and saw that the cache had around 90 entries in the "objects" WeakValueDictionary all pointing to nil 34k entries in the timestamp dictionary This is a write "heavy" workload but at no point in time more than a couple of objects will be in the cache. So somehow the VOMongoCache>>#compactIfNeeded check does not trigger and/or given the difference in the sizes of the dictionary it is possible that some of the dead objects are not removed from the timestamp cache. I have accidentally restarted one image and flushed the cache on the other but if it is of any help I can wait a day or two and then look at the compactLimit again. But even right now in one image the compactLimit is 3277, the objects dictionary has 142 entries and the timestamp one 272. Is this a known issue? Does this look like "normal"/"good" operation? kind regards holger

Dec. 3, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50482 Home: https://github.com/pharo-project/pharo-core

Dec. 3, 2015

[pharo-project/pharo-core] e5a9d5: 50482

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: e5a9d5fb62466db4fa8eeb32b048bba460adfaeb https://github.com/pharo-project/pharo-core/commit/e5a9d5fb62466db4fa8eeb32… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-12-03 (Thu, 03 Dec 2015) Changed paths: M NECompletion-Tests.package/NECContextTest.class/instance/tests/testCreateModel.st M NECompletion.package/NECContext.class/instance/accessing/createModel.st R Refactoring-Core.package/RBDeprecateMethodRefactoring.class/class/as yet unclassified/model_deprecateMethod_in_using_.st A Refactoring-Core.package/RBDeprecateMethodRefactoring.class/class/intance creation/model_deprecateMethod_in_using_.st R Refactoring-Core.package/RBDeprecateMethodRefactoring.class/instance/transforming/formDeprecatedMethod.st R Refactoring-Core.package/RBDeprecateMethodRefactoring.class/instance/transforming/formRewriteRule.st M Refactoring-Core.package/RBDeprecateMethodRefactoring.class/instance/transforming/transform.st R Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/README.md R Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/definition.st R Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/instance/failure tests/testTooManyArguments.st R Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/instance/failure tests/testWrongNumberOfArguments.st R Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/instance/tests/testDeprecateMethod.st R Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/instance/tests/testDeprecateMethodOnClassSide.st R Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/instance/tests/testDeprecateMethodWithLotsOfArguments.st R Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/instance/tests/testDeprecateMethodWithSenders.st R Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/instance/tests/testDeprecateMethodWithSendersInSubclass.st R Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/instance/tests/testSenderNotSelf.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50481.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50482.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50481.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50482.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Slot-Tests.package/SlotTest.class/instance/as yet unclassified/testAsSlotCollection.st M Slot.package/extension/String/instance/asSlotCollection.st A Slot.package/extension/String/instance/asValidInstVarName.st Log Message: ----------- 50482 17176 Simplify Deprecation refactoring https://pharo.fogbugz.com/f/cases/17176 17171 String>>#asSlotCollection parsing does not handle non valid characters https://pharo.fogbugz.com/f/cases/17171 17166 bad completion suggestions on method definitions https://pharo.fogbugz.com/f/cases/17166 http://files.pharo.org/image/50/50482.zip

Dec. 3, 2015

Re: [Pharo-dev] fixing our tools

by Marcus Denker

Hi, Yes, I think we really need to unify both the editor (get really rid of the old one) and the toolsâ¦ e.g. it is strange that all the changes we did for breakpoint visuals now have to be redone 3 times to get them in all toolsâ¦ I will have a look at these, many seem to be related to the suggestions-menu. > On 03 Dec 2015, at 08:47, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > please take a look at this errors: > > (I don't want to open 20 bug entries, and I think those issues are related > to two changes for Suggestions menu and one problem on rubric (the current menu builder > does not work for all tools where rubric is used) > So, maybe there are only 2 or 3 "real" issues. > > Help appreciate, especially for the rubric issue. Every time I tried to fix one > tool, there is at least one other tool with a broken menu. > > Open Nautilus on a method: > (Morph>>#drawOn:) browse > without any other interaction, right click on the code pane > -> a menu appears with embedded "why you see this menu/debug" debug menu > caused by empty selection interval > as soon as you select once one method entry, the right click menu works again. > > Open VersionBrowser (or any other tool (MC-changes / merge) with diff morph > right click in one of the diff code panes > -> error contextFor: 'Not defined context for a RubEditingArea' > > Open Transcript > right click > -> error contextFor: 'Not defined context for a RubEditingArea' > > Open Finder > right click in the lower code pane > -> 'Not defined context for a RubEditingArea' > > Open ProcessBrowser > right click in the lower code pane > -> 'Not defined context for a RubEditingArea(808452096)' > > Open TimeProfiler > select an entry from the time-"tree" > right click in the code pane > deprecation warning -> The method SmalltalkEditor class>>smalltalkEditorMenuOn: has been deprecated. > > Open a basic inspector (EyeInspector) > right click in the workspace pane > -> EyeIntegerInspector(Object)>>doesNotUnderstand: #selectedMessage > > Open ChangesBrowser > right click in the lower code pane (regardless whether you select a changed class and method > or not you'll get always) > -> ChangeSorterApplication(Object)>>doesNotUnderstand: #selectedMessage > > Open CriticsBrowser > right click on the code pane > -> SingleCodeCriticResultList(Object)>>doesNotUnderstand: #selectedMessage > > Open recover lost changes > right click on the lower code pane > -> ExternalChangesBrowser(Object)>>doesNotUnderstand: #selectedMessage > > The same in external browser > ExternalBrowser(Object)>>doesNotUnderstand: #selectedMessage > > Open debugger > select a inst var or context var > right click in the var "value"-pane > -> MorphicTextAdapter(Object)>>doesNotUnderstand: #acceptAllowed > > Open VersoinBrowser > change from "Side-by-Side" to "Source" view > right click in the code pane > -> UndefinedObject(Object)>>doesNotUnderstand: #ast >

Dec. 3, 2015

fixing our tools

by Nicolai Hess

please take a look at this errors: (I don't want to open 20 bug entries, and I think those issues are related to two changes for Suggestions menu and one problem on rubric (the current menu builder does not work for all tools where rubric is used) So, maybe there are only 2 or 3 "real" issues. Help appreciate, especially for the rubric issue. Every time I tried to fix one tool, there is at least one other tool with a broken menu. Open Nautilus on a method: (Morph>>#drawOn:) browse without any other interaction, right click on the code pane -> a menu appears with embedded "why you see this menu/debug" debug menu caused by empty selection interval as soon as you select once one method entry, the right click menu works again. Open VersionBrowser (or any other tool (MC-changes / merge) with diff morph right click in one of the diff code panes -> error contextFor: 'Not defined context for a RubEditingArea' Open Transcript right click -> error contextFor: 'Not defined context for a RubEditingArea' Open Finder right click in the lower code pane -> 'Not defined context for a RubEditingArea' Open ProcessBrowser right click in the lower code pane -> 'Not defined context for a RubEditingArea(808452096)' Open TimeProfiler select an entry from the time-"tree" right click in the code pane deprecation warning -> The method SmalltalkEditor class>>smalltalkEditorMenuOn: has been deprecated. Open a basic inspector (EyeInspector) right click in the workspace pane -> EyeIntegerInspector(Object)>>doesNotUnderstand: #selectedMessage Open ChangesBrowser right click in the lower code pane (regardless whether you select a changed class and method or not you'll get always) -> ChangeSorterApplication(Object)>>doesNotUnderstand: #selectedMessage Open CriticsBrowser right click on the code pane -> SingleCodeCriticResultList(Object)>>doesNotUnderstand: #selectedMessage Open recover lost changes right click on the lower code pane -> ExternalChangesBrowser(Object)>>doesNotUnderstand: #selectedMessage The same in external browser ExternalBrowser(Object)>>doesNotUnderstand: #selectedMessage Open debugger select a inst var or context var right click in the var "value"-pane -> MorphicTextAdapter(Object)>>doesNotUnderstand: #acceptAllowed Open VersoinBrowser change from "Side-by-Side" to "Source" view right click in the code pane -> UndefinedObject(Object)>>doesNotUnderstand: #ast

Dec. 3, 2015

Re: [Pharo-dev] Help needed: old issues issue tracker entries

by Nicolai Hess

Am 03.12.2015 1:08 vorm. schrieb "EuanM" <euanmee(a)gmail.com>: > > I had an issue assigned against me, which I have not the time nor the > knowledge to fix. > > (Inconstant aspect ratio of Desktop background image). > > Can I suggest it is given to someone who knows the Desktop GUI codebase? > > (If I was in a position to fix it, I would have just submitted a fix, > not a bug report) It was assigned to "everyone". And just assigned to you after a fix was provided. That issue is already closed. > > On 2 December 2015 at 13:42, webwarrior <reg(a)webwarrior.ws> wrote: > > Case 16725 - Merge changes from spec github repository. > > 2 subcases are resolved, 2 other need decision. Nothing time-consuming - > > just decide if we integrate them or mark as wontfix. > > > > > > Case 15927 - Menu is broken when contained in a list. > > This is much more complicated, it's even not clear which class > > (TransfromMorph or MenuItemMorph) is bugged. > > I tried to fix it myself, but had no success. > > > > > > > > -- > > View this message in context: http://forum.world.st/Help-needed-old-issues-issue-tracker-entries-tp486426… > > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > > >

Dec. 3, 2015

Re: [Pharo-dev] Help needed: old issues issue tracker entries

by EuanM

I had an issue assigned against me, which I have not the time nor the knowledge to fix. (Inconstant aspect ratio of Desktop background image). Can I suggest it is given to someone who knows the Desktop GUI codebase? (If I was in a position to fix it, I would have just submitted a fix, not a bug report) On 2 December 2015 at 13:42, webwarrior <reg(a)webwarrior.ws> wrote: > Case 16725 - Merge changes from spec github repository. > 2 subcases are resolved, 2 other need decision. Nothing time-consuming - > just decide if we integrate them or mark as wontfix. > > > Case 15927 - Menu is broken when contained in a list. > This is much more complicated, it's even not clear which class > (TransfromMorph or MenuItemMorph) is bugged. > I tried to fix it myself, but had no success. > > > > -- > View this message in context: http://forum.world.st/Help-needed-old-issues-issue-tracker-entries-tp486426… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Dec. 3, 2015

Re: [Pharo-dev] Digest from slack to the mailing list?

by EuanM

I grabbed the message history manually today. The elapsed time was 2 hours! You need administrator privileges to use the API even to download the message history in a more direct way. Could someone please add me as a Slack administrator, and I will curate the message history (along with any other willing volunteers) on an ongoing basis until we have automated the history-grab and Slack has implemented threading. We also need a server on which to store the raw and the curated histories. One option would be to add new Pharo mailing lists: ones which accepted a history log per day. This would automatically give us the same replication-to-web that the emails receive. This in turn provides us with good web searchability courtesy of Google, etc. Manually handling the backlog will be time-consuming, so if someone could assist me in automating the process, that would be lovely. For any community members not yet ready to contribute code, but who have time available, this is an ideal role to gain experience of the community, to help the community, and to discover what's going on in the core development team on a day-to-day basis. On 2 December 2015 at 15:28, GastÃ³n Dall' Oglio <gaston.dalloglio(a)gmail.com> wrote: > You are welcome. > > Or you can use the API directly, but I do not know if it is paid or if you > are limited to 10k latest messages > https://api.slack.com/methods/channels.history > > Regards > > 2015-12-02 11:14 GMT-03:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: >> >> Thanks Gaston >> >> I created the Pharo Slack's bot for it, but I'm getting a connection >> refused error when trying to set up the SlackDigest.com integration. >> I'll try later. >> >> Regards! >> >> >> Esteban A. Maringolo >> >> >> 2015-12-02 11:05 GMT-03:00 GastÃ³n Dall' Oglio >> <gaston.dalloglio(a)gmail.com>: >> > Hello. >> > >> > Just a thought ... There's a automated tool for do that (I have not >> > tried >> > yet) >> > http://slackdigest.com/digest.html >> > >> > It send a DM to interested users, but maybe using Outgoing WebHooks the >> > DM >> > can be forwarded to some service to publish it. >> > >> > >> > >> > 2015-11-30 17:47 GMT-03:00 philippe.back(a)highoctane.be >> > <philippe.back(a)gmail.com>: >> >> >> >> And I've not been looking at Slack that much. >> >> >> >> Digest would be we nice indeed. >> >> >> >> Phil >> >> >> >> On Nov 30, 2015 4:53 AM, "EuanM" <euanmee(a)gmail.com> wrote: >> >>> >> >>> And of course, we can stop doing it manually once threading arrives. >> >>> >> >>> On 30 November 2015 at 03:52, EuanM <euanmee(a)gmail.com> wrote: >> >>> > I have been talking to the Slack dev team and they assure me that >> >>> > threading is on its way - as a priority. >> >>> > >> >>> > I am happy to manually curate threads if someone gets a 24hour dump >> >>> > to >> >>> > log files working. >> >>> > >> >>> > The best way to do this would be to have teams of curators per >> >>> > channel, each doing a little curation periodically on a rota per >> >>> > channel basis. >> >>> > >> >>> > This is an ideal task for people still getting up to speed with >> >>> > Pharo >> >>> > internals. It is a great way to be exposed to stuff you don't >> >>> > understand, and put your mind around it. >> >>> > >> >>> > This provide a starter slope for future contributors. >> >>> > >> >>> > On 23 November 2015 at 08:14, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> >> >>> > wrote: >> >>> >> The problem is, that it is not that easy to create a âdigestâ from >> >>> >> Slack, as there is no kind of grouping. Either you have to detect >> >>> >> similar >> >>> >> words in discussion, or you have to simply export everything. I >> >>> >> donât know >> >>> >> whether it makes sense to just compose a huge email of all >> >>> >> discussions, but >> >>> >> we can try to do that. >> >>> >> >> >>> >> Cheers. >> >>> >> Uko >> >>> >> >> >>> >>> On 23 Nov 2015, at 00:21, EuanM <euanmee(a)gmail.com> wrote: >> >>> >>> >> >>> >>> I agree - if we can have each 24 hours of chat archived to >> >>> >>> somewhere >> >>> >>> that provides a free-text search, that would be very good. >> >>> >>> >> >>> >>> Up until now, I've been grabbing, editting and posting chats I >> >>> >>> find >> >>> >>> of >> >>> >>> interest and importance to me. And it seems to lend itself to >> >>> >>> design >> >>> >>> discussions. What it's not very good at, atm, is discussion >> >>> >>> threading. It would be great to be able to set your typing as >> >>> >>> belonging to a thread., so that when it get sucked out and >> >>> >>> archived >> >>> >>> that the threads were segregated. >> >>> >>> >> >>> >>> Does someone have a server that could receive a text dump of all >> >>> >>> recent Slack messages every 12 (or 24, or 6) hours, and then make >> >>> >>> it >> >>> >>> available for indexing by Google et al, and querying (via the >> >>> >>> search >> >>> >>> engines) by our dev base? >> >>> >>> >> >>> >>> >> >>> >>> >> >>> >>> >> >>> >>> >> >>> >>> On 22 November 2015 at 13:57, Dimitris Chloupis >> >>> >>> <kilon.alios(a)gmail.com> wrote: >> >>> >>>> Just to clear something up , because I see people in slack saying >> >>> >>>> goodbye, >> >>> >>>> or "I cant reply right now I have something to do" . Slack is not >> >>> >>>> just a >> >>> >>>> real time chat, it keeps messages inside a history of 10 thousand >> >>> >>>> messages. >> >>> >>>> So that means you can log in Slack at any time and not lose a >> >>> >>>> message. There >> >>> >>>> is no reason for you to be online all time, no reason to say >> >>> >>>> goodbye, >> >>> >>>> goodmorning , goodafternoon. You can come and go as you please >> >>> >>>> the >> >>> >>>> exact >> >>> >>>> same way as the mailing list. >> >>> >>>> >> >>> >>>> The problem arises when we exceed 10k messages, the old ones get >> >>> >>>> lost and I >> >>> >>>> think having a place to store them is a good idea. >> >>> >>>> >> >>> >>>> Also what is important is in the eye of the beholder, for example >> >>> >>>> I >> >>> >>>> dont >> >>> >>>> care about any discussion about web development , its just does >> >>> >>>> not >> >>> >>>> interest >> >>> >>>> me or database coding or many other things. I have learned to >> >>> >>>> filter >> >>> >>>> out the >> >>> >>>> messages I dont care about in the mailing list and just reject >> >>> >>>> them. >> >>> >>>> Slack >> >>> >>>> is same story, I quickly glance through its history and I can >> >>> >>>> search >> >>> >>>> the >> >>> >>>> messages that interest me using the search bar , I can star >> >>> >>>> messages >> >>> >>>> that I >> >>> >>>> want to keep, and I can comment on existing messages / code >> >>> >>>> snippets >> >>> >>>> which >> >>> >>>> create a thread about that message. >> >>> >>>> >> >>> >>>> In the end its impossible to keep the community in one place but >> >>> >>>> to >> >>> >>>> have a >> >>> >>>> central hub that collects all the little gems can be quite >> >>> >>>> useful. >> >>> >>>> >> >>> >>>> On Sun, Nov 22, 2015 at 3:46 PM stepharo <stepharo(a)free.fr> >> >>> >>>> wrote: >> >>> >>>>> >> >>> >>>>> Yes this would be good. >> >>> >>>>> People should understand that important discussions should be >> >>> >>>>> via >> >>> >>>>> the >> >>> >>>>> mailing-list. >> >>> >>>>> Emails are good because you can consume them the way you want. >> >>> >>>>> I simply cannot be connected all the time. So emails are good >> >>> >>>>> because I >> >>> >>>>> can process them >> >>> >>>>> when I decide. >> >>> >>>>> Slack is good for more interactive session around debugger and >> >>> >>>>> things >> >>> >>>>> like that. >> >>> >>>>> >> >>> >>>>> Stef >> >>> >>>>> >> >>> >>>>> >> >>> >>>>> Le 21/11/15 18:05, Stephan Eggermont a Ã©crit : >> >>> >>>>>> Should we have a digest from slack to a mailing list? >> >>> >>>>>> We are already losing messages >> >>> >>>>>> >> >>> >>>>>> Stephan >> >>> >>>>>> >> >>> >>>>>> >> >>> >>>>>> >> >>> >>>>> >> >>> >>>>> >> >>> >>>> >> >>> >>> >> >>> >> >> >>> >> >> >>> >> > >> >

Dec. 3, 2015

PhD in Chile

by Alexandre Bergel

Hi! We have national grant to do a PhD in Chile. Here are some information: http://www.conicyt.cl/becas-conicyt/2015/10/becas-doctorado-nacional-2016/ Deadline is approaching very soon. Let me know (privately) if you are interested. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 2, 2015

Re: [Pharo-dev] Is it possible to use GTDebugger with DarkTheme?

by Mariano Martinez Peck

Hi Andrei, Thanks, it worked. Now, let me ask something else. I do like the #enableStackColoring: feature. And so if that would work with DarkTheme that would be nice. It seems the colors are hardcoded in #textAttributesForStackEntry: right? So if we would want that to be Theme dependent we would have to move that into Theme settings? Just as a temporal fix I made an override of that method with colors that would work more or less with DarkTheme. Thanks! On Wed, Dec 2, 2015 at 1:44 PM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > > On Wed, Dec 2, 2015 at 5:34 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> >> >> On Wed, Dec 2, 2015 at 1:17 PM, Andrei Chis <chisvasileandrei(a)gmail.com> >> wrote: >> >>> >>> >>> On Wed, Dec 2, 2015 at 5:02 PM, Mariano Martinez Peck < >>> marianopeck(a)gmail.com> wrote: >>> >>>> That's super cool! But I have a couple of questions: >>>> >>>> 1) How can I load (exactly) latest working GT (including GT Debugger) >>>> for a fresh Pharo 4.0? >>>> >>> >>> I tried loading the latest version of all GTools in Pharo 4 and the >>> image hangs. >>> Luckily if you want you can only load GTDebugger and that should work. >>> >> >> I guess the very last version, correct? >> > > Yes, the latest version. > > >> >> >>> >>> >>>> I need to include this DarkTheme fix and ideally your latest changes to >>>> the test runner debugger to see the diff :) >>>> Of course, I could use #bleedingEdge but I wonder if at some point that >>>> breaks because you assume XXX version work only in Pharo 5.0. >>>> >>> >>> I can make a version of GTDebugger+SUnit extensions that works in pharo >>> 4. Just that version would not get updated any more. >>> >>> >> >> That would be awesome :) >> >> >>> >>>> 2) Is there a way I can set the GTDebugger as the default debugger and >>>> avoid having to click on "Debug Glamorously" ? >>>> >>> >>> GTGenericStackDebugger register. >>> >>> >> >> Thanks. >> >> >>> >>>> Sorry to bother in using 4.0 but sometimes when you work in a team, not >>>> everybody have the time to move to the bleeding edge of Pharo. I try to >>>> keep my client team all working with latest stable release (4.0 in this >>>> case). >>>> >>> >>> No problem. I just hope we can get it to work easily as things changed >>> quite a bit. >>> >>> >> I know. So if at least I am able to use GTDebugger + SUnitExtentions in >> 4.0 that's enough for me for the moment :) >> I have no problem loading specific package versions, no problem on >> loading slices if needed, etc. >> I just need to know what to load hahaha >> >> Cheers, >>> Andrei >>> >>> >>>> >>>> Thanks in advance, >>>> >>>> >>>> >>>> On Wed, Dec 2, 2015 at 12:54 PM, Andrei Chis < >>>> chisvasileandrei(a)gmail.com> wrote: >>>> >>>>> I fixed it. The latest version should work. >>>>> >>>>> Cheers, >>>>> Andrei >>>>> >>>>> On Wed, Dec 2, 2015 at 4:41 PM, Mariano Martinez Peck < >>>>> marianopeck(a)gmail.com> wrote: >>>>> >>>>>> Hi guys, >>>>>> >>>>>> I am trying to use GTDebugger in Pharo 4.0 but I find it complicated >>>>>> using it with DarkTheme set. It looks like if GTDebugger would not take >>>>>> into account some theme settings? I tried in 4.0 and 5.0. >>>>>> Look at the attached screenshot. The complicated part is the left >>>>>> pane, where the stack is. As you can see, the font is too dark for such a >>>>>> dark background. >>>>>> >>>>>> Also..should GTDebugger work in Pharo 4.0? If true, which version? >>>>>> >>>>>> Any idea? >>>>>> >>>>>> -- >>>>>> Mariano >>>>>> http://marianopeck.wordpress.com >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Mariano >>>> http://marianopeck.wordpress.com >>>> >>> >>> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > -- Mariano http://marianopeck.wordpress.com

Dec. 2, 2015