Magma March 2009

magma@lists.squeakfoundation.org

11 participants
21 discussions

Re: Newbie Questions
by Chris Muller 24 Mar '09

24 Mar '09

Hmm, take a look at TestSuite>>#tests. In my image I have: tests tests isNil ifTrue: [tests := OrderedCollection new]. ^tests but it sounds like the Damien image changed it to a Set, I wonder why? Oh well.. I would revert that method back to using an OrderedCollection and try again, or don't use that image.. - Chris On Mon, Mar 23, 2009 at 11:27 PM, Ross Boylan <ross(a)biostat.ucsf.edu> wrote: > This time I installed only the tester. However, I got the same error. > > On the off chance it's relevant, I installed "Nice fonts" from the > Universe browser before installing Magma. > > #addAllFirst: is implemented on OrderedCollection. > In the TestSuite, self tests has class Set, a direct subclass of > Collection. > > Does 3.10 have a different collection hierarchy? > > On Mon, 2009-03-23 at 20:39 -0500, Chris Muller wrote: >> Hi Ross, please use the Magma installation instructions found on the Swiki: >> >> http://wiki.squeak.org/squeak/2657 >> >> You are not the first get confused by Magma's installation process. I >> may have "tried too hard" to make it easy, and ended up confusing >> people instead in many cases.. >> >> I have just updated that documentation page, made clarifications and >> placed emphasis on the important aspect of the installation which is >> regularly missed. Please give it another try! >> >> Regards, >> Chris >> >> >> On Mon, Mar 23, 2009 at 4:49 PM, Ross Boylan <ross(a)biostat.ucsf.edu> wrote: >> > On Mon, 2009-03-23 at 11:53 -0500, Chris Muller wrote: >> >> > I'm thinking of using Damien's squeak-dev 3.10 image. Should that >> >> work? >> >> >> >> Please run the Magma test suite on that image. It's really the best >> >> and only way to know. >> >> >> >> 1) Load Magma tester from SqueakMap >> >> 2) MagmaTestCase fullSuite maDebug "do it" >> > >> > It didn't get too far. In TestSuite self tests doesn't understand the >> > message #addAllFirst:. The stack trace appears below. >> > >> > Perhaps this is related to a glitch during installation: >> > >From squeakmap I loaded the r42beta2 versions of Magma Server and then >> > Magma Client. During the latter I got: >> > "You are about to load new versions of the following packages that have >> > unsaved changes in the image. If you continue, you will lose these >> > changes. >> > >> > Ma base additions >> > >> > Select Proceed to continue, or close this window to cancel the >> > operation." >> > >> > Of course, I also got messages that the packages were not known to be >> > compatible with 3.10. >> > >> > ------------------------------------ stack trace-------------------- >> > 23 March 2009 2:46:31 pm >> > >> > VM: unix - a SmalltalkImage >> > Image: Squeak3.10.2 [latest update: #7179] >> > >> > SecurityManager state: >> > Restricted: false >> > FileAccess: true >> > SocketAccess: true >> > Working Dir /usr/local/src/insurance >> > Trusted Dir /usr/local/src/insurance/secure >> > Untrusted Dir /usr/local/src/insurance/My Squeak >> > >> > Set(Object)>>doesNotUnderstand: #addAllFirst: >> > Receiver: a Set(MagmaCollectionTester>>#testPersistentEmpty {test >> > querys - persistent empty} MagmaCo...etc... >> > Arguments and temporary variables: >> > aMessage: addAllFirst: a Set(MagmaTestCase>>#testUpdateByteObjects >> > {other small...etc... >> > Receiver's instance variables: >> > tally: 18 >> > array: an Array(nil nil nil >> > MagmaCollectionTester>>#testPersistentEmpty {test q...etc... >> > >> > TestSuite>>addTestsFirst: >> > Receiver: a TestSuite >> > Arguments and temporary variables: >> > aCollection: a Set(MagmaTestCase>>#testUpdateByteObjects {other small >> > tests} Ma...etc... >> > Receiver's instance variables: >> > tests: a Set(MagmaCollectionTester>>#testPersistentEmpty {test querys >> > - persist...etc... >> > resources: nil >> > name: nil >> > >> > MagmaTestCase class>>fullSuite >> > Receiver: MagmaTestCase >> > Arguments and temporary variables: >> > >> > Receiver's instance variables: >> > superclass: MaNetworkTestCase >> > methodDict: a MethodDictionary(size 188) >> > format: 162 >> > instanceVariables: #('magmaConsole' 'peerConsole' 'clientSession' >> > 'localRoot' '...etc... >> > organization: ('initialize-release' abort abortClients >> > assertForwardRecoverySig...etc... >> > subclasses: {MagmaCollectionTester} >> > name: #MagmaTestCase >> > classPool: a Dictionary(#InitiateBackupPrereqsCompleted->nil >> > #MagmaServerAddres...etc... >> > sharedPools: nil >> > environment: a SystemDictionary(lots of globals) >> > category: #'Magma tester-SUnit tests' >> > traitComposition: nil >> > localSelectors: nil >> > >> > UndefinedObject>>DoIt >> > Receiver: nil >> > Arguments and temporary variables: >> > >> > Receiver's instance variables: >> > nil >> > >> > >> > --- The full stack --- >> > Set(Object)>>doesNotUnderstand: #addAllFirst: >> > TestSuite>>addTestsFirst: >> > MagmaTestCase class>>fullSuite >> > UndefinedObject>>DoIt >> > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - >> > Compiler>>evaluate:in:to:notifying:ifFail:logged: >> > [] in TextMorphForShoutEditor(ParagraphEditor)>>evaluateSelection {[rcvr >> > class evaluatorClass new evaluate: self selectionAsStream in: >> > ctxt...]} >> > BlockContext>>on:do: >> > TextMorphForShoutEditor(ParagraphEditor)>>evaluateSelection >> > TextMorphForShoutEditor(ParagraphEditor)>>doIt >> > [] in TextMorphForShoutEditor(ParagraphEditor)>>doIt: {[self doIt]} >> > TextMorphForShoutEditor(Controller)>>terminateAndInitializeAround: >> > TextMorphForShoutEditor(ParagraphEditor)>>doIt: >> > TextMorphForShoutEditor(ParagraphEditor)>>dispatchOnCharacter:with: >> > TextMorphForShoutEditor(TextMorphEditor)>>dispatchOnCharacter:with: >> > TextMorphForShoutEditor(ParagraphEditor)>>readKeyboard >> > TextMorphForShoutEditor(TextMorphEditor)>>readKeyboard >> > [] in TextMorphForShout(TextMorph)>>keyStroke: {[editor readKeyboard]} >> > TextMorphForShout(TextMorph)>>handleInteraction:fromEvent: >> > TextMorphForShout(TextMorphForEditView)>>handleInteraction:fromEvent: >> > TextMorphForShout(TextMorph)>>keyStroke: >> > TextMorphForShout(TextMorphForEditView)>>keyStroke: >> > TextMorphForShout(TextMorph)>>handleKeystroke: >> > KeyboardEvent>>sentTo: >> > TextMorphForShout(Morph)>>handleEvent: >> > TextMorphForShout(Morph)>>handleFocusEvent: >> > [] in HandMorph>>sendFocusEvent:to:clear: {[ActiveHand := self. >> > ActiveEvent := anEvent. e := anEvent transformedB...]} >> > [] in PasteUpMorph>>becomeActiveDuring: {[aBlock value]} >> > BlockContext>>on:do: >> > PasteUpMorph>>becomeActiveDuring: >> > HandMorph>>sendFocusEvent:to:clear: >> > HandMorph>>sendEvent:focus:clear: >> > [] in HandMorph>>sendKeyboardEvent: {[:focusHolder | anEvent wasHandled >> > ifFalse: [self sendEvent: anEvent ...]} >> > OrderedCollection>>do: >> > HandMorph>>sendKeyboardEvent: >> > HandMorph>>handleEvent: >> > HandMorph>>processEvents >> > [] in WorldState>>doOneCycleNowFor: {[:h | ActiveHand := h. h >> > processEvents. capturingGesture := capturingGest...]} >> > Array(SequenceableCollection)>>do: >> > WorldState>>handsDo: >> > WorldState>>doOneCycleNowFor: >> > WorldState>>doOneCycleFor: >> > PasteUpMorph>>doOneCycle >> > [] in Project class>>spawnNewProcess {[[World doOneCycle. Processor >> > yield. false] whileFalse. nil]} >> > [] in BlockContext>>newProcess {[self value. Processor >> > terminateActive]} >> > >> > >> > >> _______________________________________________ >> Magma mailing list >> Magma(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/mailman/listinfo/magma >> > >

1 0

Magma Client r42Beta2 on Pharo 10259
by Timothy James Ziebart 23 Mar '09

23 Mar '09

3 2

Newbie Questions
by Ross Boylan 23 Mar '09

23 Mar '09

I am considering using Magma for a new project, which really only involves a single user (me). I want a database because a previous project without one eventually produce a huge, unresponsive image. Do you recommend using r41 or the r42beta? I can be a bit of a guinea pig, but I'm more concerned with getting my program working. What channel should I use to get Magma? I gather there are several (SqueakMap, SqueakSource, UniverseBrowser). I'm thinking of using Damien's squeak-dev 3.10 image. Should that work? I will be using DateAndTime and, probably, TimeSpan's (e.g., Date, Month). Since TimeSpan's are intervals, rather than points, I'm not sure how or if they can be put in indices or used in queries. The documentation asks for attributes to be indexed. Does this mean instance variables, or can one index the results of methods? For example, if an object has a TimeSpan instance variable and methods #start and #end that give the start and endpoints of that variable, can I index on start and end? Thanks. Ross

2 3

[ANN] Magma Buffer Browser r2
by Chris Muller 23 Mar '09

23 Mar '09

This tool has been around for years, but last week I spruced it up and now even provide a Maui-based UI for it. A screenshot can be seen here: http://wiki.squeak.org/squeak/5728 To load it, - load the latest Magma server or Magma tester package from SqueakMap. - load Maui from SqueakMap. - load "Magma Buffer Browser" from SqueakMap. Enjoy, Chris

1 0

r42Beta2
by Chris Muller 23 Mar '09

23 Mar '09

I have just posted r42Beta2 to SqueakMap. - When creating a repository, Magma now creates a full-backup "seed" copy of the repository. For only the 42K of disk space it consumes, the seed repository allows any repository which has never been backed up to be restored to any point in time. It also allows a single-server production deployment to go to multi-server without having to make an initial full-backup. The seed just rolls forward via the commit-logs. - Better support for deployment of multi-server repositories that were initialized in a different environment than the deployment environment. - Support for the new Magma Buffer Browser tool. - Upgrade to MagmaForwardingProxies. Cleaner code and a bug fix. - Fixes to startup sequence to ensure MagmaRepositoryController gets to startup before MaServerSocket. - Test suite enhancements. - Chris

1 0

SeasideHelper install problem
by Udo Schneider 19 Mar '09

19 Mar '09

All, I just tried to install seasideHelper in Damiens 3.0 image using Installer squeaksource project: 'Installer'; install: 'Installer-Core'. Installer universe answer:'username' with:'admin'; answer:'password' with:'seaside'; install: 'Magma seasideHelper'; install. During the installation I get an DNU. Only after adding the following to methods does the installation succeed. ProcessorScheduler class>>current ^Processor ProcessorScheduler class>>avtiveProcess ^Processor activeProcess. CU, Udo

1 0

r42Beta1
by Chris Muller 19 Mar '09

19 Mar '09

I am pleased to announce r42Beta1, the first serious version of Magma with 24x7x365 operational capability. Magma can now serve a repository from multiple copies hosted on different physical machines, all updated virtually simultaneously as commits come in. Individual servers copies are able to be brought off-line for maintenance, compression, etc., and then simply started again to automatically rejoin the Node. Detailed documentation is available at: http://wiki.squeak.org/squeak/6101 - Chris

4 5

Magma Session connection perfomance?
by Udo Schneider 10 Mar '09

10 Mar '09

All, which connection times are "normal" for magma. I'm currently experiencing around 7 seconds for the server image to connect to the repository and 10-12 seconds to establish a session for the seaside frontend images. I do not really care about the server - however having a user to wait for 10-12 seconds for the initial page/login is quite another story. I'm currently using a base 3.10 image with r42alpha4 on a DualCore 2.4 Ghz Linux Machine. Are these times "normal"? CU, Udo

6 8

Migration headache
by Göran Krampe 04 Mar '09

04 Mar '09

Hi! Ok, so Gjallar is improving day-by-day and the current Gjallar is built on Squeak 3.10.2-7179 and MC packages "r42Alpha4" + "Magma sunit" from MagmaTester on SS. I have been working on this latest incarnation of Magma the latest few days and it seems to be working fine (although marked as alpha). I now need to migrate an existing Gjallar customer over to the above new system/version. The older Gjallar runs MagmaServerLoader-kph.35 in a 3.8.1-6747 image. This is of course a rather old Magma but it has been running for over a year, continuous use (although on the lighter side) with no serious problems at all. Good work Chris! :) Questions: 1. Would I be better off to use r41.2 than r42Alpha? Presuming that is the latest official release, which I think it is? 2. Are there migration instructions? I did the simplest thing first, just opened up the old db using the new image. Of course it says that hey, this repo is version 9 so I need to migrate it. Cool, go ahead. :) Then after that phase I stumbled on 2 issues I "solved": - Missing ivar in MaRootAnchor. Fine, seems to be "stats" so I just told Magma to go forward with that. - Then Magma blew up because it was sending "node" in #sendToWarmBackups: and getting nil. After a bit of investigation I realized this is related to the latest HA-code so this little trick seemed to repair that: MagmaRepositoryController allInstances anyOne session commit: [node := MagmaNode new] Then it got harder. :) It looks very promising at this stage, most of Gjallar seems to work fine. I can explore the db and it all looks fine except for one important thing: SortedCollections with stored sortBlocks In the old image it all works fine, in the new image I end up with a garbled SortedCollection with these ivars: array: 4081353 firstIndex: 281473902968834 lastIndex: 281473902968835 sortBlock: 4081234 ...so obviously there is a problem here with SortedCollection instances *that have sortBlocks* - because in other places I have SortedCollections with a nil sortBlock, and those work fine. Hmmm, I will try to work around this but of course it might be interesting for you to be aware of the issue. regards, Göran

2 8

Single User vs Multi User quetions
by Milan Zimmermann 03 Mar '09

03 Mar '09

Hi, Continuing with the examples in http://wiki.squeak.org/squeak/2689 It sounds like when I want to have more than 1 connection (session) to Magma, I have to use the "Server/Client" connection mode described there - the single user mode would not allow 2 correctly functional sessions, is that correct? Also a follow up question: I am not sure how to understand the following: "While your session is connected, it is recommended you keep up-to-date every 30 seconds or so changes made by other users will be reflected in the objects you visit." Thanks Milan

3 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Magma March 2009