Magma April 2011

magma@lists.squeakfoundation.org

11 participants
15 discussions

Difficulties setting up Magma Monticello Repository
by Markus Fritsche 30 Apr '11

30 Apr '11

Hello, I tried to set up a remote repository on a networked machine. When I define a repository (local or remote) I get a DNU for Dictionary>>#indexOf: coming from MCRepositoryInspector>>#versionSelection versions is a Dictionary, in the other Repository, it's a nested Array. I use Pharo1.3a Latest update: #13177 (but I also tried it with Squeak 4.2) and the 1.2alpha1.mcm from the MagmaTester repository. Regards, Markus

2 3

Fwd: Persisting IdentityDictionary
by Elliot Finley 28 Apr '11

28 Apr '11

Oops, forgot to reply-all to get it to the list. Here it is. On Tue, Apr 26, 2011 at 8:39 PM, Chris Muller <ma.chris.m(a)gmail.com> wrote: >> You're using 'self keyHash: key' to find a specific bucket that should >> contain that object. But 'self keyHash: key' may (and probably will) >> answer a different number for the same object each time it is >> materialized from the database unless it is somehow using the MagmaOID >> in place of the identityHash. > > Right, you definitely cannot use Squeak's #identityHash in the equation. > > Hm, let me about this a few days, I think an easy solution will appear.. maybe: use magmaOid as keyHash. when finding a key (#at), check if key has magmaOid first, if not, 'self errorKeyNotFound: key' because it doesn't exist in IdentityDictionary anyway. when storing a value (#at: put:); before finding its bucket, check if key has magmaOid, if not, store key in database so it will have a magmaOid. I'm not sure what the code looks like on this last one, but it sounds good :)

2 2

Re: [Pharo-project] ConfigurationOfMagma with support for Magma 1.2 and symbolic versions
by Miguel Cobá 27 Apr '11

27 Apr '11

Yes is in the to-do list. Some weeks ago Mariano created an account on the book site for me in order to update the relevant sections but only until now the configuration is working. I will update it ASAP. Cheers El mié, 27-04-2011 a las 22:13 +0200, Stéphane Ducasse escribió: > cool > miguel may be we should publish this information on the collabactive book. > > stef > > On Apr 27, 2011, at 6:35 PM, Miguel Cobá wrote: > > > Hi all, > > > > I'm glad to announce a new version of ConfigurationOfMagma with support > > for Magma 1.2. This configuration has been tested on > > > > PharoCore 1.1.x > > PharoCore 1.2.x > > > > Thank you very much to Chris Muller who, as always, is working hard to > > keep Magma running on Squeak and Pharo. I used the same versions of > > packages he used in his scripts for Squeak in order to update the > > configuration. > > > > You must download the latest PharoCore image or update a existing one > > before installing Magma, as Magma needs some changes that were applied > > to Pharo post-release and are available in the update stream. > > > > > > Pharo 1.1.x > > ------------ > > > > Download PharoCore 1.1.2 from: > > > > https://gforge.inria.fr/frs/download.php/28341/PharoCore-1.1.2.zip > > > > Update it if necessary and save it. > > > > > > Pharo 1.2.x > > ------------ > > > > You have two options: > > > > 1. Take a released 1.2.1 from: > > > > http://www.pharo-project.org/pharo-download/stable-core > > > > This is actually image update 12345. Evaluate: > > > > SystemVersion newVersion: 'Pharo1.2.2a'. > > > > update the image (it will update to 12350, at this time) and save it. > > > > 2. Take a snapshot of the upcoming 1.2.2 release of Pharo 1.2.x line > > from: > > > > https://gforge.inria.fr/frs/download.php/28436/PharoCore-1.2.2a-12345.zip > > > > update the image (it will update to 12350, at this time) and save it. > > > > > > Install Magma > > -------------- > > > > Ok, now you have an updated image. Load the configuration by evaluating: > > > > Gofer new > > squeaksource: 'MetacelloRepository'; > > package: 'ConfigurationOfMagma'; > > load. > > > > And depending on which of client, server or the full suite of Magma do > > you want, evaluate: > > > > - Magma client > > > > ((Smalltalk at: #ConfigurationOfMagma) > > project version: #stable) load: 'Client'. > > > > > > - Magma server > > > > ((Smalltalk at: #ConfigurationOfMagma) > > project version: #stable) load: 'Server'. > > > > - Magma tester > > > > ((Smalltalk at: #ConfigurationOfMagma) > > project version: #stable) load: 'Tester'. > > > > For example, to load the full magma suite evaluate: > > > > Gofer new > > squeaksource: 'MetacelloRepository'; > > package: 'ConfigurationOfMagma'; > > load. > > ((Smalltalk at: #ConfigurationOfMagma) > > project version: #stable) load: 'Tester'. > > > > This will load client, server and test of Magma. > > > > > > Running tests > > ------------- > > To run the tests evaluate: > > > > MagmaTestCase allowWriteBarrier: false. > > MagmaTestCase fullSuite maDebug. > > > > > > Stable versions > > --------------- > > > > This release of ConfigurationOfMagma includes support for Metacello's > > symbolic versions. Currently the #stable version of Magma is configured > > like this: > > > > Pharo version #stable version > > ------------- --------------- > > Pharo 1.1.x 1.2 > > Pharo 1.2.x 1.2 > > Pharo 1.3.x 1.2 > > > > That is, Magma 1.2 is the #stable version for Pharo 1.1, Pharo 1.2 and > > Pharo 1.3. > > > > Known issues > > -------------- > > > > Magma 1.2 loads correctly and appears to work for the basic things > > (create a repo, add data, commit, etc) in PharoCore 1.3 and Pharo 1.3, > > but the full suite hasn't ran correctly in the current unstable Pharo. > > So use Magma 1.2 on Pharo 1.3 on your own risk and not for production > > yet. When the issues (including the Transcript revert that should happen > > in Pharo soon) are addressed, a new announce will be made for Magma on > > Pharo 1.3 > > > > Any feedback welcome. > > > > Enjoy. > > -- > > Miguel Cobá > > http://twitter.com/MiguelCobaMtz > > http://miguel.leugim.com.mx > > > > > > > > > > > > > > -- Miguel Cobá http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

1 0

ConfigurationOfMagma with support for Magma 1.2 and symbolic versions
by Miguel Cobá 27 Apr '11

27 Apr '11

Hi all, I'm glad to announce a new version of ConfigurationOfMagma with support for Magma 1.2. This configuration has been tested on PharoCore 1.1.x PharoCore 1.2.x Thank you very much to Chris Muller who, as always, is working hard to keep Magma running on Squeak and Pharo. I used the same versions of packages he used in his scripts for Squeak in order to update the configuration. You must download the latest PharoCore image or update a existing one before installing Magma, as Magma needs some changes that were applied to Pharo post-release and are available in the update stream. Pharo 1.1.x ------------ Download PharoCore 1.1.2 from: https://gforge.inria.fr/frs/download.php/28341/PharoCore-1.1.2.zip Update it if necessary and save it. Pharo 1.2.x ------------ You have two options: 1. Take a released 1.2.1 from: http://www.pharo-project.org/pharo-download/stable-core This is actually image update 12345. Evaluate: SystemVersion newVersion: 'Pharo1.2.2a'. update the image (it will update to 12350, at this time) and save it. 2. Take a snapshot of the upcoming 1.2.2 release of Pharo 1.2.x line from: https://gforge.inria.fr/frs/download.php/28436/PharoCore-1.2.2a-12345.zip update the image (it will update to 12350, at this time) and save it. Install Magma -------------- Ok, now you have an updated image. Load the configuration by evaluating: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfMagma'; load. And depending on which of client, server or the full suite of Magma do you want, evaluate: - Magma client ((Smalltalk at: #ConfigurationOfMagma) project version: #stable) load: 'Client'. - Magma server ((Smalltalk at: #ConfigurationOfMagma) project version: #stable) load: 'Server'. - Magma tester ((Smalltalk at: #ConfigurationOfMagma) project version: #stable) load: 'Tester'. For example, to load the full magma suite evaluate: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfMagma'; load. ((Smalltalk at: #ConfigurationOfMagma) project version: #stable) load: 'Tester'. This will load client, server and test of Magma. Running tests ------------- To run the tests evaluate: MagmaTestCase allowWriteBarrier: false. MagmaTestCase fullSuite maDebug. Stable versions --------------- This release of ConfigurationOfMagma includes support for Metacello's symbolic versions. Currently the #stable version of Magma is configured like this: Pharo version #stable version ------------- --------------- Pharo 1.1.x 1.2 Pharo 1.2.x 1.2 Pharo 1.3.x 1.2 That is, Magma 1.2 is the #stable version for Pharo 1.1, Pharo 1.2 and Pharo 1.3. Known issues -------------- Magma 1.2 loads correctly and appears to work for the basic things (create a repo, add data, commit, etc) in PharoCore 1.3 and Pharo 1.3, but the full suite hasn't ran correctly in the current unstable Pharo. So use Magma 1.2 on Pharo 1.3 on your own risk and not for production yet. When the issues (including the Transcript revert that should happen in Pharo soon) are addressed, a new announce will be made for Magma on Pharo 1.3 Any feedback welcome. Enjoy. -- Miguel Cobá http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

1 0

Persisting IdentityDictionary
by Elliot Finley 27 Apr '11

27 Apr '11

Chris or whoever may be able to answer, I'm in the process of evaluating Aida/Web. Part of the evaluation is obviously the different persistence strategies. Its default strategy is to use the image and just take a snapshot every hour. That works for some people but I really don't feel comfortable with that strategy for many reasons I won't go into. I would really like to use Magma to persist my object graph. At first glance it looks simple, just use Magma like normal and persist the graph. But upon closer inspection, it turns out that one of the features that makes Aida/Web so appealing and so easy to use also makes it difficult (I think, I hope I'm wrong) to persist with anything other than the image or Gemstone. Aida/Web keeps two dictionaries: URL -> Object (Dictionary) Object -> URL (IdentityDictionary) If these aren't persisted in an external database, then they'll keep a reference to every object used in the web application in your image, thus negating the benefits of using an external database in the first place. The Dictionary is easy. The IdentityDictionary is using the Object's identityHash as the key and I don't see any easy way to make that work. So the question boils down to - Is there a way to persist an IdentityHash with Magma? If not, are there any workarounds that you can think of? Any help would be appreciated. Thanks, Elliot

3 7

Magma/Pharo
by Elliot Finley 26 Apr '11

26 Apr '11

Is newest Magma working with Pharo 1.2.1? How would I load? TIA Elliot

5 15

[ANN] Magma 1.2
by Chris Muller 20 Apr '11

20 Apr '11

Magma 1.2 is now finally released for Squeak 4.2, Pharo 1.1 and Pharo 1.2. This new release offers improved performance thanks to minimizing the problem associated with finalization, as well as avoiding Squeak's slow become except once every 30 seconds. See http://wiki.squeak.org/squeak/6163 for release-notes details. I just went through all of the wiki pages and fixed / updated several of them, including new, clean, one-click installation scripts for for Pharo: http://wiki.squeak.org/squeak/2657 Squeak users may install with one-click directly from the SqueakMap Catalog user-interface. I hope Pharo will consider bringing this back into a future version; SqueakMap already has several projects that load from Metacello. I also realized several of Magma's special capabilities have been undocumented. I've now documented them. http://wiki.squeak.org/squeak/6164 This release is, exactly, one year since Magma 1.1, thank you for your patience. As before, support for Magma is described at: http://wiki.squeak.org/squeak/5818

4 3

conflicting information in 'Magma Supported Classes'
by Elliot Finley 19 Apr '11

19 Apr '11

Here: http://wiki.squeak.org/squeak/5722 It says: I discovered the following are not part of the test cases, yet I fully expect them to work: Any object with both named and indexed instance-variables WriteStream IdentityBag IdentityDictionary IdentitySet then later it says: CAUTION: Unsupported The following kinds of objects are not supported. They've never been tested and I don't expect them to work: Classes with both named and indexed instance-variables. Any subclasses of Set or Dictionary. IdentityDictionary is a subclass of Dictionary and thus it is listed in the 'expected to work' and the 'not expected to work' sections. I don't see how an IdentityDictionary could work, but I'm hoping it does. Anyone care to clarify? Thanks, Elliot

1 1

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

19 Apr '11

Just bench it: Before change: [ NetNameResolver localHostAddress ] bench " '34,000 per second.' " After change: [ NetNameResolver localHostAddress ] bench " '31 per second.' " In just looking at the reason given for making the change, it says this is to satisfy an _exceptional_ case; e.g., the case where "no network connection is available." Then I look at the new code called by #localHostAddress and becomes obvious why: isConnected "Dirty, but avoids fixing the plugin bug" [NetNameResolver addressForName: 'www.esug.org'.] on: NameLookupFailure do: [:ex| ^false]. ^true A hard-coded nslookup to 'www.esug.org' wrapped in an exception-handler? Wow! If this isn't enough, you can run the Magma test-suite to see the effect on a real-world networking application. I recommend Pharo crew revert this change and consider a different approach. - Chris On Tue, Apr 19, 2011 at 2:27 AM, Stéphane Ducasse <stephane.ducasse(a)inria.fr> wrote: > yes > Now do you have a description how we can reproduce your problem because the fix was fixing something. > and it would be good to understand what is the deeper problem. > Stef > > On Apr 19, 2011, at 4:20 AM, Chris Muller wrote: > >> Thank you too; it was a bruising problem I'm glad to have it identified. >> >> On Mon, Apr 18, 2011 at 12:21 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> On Apr 18, 2011, at 7:14 PM, Chris Muller wrote: >>> >>>>> The only change to NetNameResolver was this: >>>>> >>>>> http://code.google.com/p/pharo/issues/detail?id=1853 >>>> >>>> Reverting this change fixed it. >>>> >>> >>> >>> Thanks! I have opend the issue again for 1.2.2 and 1.3 >>> >>> Marcus >>> >>> >>> -- >>> Marcus Denker -- http://www.marcusdenker.de >>> INRIA Lille -- Nord Europe. Team RMoD. >>> >>> >>> >> > > >

1 0

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

19 Apr '11

Thank you too; it was a bruising problem I'm glad to have it identified. On Mon, Apr 18, 2011 at 12:21 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Apr 18, 2011, at 7:14 PM, Chris Muller wrote: > >>> The only change to NetNameResolver was this: >>> >>> http://code.google.com/p/pharo/issues/detail?id=1853 >> >> Reverting this change fixed it. >> > > > Thanks! I have opend the issue again for 1.2.2 and 1.3 > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > >

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Magma April 2011