Magma April 2011

magma@lists.squeakfoundation.org

11 participants
15 discussions

Re: [Pharo-project] Networking change in Pharo 1.2?
by Chris Muller 18 Apr '11

18 Apr '11

> The only change to NetNameResolver was this: > > http://code.google.com/p/pharo/issues/detail?id=1853 Reverting this change fixed it.

1 0

Networking change in Pharo 1.2?
by Chris Muller 17 Apr '11

17 Apr '11

I was able to work on getting Magma 1.2 going in Pharo. It was quite easy to get the code loaded and functioning in Pharo 1.1.1, Pharo 1.2, and Pharo 1.3. But something seems to have changed in Pharo's networking from 1.1.1 to 1.2. All Magma functionality seems to work fine for low-volume activity. However, when the test-suite gets to the HA test cases (at the end), one of the images performing heavy networking activity, consistently gets very slow and bogged down for some reason; causing the clients to timeout and disrupting the test suite. Fortunately, it happens in the same place in the test-suite every time. The UI of the image in question becomes VERY sluggish, but MessageTally spyAllOn: didn't reveal anything useful. What is it doing? I did verify that the Magma server in that image is still functioning; clients were committing, but I had to increase their timeouts from 10 to 45 seconds to avoid timeouts.. Unfortunately, two days of wrangling in Pharo (because I'm an old Squeak dog) I could not nail the problem down; but I have one suspect.. A couple of times, I caught a process seemingly hung up in NetworkNameResolver; trying to resolve an IP from 'localhost'. This exact set of Magma packages is rock-solid on Pharo 1.1.1 and Squeak, but that doesn't mean the problem for sure lies in Pharo 1.2; maybe a networking bug in 1.1.1 is allowing Magma to "misuse" the network and get away with it and Pharo 1.2 is now more strict? I don't know, I would just like to ask the experts here for help who know all what went into Pharo 1.2 so hopefully we can get to the bottom of it. Thanks, Chris

2 1

Status of Magma on Pharo 1.2
by Miguel Cobá 17 Apr '11

17 Apr '11

Hi all, a lot of messages have been sent asking about the status of Magma on Pharo and in particular on Pharo 1.2. Here is it. Magma latest version (1.2) isn't working on Pharo 1.2. This is due to some changes that Pharo 1.2 have and some changes that Magma 1.2 uses that only were on Squeak 4.2. As they are very difficult to integrate now that Pharo 1.2 is out, they are targetted to Pharo 1.3. So, Magma 1.2 (or greater) will only be available to Pharo 1.3. Now, what if I want to use Magma in Pharo 1.2 right now. Well, your only option is Magma 1.1r1. Is that bad, I don't think so, as the new releases of magma are mostly about performance and not about new functionality. So for a OO database, 1.1r1 is as good as 1.2. So mind not about it. Now, to load it, evaluate in a workspace: Deprecation raiseWarning: false. Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfMagma'; load. ((Smalltalk at: #ConfigurationOfMagma) project version: #stable) load: 'Tester'. Currenty 1.1r1 is the stable version for Pharo 1.2.x. Then create a directory for the repo (magma in this case) and evaluate: MagmaRepositoryController create: 'magma/' root: Dictionary new. Start the magma server MagmaServerConsole new open: 'magma/'; processOn: 51969; inspect. Connect to magma (MagmaSession host: 'localhost' port: 51969) connectAs: 'miguel'; inspect. In the window opened by the last doit (the connection window) evaluate: self root inspect and then self root at #miguel put: OrderedCollection new and then again: self root inspect. add some value: (self root at: #miguel) add: 'Hello world' read that value (print it) (self root at: #miguel) first "-> 'Hello world' Chris Muller is kindly working on the issues found in order to make latest Magma working in Pharo. When he publishes a new version I will update the ConfiguratioOfMagma, pointing #stable to the new version. Until then, 1.1r1 should work. Cheers -- Miguel Cobá http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

1 0

Magma support (was: Magma/Pharo)
by Chris Muller 14 Apr '11

14 Apr '11

The packages on Magma squeaksource are less than a month old, and I've been gone for 13 days out the last 30..!! These are the latest-and-greatest version of Magma that Pharo users should be using. Plus you also pointed out the two verbal updates I put out on the list about an official 1.2 release. So I'm not sure what you mean by "quiet"? Nor am I sure why you would need me to tell you what's broken about Magma in Pharo, especially when you acknowledged I don't use Pharo, but you do and had a problem with the Metacello config. If you think it will help, ok, "Someone from Pharo fix that," there you are. Someone else asked if I could update the wiki to clarify something. Let me just say, to those who are interested in Magma, I invite you to integrate yourself into Magma development; fix the Metacello, update the wiki, post helpful messages on the Magma mailing list instead of just questions, etc. I feel that I've demonstrated my mode of support, over years, to those who engage me with Magma questions. If you need more output, you've got to give more input (or money). If things are too "quiet" for you, please subscribe to the Magma project so you will be notified when new packages arrive. Check the MC history, there were 11 versions of the "Magma client" package in March, 2011, alone. - Chris On Thu, Apr 14, 2011 at 12:45 AM, Daniel Lyons <fusion(a)storytotell.org> wrote: > > On Apr 12, 2011, at 10:34 AM, Chris Muller wrote: > >> Magma is not yet supported on Pharo 1.2, but it is part of my plans to >> do so. In fact, I plan to look into it this month. > > http://lists.squeakfoundation.org/pipermail/magma/2011-March/001747.html > http://lists.squeakfoundation.org/pipermail/magma/2011-February/001718.html > >> Please note that I expect Pharo to eventually produce resources >> (developers or money) to assist with Magma support and upgrades as >> Pharo becomes more and more divergent from Squeak in the future. > > > I appreciate that you're busy and I can understand not wanting to maintain a port of your software to a platform you don't use, but as long as Magma development remains this quiet, what good will it do for Pharo to provide developers? If it were "hey, this piece is broken under Pharo, please someone from Pharo take a look at it," it would be a lot easier I think for people to get involved and help shoulder some of the burden. It is (or should be) much easier to get help when you ask for it than when you wish for it silently, looking into the void. > > I'm not an expert at Smalltalk or Pharo and *far* from being one in Magma, but I *am* a real programmer and I know how to fix bugs. Step one is knowing what they are. > > — > Daniel Lyons > >

2 1

Serialization sizeWarningThreshold reached
by Facundo Vozzi 04 Apr '11

04 Apr '11

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Magma April 2011