Magma August 2009

magma@lists.squeakfoundation.org

14 participants
17 discussions

Pharo port
by Stuart Herring 16 Aug '09

16 Aug '09

Hi all, As I mentioned earlier, I've been working on a port to Pharo. It's effectively a branch (not a fork), and can be found in the MagmaPharo SqueakSource project. The current version, which is based on r42Gamma6 can be loaded via the MagmaPharo-42Gamma6-test3.mcm Monicello Configuration Map. It loads cleanly into Beta1 (10401) and 10413, and seems to work for simple uses. However, there's still some issues, and the tests do not pass yet. What I have had to change so far: * Ma base additions: - Copied the extension methods from BlockContext to BlockClosure, which has been previously discussed. * Ma object serialization: - Removed the extension methods for classes no longer existent in Pharo - meaning no more warnings when loading. - Created a new MaBlockClosureStorage class based on MaBlockContextStorage, to handle the different internal representation of a BlockClosure. I'm not entirely sure of my handling of the outerContext instVar though. - copied the extension methods from BlockContext, but modified them to use MaBlockClosureStorage instead of MaBlockContextStorage, and to call asBlockClosure not asBlockContext when materializing. * Ma Armored Code - Replace the use of the missing ScreenController class with Display - Changes to the code to connect to localhost to support Pharo ( #connectTo:port: no longer accepts a ByteArray for the address - so used SocketAddress loopback4 instead) * Ma object serialization tester: - removed the soundSamples method, due to the classes being tested no longer existing. - Copied #maEquivalentForSerializationTest:... from BlockClosure to BlockContext, modifying it to reflect the differences between the classes. * MagmaTester - replace usage of Utilities>>setAuthorInitials with Author>>initials to prevent the tests being paused by deprecation warnings. I'll have to update it again now to use Author>>fullName Author>>initials was also deprecated sometime after 10401. As I said, the tests don't pass yet. There's two immediate issues: 1. A Pharo bug - (issue 966) preventing MethodProperties from being compared which causes the object serialization tests to fail. I've submitted a fix for that, which hopefully will make its way in. 2. Even with the MethodProperties fix, the sampleProcess serialization tests fail. This appears to be because a Process in Pharo has a slightly different representation to one in Squeak - in Squeak, the suspendedContext instVar is a BlockContext, in Pharo it's a MethodContext. After coming out of #maMaterializeFromGraph:, that MethodContext in suspendedContext appears to be incomplete. I haven't been able to figure out why yet, probably because I haven't consumed enough coffee to understand exactly what happens in the serialization/materialization process. In addition, some experimentation shows that some of the collection tests may also fail, but I'll worry about that once the Process stuff is dealt with. Also, I don't think there's a version of NewCompiler that works with Pharo yet, so there's no WriteBarrier support. If anyone with a deeper understanding of either the serialization process, or Processes, BlockClosures and MethodContexts wants to have a look, please do! The general idea of the MagmaPharo repository is that it should only contain changes specifically required to make Magma work on Pharo, general non pharo-specific changes should go to Chris and MagmaTester as usual. Whenever Chris publishes a new .mcm, I'll merge it into the MagmaPharo repository, and then publish a new .mcm for Pharo, once I've verified that all the tests still pass (assuming we've got to the point where the tests do in fact pass). Regards, Stuart

3 4

Trying to launch pharo image..
by Chris Muller 13 Aug '09

13 Aug '09

I decided to see what it is like to load Magma into Pharo. But I couldn't get the image launched: squeak pharo1.0beta-10413web09.08.1.image & results in: $ This interpreter (vers. 6502) cannot read image file (vers. 6504). Press CR to quit... Pressing Enter on the keyboard results in the squeak process still out there, the only way I could rid it was to use kill -9... I'm using the 3.10-4 VM... Any ideas?

3 2

Fwd: The role of magma on the Pharo
by Stuart Herring 13 Aug '09

13 Aug '09

gah, keep forgetting to CC the list. ---------- Forwarded message ---------- From: Stuart Herring <st-lists(a)stuartherring.com> Date: 2009/8/13 Subject: Re: The role of magma on the Pharo To: Miguel Enrique Cobá Martinez <miguel.coba(a)gmail.com> 2009/8/12 Miguel Enrique Cobá Martinez <miguel.coba(a)gmail.com>: > > Well I'm trying to do my part too. I just wanted to start a discussion > not a flame war. I recognise that, and it's a good and useful discussion to be having. My apologies if I came across as flamy. >> You could probably get an idea of the pros and cons of each of those >> approaches by going back through the Seaside and Magma lists, as the >> topics have come up a few times. > Yes, maybe I could, but what about someone that for the first time > arrives to smalltalk and to object databases. They want to know a list > of pros/cons without reading the complete archives of magma, seaside, > pharo and squeak list just for evaluating which alternative to go for. Actually, what I meant here was that someone could do that and then compile the results of that research into a wiki page. I agree that it's not much having to trawl through mailing lists to find basic information like that. Regards, Stuart

1 0

The role of magma on the Pharo
by Miguel Enrique Cobá Martinez 13 Aug '09

13 Aug '09

This is my personal view/opinion. Magma it is an *impressive* piece of software. Magma it has more potential in the web arena than in the desktop arena. Magma hasn't exploited all the potential it has. Magma hasn't been marketed correctly. Magma needs good documentation. Magma needs to show off what it can do. Magma needs to easy the seaside integration. Magma needs a good looking/professional website. Magma should provide alternatives to integration with seaside and the pros/cons of each one. Now, what can we do in order to give Magma a relevant position in the seaside/pharo/smalltalk arena? I could help with several of these points, but Chris, you must lead this effort. It shouldn't appear tho the potential or real contributors (fixes, addons, helpers, whatever) that you only mind of Magma and nothing at all about every else that is not Magma. -- Miguel Cobá http://miguel.leugim.com.mx

3 3

Magma and Magma on Pharo questions
by Miguel Enrique Cobá Martinez 12 Aug '09

12 Aug '09

Hi Chris, I am a little frustrated by the documentation about installing magma. They talk about squeak map, sar, monticello, monticello configuration. I know that this question has been asked *several* times before but, please, one more time: where can we get the latest Magma client Magma server Magma tester for both r41 r42 and for monticello/monticello configuration. Personally I think that the universes, map and friends are very frustrating to cope with. Shouldn't be good, with the inminent r42 release, to create a *brand new* repository location and put there everything that is needed and nothing else (historic versions, versions with other names, etc) and in each page of magma on the wiki put a line pointing to that location. I believe that most users will use the new version and the historic ones shouldn't make noise here. Also, the latest version is the supported one, so it is wise to stay current. Second question. Are there plans to support Magma on Pharo. I know that Pharo has many incompatibilities with squeak, but also, it is cleaner than squeak. Other thing that is happening right now in squeak is the integration of closures that make magma incompatible with the next version of squeak (I think :)) and pharo already has closures integrated. Shouldn't be time to have a new version for this platforms? Thanks for your time answering this.

6 18

Magma + Seaside (+Seaside28Jetsam?)
by Ramiro Diaz Trepat 09 Aug '09

09 Aug '09

Hi,I am trying to get a working image that includes Seaside and Magma. I am using the latest Pharo web as my start point. I have published a couple of Monticellos with the extension migrations from BlockContext to BlockClosure. After this, Magma seems to work fine in Pharo. But, to install the seaside modules, the wiki says that I must first install Seaside28Jetsam Which seems to break Seaside (2.8). This was surprising since the latest version seems to be very recent (7th of July). Any clues on how to get this stack working will be greatly appreciated. Cheers r.

1 0

r42Gamma6
by Chris Muller 04 Aug '09

04 Aug '09

42 is demanding patience, it's as simple as that. Let's see if we can get through a three weeks without any further bug reports and, if so, hopefully *this* will become the final for 42. Here are the specific improvements from gamma5: - HA performance fix. When sending commit-log records to the warm-backups, we are now only correctly sending "trimmed" copies instead of the "private", reused, bloated record, which is as large as the largest-ever encountered CommitRecord since that server was started! - WriteBarrier fixed up and working again. - Removed MagmaLowOnMemory in favor of the new proper hook into the LowSpaceWatcher. - Discovered WeakArray>>#addWeakDependent:. Using it to keep MaWeakKey dictionary sizes in check. This may be less aggressive than the former 30-second timer, but so far memory utilization seems fine. - Sigh. MaRecoveryRecord physicalSize *was* only 3 bytes. The notion that we would never have a commit > 16MB was short-sighted; because it is at least useful for initial transfer of a legacy object model into Magma. So, now we have a new definition for MaRecoveryRecord, that will have 4 bytes for the physicalSize, allowing up to 4GB commits, should be plenty. To upgrade, - Bring system down. - Launch newly built image with this new code. - Restart system. A warning is presented to ensure you want to convert from 11 to 12. - Possible fix for disconnect hanging when Network error is encountered on initial disconnect. - Fix DNU when using #noteOldKeysFor:! - Ensure not to allow a session to add more than 4 million new objects in a single transaction, because that exceeds the number of new-object oids.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Magma August 2009