Magma February 2010

magma@lists.squeakfoundation.org

6 participants
6 discussions

[ANN] Magma 1.0 release 44
by Chris Muller 03 Mar '10

03 Mar '10

I am pleased to announce the immediate availability of Magma 1.0 release "44" for both Squeak, 3.9, 3.10 and Pharo. Although I am looking into alternatives for future releases, for now I am still distributing Magma in my traditional ways: - On SqueakMap - three one-click installable packages. - In the "1.0r44" Monticello Configuration in the "Magma" project of squeaksource, there are three one-click installable configurations (client, server, tester). - The "r44Final" Monticello Configuration in the "MagmaTester" project of squeaksource is the one-click installable MagmaTester package. As has always been the case, ONLY ONE of the three packages needs to be installed, the full and proper configuration is loaded with one-click. Compared to r43, this is mostly a maintenance release without any major new functionality, but with improved robustness in the HA and luxury querying as well as several other fixes. Here are the specific improvements over 43: - Made several HA fixes and improvements, many identified by Bart Gaquie by testing with more than a two-server Magma Node. Many thanks Bart. - Updated MaQueryExecutor>>#fractionComplete to answer an unreduced Fraction instead of a reduced one. This convey's more information; since the denominator represents the total number of elements in the final result. Thanks again to Bart Gauqie. - Upgraded MagmaCollectionReader>>#release to allow give a well-behaved application much freer access to the "luxury" query features of MagmaCollections. It is essential for applications employing luxury query features of Magma for ad-hoc querying, to #release the Reader returned from the query so that resources on the server can be freed. - Now properly truncating the applied.images file, so it doesn't grow and grow.. - Now, when a repository is opened locally, if it's location has never been set (new repository) or was a different *local* location, then update it to the new aMagmaLocalLocation. If it was formerly a network-hosted server, do not update since we could be here simply just for re-opening that repository. So, to go from a remote repository to a local one, you have to manually update the node's primaryLocation. - Server no longer allows any clients to log in with the system name, since it is sometimes checked for special-purpose server housekeeping. - Updated MagmaSession's standard printing method, again! - Added MagmaCollectionReader>>#sortBy:makeDistinct:descending: and #sortBy:makeDistinct:descending:. - Made MaRepositoryDisconnectRequest asynchronous, it now returns considerably faster! - Fix for a recent MagmaCollection optimization. - Removed hard-reference to OSProcess. - Patch for #removeListener to avoid DependentsArray problem. - Fixed a ReadStrategy regression.

3 7

Re: [Pharo-project] [ANN] Magma 1.0 release 44
by Mariano Martinez Peck 24 Feb '10

24 Feb '10

Miguel will be probably able to help you. On Wed, Feb 24, 2010 at 8:09 AM, Stéphane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Thanks we will have a look. > Note that Installer is not available from ScriptLoader (ScriptLoader is not > a public class and nobody should use it) > Either use gofer which is the default loader or install installer manually. > > > Stef > > On Feb 24, 2010, at 5:38 AM, Chris Muller wrote: > > > Hi Ramiro, something happened between Pharo1.0-10502-rc1dev09.12.2. > > and 10508 related to Networking. Please see: > > > > > http://lists.gforge.inria.fr/pipermail/pharo-project/2010-February/021912.h… > > > > I am not sure what happened. Perhaps someone on the Pharo team would > elaborate? > > > > - Chris > > > > > > On Tue, Feb 23, 2010 at 6:54 PM, Ramiro Diaz Trepat > > <ramiro(a)diaztrepat.name> wrote: > >> Hi Chris, > >> Once again, thanks for your work. > >> One question though, is this version running fine on the latest Pharo > 1.0 ? > >> I haven't been able to start a server successfuly, I get a primitive has > >> failed. > >> It doesn't run on Pharo 1.1 or Squeak trunk but you didn't mention those > :) > >> I loaded it in a fresh Pharo 1.0 image using: > >> ScriptLoader new installer. > >> Installer ss project: 'Magma'; > >> install: '1.0r44 (server)'. > >> > >> Cheers > >> > >> r > >> > >> On Wed, Feb 17, 2010 at 8:46 PM, Chris Muller <asqueaker(a)gmail.com> > wrote: > >>> > >>> I am pleased to announce the immediate availability of Magma 1.0 > >>> release "44" for both Squeak, 3.9, 3.10 and Pharo. Although I am > >>> looking into alternatives for future releases, for now I am still > >>> distributing Magma in my traditional ways: > >>> > >>> - On SqueakMap - three one-click installable packages. > >>> > >>> - In the "1.0r44" Monticello Configuration in the "Magma" project of > >>> squeaksource, there are three one-click installable configurations > >>> (client, server, tester). > >>> > >>> - The "r44Final" Monticello Configuration in the "MagmaTester" > >>> project of squeaksource is the one-click installable MagmaTester > >>> package. > >>> > >>> As has always been the case, ONLY ONE of the three packages needs to > >>> be installed, the full and proper configuration is loaded with > >>> one-click. > >>> > >>> Compared to r43, this is mostly a maintenance release without any > >>> major new functionality, but with improved robustness in the HA and > >>> luxury querying as well as several other fixes. Here are the specific > >>> improvements over 43: > >>> > >>> - Made several HA fixes and improvements, many identified by > Bart > >>> Gaquie by testing with more than a two-server Magma Node. Many thanks > >>> Bart. > >>> - Updated MaQueryExecutor>>#fractionComplete to answer an > unreduced > >>> Fraction instead of a reduced one. This convey's more information; > >>> since the denominator represents the total number of elements in the > >>> final result. Thanks again to Bart Gauqie. > >>> - Upgraded MagmaCollectionReader>>#release to allow give a > >>> well-behaved application much freer access to the "luxury" query > >>> features of MagmaCollections. It is essential for applications > >>> employing luxury query features of Magma for ad-hoc querying, to > >>> #release the Reader returned from the query so that resources on the > >>> server can be freed. > >>> - Now properly truncating the applied.images file, so it doesn't > >>> grow > >>> and grow.. > >>> - Now, when a repository is opened locally, if it's location has > >>> never been set (new repository) or was a different *local* location, > >>> then update it to the new aMagmaLocalLocation. If it was formerly a > >>> network-hosted server, do not update since we could be here simply > >>> just for re-opening that repository. So, to go from a remote > >>> repository to a local one, you have to manually update the node's > >>> primaryLocation. > >>> - Server no longer allows any clients to log in with the system > >>> name, > >>> since it is sometimes checked for special-purpose server housekeeping. > >>> - Updated MagmaSession's standard printing method, again! > >>> - Added MagmaCollectionReader>>#sortBy:makeDistinct:descending: > and > >>> #sortBy:makeDistinct:descending:. > >>> - Made MaRepositoryDisconnectRequest asynchronous, it now > returns > >>> considerably faster! > >>> - Fix for a recent MagmaCollection optimization. > >>> - Removed hard-reference to OSProcess. > >>> - Patch for #removeListener to avoid DependentsArray problem. > >>> - Fixed a ReadStrategy regression. > >>> _______________________________________________ > >>> Magma mailing list > >>> Magma(a)lists.squeakfoundation.org > >>> http://lists.squeakfoundation.org/mailman/listinfo/magma > >> > >> > >> _______________________________________________ > >> Magma mailing list > >> Magma(a)lists.squeakfoundation.org > >> http://lists.squeakfoundation.org/mailman/listinfo/magma > >> > >> > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

1 0

magma on squeak trunk
by radoslav hodnicak 11 Feb '10

11 Feb '10

Hello, is Magma supported/working on the Squeak trunk images? I've installed r43final from SS into my trunk image (update 9308) and I get this error when trying to create a new database (happens with r44beta2 too) MagmaUserError: Invalid reference, an object may not change during serialization. rado stack trace [] in [] in [] in MaCommitLogEntry>>linkObjectModel Dictionary>>at:ifAbsent: [] in [] in MaCommitLogEntry>>linkObjectModel MaFixedObjectBuffer(MaObjectBuffer)>>instVarsDoWithIndex: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - [] in MaCommitLogEntry>>linkObjectModel [] in MaCommitPackage>>objectsDo: [] in MaSerializedGraphBuffer>>buffersDo: MaSerializedGraphBuffer>>bufferPositionsDo: MaSerializedGraphBuffer>>buffersDo: MaCommitPackage>>objectsDo: MaCommitLogEntry>>linkObjectModel MaCommitLogEntry>>link [] in MaObjectRepository>>write: BlockClosure>>ensure: [] in Mutex>>critical: [] in Semaphore>>critical: BlockClosure>>ensure: Semaphore>>critical: Mutex>>critical: MaObjectRepository>>commitCritical: MaObjectRepository>>write: MaObjectRepository>>submitAll:for:beginAnother: [] in MagmaRepositoryController>>forceWritePackage: BlockClosure>>ensure: MagmaRepositoryController>>forceWritePackage: MagmaRepositoryController>>forceWrite: MagmaRepositoryController>>createRepositoryAt: MagmaRepositoryController class>>create: MagmaRepositoryController class>>create:root:

2 1

New Smalltalk-Research group
by Mariano Martinez Peck 08 Feb '10

08 Feb '10

Hi folks. We were discussing about this in the Pharo mailing list but the idea is for all Smalltalkers. I am not sure if this will work, but it is worth to try it as I don't have anything to loose. We were thinking to have a place, an environment and hopefully a community, where we can freely discuss about Smalltalk papers or OO in general. All smalltalkers of all flavors can join, discuss, tell their experiences and thoughts, share and learn. The main purpose about that list is: - be able to FREELY discuss about papers about Smalltalk or OO in general. I say freely because maybe someone gives an opinion of a paper that the person who wrote it is also in this place. We are all professional and I think we can discuss with respect. - LEARN. Other uses: - Don't reinvent the wheel. Maybe I wanted to do something and I read that XXX person did YYY. So, I can look at it. - Be aware of what other people is doing, working, writing and learning. - Have different opinions of a certain topic / paper. - A little step to join all the Smalltalk community in one place. We can meet people, join forces, etc. - Help in the preparation, ANN, collaborate, etc in Workshops, conferences, and so on. - Ask for help on review. Several times someone has several papers to review for a certain conference. This can be a place to ask for that help. - Publish papers that were rejected from someone. How many times some papers where rejected but do you still read it and find it useful ? - Educate people and being educated. - Share latex template, commands, or tricks related to smalltalk code for example. - Discuss about research in general. - Ask for a certain topic. Suppose I want to start to work in XXX topic, I can ask to see if someone knows related papers or work. - others In two words: DISCUSS AND LEARN. FAQ: 1) Which is the address? http://groups.google.com/group/smalltalk-research 2) Do I need to be "Researcher" to join ? Not necessary. You may just be interested. 3) Is there a Nabble interface? Yes: http://n4.nabble.com/Smalltalk-Research-f1473466.html Now, please what I would appreciate is if you can help me to you distribute (I am not in Gemstone, Cincom or GNU for example) this ANN. It would be cool to create a community. I know there are a lot of Smalltalk researchers that doesn't have time to follow the active smalltalks lists. If you can send private mails to them would be fantastic! Thank you very much. Mariano

1 0

How to do data merging
by Dave Woodward 03 Feb '10

03 Feb '10

I'm using Magma in a project where there are users who have their own offline Magma database for data collection. When these users have an internet connection, their data will be uploaded and "merged" with the data in the Magma database on the server. Both the server and the client are running Pharo. The user will pretty much be the master of their own subset of data, however the data could be changed on the server. My question is if there is already any functionality within Magma to perform some sort of "data merge"? I think I'll have to make the algorithm myself. Right now I'm thinking of making some sort of a "changeset" on each individual object in the database that tracks changed to specific ivars, and the merge would compare read/write timestamps and then fall back on examining the individual changes, and finally throw some error and allow the user to manually choose the winning data. I've seen, but never used, the MVCC and change conflicts that CouchDB does on a per-document basis and I'm kind of thinking in those terms. But I'd just like to know if there is already something out there that I may not know about that I can use. Any feedback would be appreciated! Thanks! -- Dave Woodward ................................................... www.promedmedical.net davewoodward(a)promedmedical.net

2 1

Nabble users
by Geert Claes 02 Feb '10

02 Feb '10

For those who use online forums, there is a Smalltalk category grouping several Smalltalk mailing lists (including Magma) together on Nabble: http://n4.nabble.com/Smalltalk-f1294792.html ps. is there a logo for Magma? -- View this message in context: http://n4.nabble.com/Nabble-users-tp1459887p1459887.html Sent from the Magma mailing list archive at Nabble.com.

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Magma February 2010