[Glass] SIXX load conflict

Dale Henrichs via Glass glass at lists.gemtalksystems.com
Thu Mar 5 13:56:22 PST 2015


Dario,

I've continued my testing under the assumption that your SIXX problems 
started after loading Pier3 and it looks like the #stable version of XML 
has changed since the last time you loaded the system and used SIXX ...

At the end of the day, you just might have to use the Metacello `lock` 
on an older version of XML, until we can port SIXX to the newer version 
of XML ... at least this is my current working theory ...

Dale


On 03/05/2015 10:28 AM, Dale Henrichs wrote:
> Dario,
>
> We have to work with known stones ... apparently you have loaded other 
> code in your stone?
>
> I need to know exactly what you've done at every step of the way to be 
> able to understand what might be going wrong ...
>
> You need to always load using `Metacello new` (if you want 
> reproducible results) and in the expression below, you do not provide 
> full information about how you loaded all of the Pier and Magritte 
> code ...
>
> I am suspicious that the older versions of Pier and Magritte may be 
> interfering with the XML code, since you appear to have different XML 
> packages loaded ...
>
> Dale
> On 03/05/2015 08:12 AM, Dario Trussardi via Glass wrote:
>> Ciao Mariano,
>>
>> into stone i loaded :
>>
>> GsDeployer bulkMigrate: [ {#('Seaside3' '3.0.13' 
>> 'http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main' 
>> <http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main%27>). #('ZincHTTPComponents' 
>> '1.1' 'http://www.squeaksource.com/ZincHTTPComponents' 
>> <http://www.squeaksource.com/ZincHTTPComponents%27>). #('Magritte3' 
>> '3.0' 'http://www.squeaksource.com/MetacelloRepository' 
>> <http://www.squeaksource.com/MetacelloRepository%27>). 
>> #('Magritte3AddOns' '3.0.0' 
>> 'http://www.squeaksource.com/MetacelloRepository' 
>> <http://www.squeaksource.com/MetacelloRepository%27>). #('Pier3' 
>> '3.0.0' 'http://www.squeaksource.com/MetacelloRepository' 
>> <http://www.squeaksource.com/MetacelloRepository%27>). 
>> #('Pier3AddOns' '3.0.3' 
>> 'http://www.squeaksource.com/MetacelloRepository' 
>> <http://www.squeaksource.com/MetacelloRepository%27>)} do: [ :ar |
>>
>>
>> And i found:
>>
>> XML-Parser-monty.274
>>
>> What version of XML-Parser do you have in your stone ?
>>
>> Thanks,
>>
>> Dario
>>
>>> Hi Dario,
>>>
>>> Yes I do use Sixx, however, I don't have that issue...don't know 
>>> why. In fact, I build new stones 2 weeks ago and I could load it...
>>> Maybe you can manually remove all sixx packages and re-try the 
>>> download again, or start from a fresh extent.
>>>
>>> Cheers,
>>>
>>>
>>> On Thu, Mar 5, 2015 at 12:25 PM, Dario Trussardi via Glass 
>>> <glass at lists.gemtalksystems.com 
>>> <mailto:glass at lists.gemtalksystems.com>> wrote:
>>>
>>>     Ciao,
>>>
>>>>     Ciao,
>>>>
>>>>     i nedd to load SIXX support into   GLASS 3.1.0.6   ( stone
>>>>     created with development kit createTodeStone command ).
>>>>
>>>>>     Mariano is correct that `onLock: [:ex | ex honor];` will
>>>>>     eliminate the Warning, but I am suspicious that you are not
>>>>>     running a recent version of GLASS.
>>>>>
>>>>>     You are getting a Warning during a topaz load (I assume ... in
>>>>>     GemTools you would get a Warning dialog). There was a bug[1],
>>>>>     where the wrong default action for a Warning was triggered
>>>>>     during non-interactive loads and the bug was fixed back in June.
>>>>>
>>>>>     So I think you should upgrade GLASS1:
>>>>>
>>>>
>>>>     i follow this :
>>>>
>>>>>       Gofer new
>>>>>         package: 'GsUpgrader-Core';
>>>>>         url: 'http://ss3.gemtalksystems.com/ss/gsUpgrader';
>>>>>         load.
>>>>>       (Smalltalk at: #GsUpgrader) upgradeGLASS1.
>>>>
>>>>     but into Gemtools and into topaz this code answer :
>>>>
>>>>     ERROR 4067 , VM temporary object memory is full
>>>>     , almost out of memory, too many markSweeps since last
>>>>     successful scavenge
>>>>
>>>>     I setup  the relative to:
>>>>     SHR_PAGE_CACHE_SIZE_KB = 2000000;
>>>>     GEM_TEMPOBJ_CACHE_SIZE = 1900000;
>>>
>>>     I load:  (Smalltalk at: #GsUpgrader) upgradeGLASS1 with
>>>     commitThreshold :
>>>
>>>     .........................
>>>     ........................
>>>     "Enable AlmostOutOfMemory signal" System
>>>     signalAlmostOutOfMemoryThreshold: commitThreshold. [ (Smalltalk
>>>     at: #GsUpgrader) upgradeGLASS1.] ensure: [ "disable
>>>     AlmostOutOfMemory signal" System
>>>     signalAlmostOutOfMemoryThreshold: -1].
>>>
>>>     And this work fine.
>>>
>>>>>
>>>>>     Finally, when loading from within topaz, you should always use
>>>>>     GsDeployer class>>bulkMigrate::
>>>>>
>>>>
>>>>     I load this in any case
>>>
>>>     After i reload:
>>>
>>>>>     GsDeployer bulkMigrate: [
>>>>>       Metacello new
>>>>>           baseline: 'SIXX';
>>>>>           repository: 'github://glassdb/SIXX:master/repository';
>>>>>           load ].
>>>>
>>>>     after when i do the code: SixxExamples example2
>>>>
>>>
>>>     SixxExamples example2 report the same error:
>>>
>>>
>>>>     the system answer :
>>>>
>>>>     parseXml: xmlStringOrStream persistentRoot: persistentArrayOrNil
>>>>     | stream |
>>>>     stream := xmlStringOrStream isStream
>>>>     ifTrue: [xmlStringOrStream]
>>>>     ifFalse: [ReadStream on: xmlStringOrStream].
>>>>     ^ (XMLDOMParser parseDocumentFrom: stream persistentRoot:
>>>>     persistentArrayOrNil) topElement
>>>>
>>>>     Object _doesNotUnderstand:   parseDocumentFrom: persistentRoot:
>>>
>>>     How i can solve this problematic?
>>>
>>>     I need to load a hold version of 'XML-Parser'   ?
>>>
>>>     Anyone works with SIXX support into Glass ?
>>>
>>>     I'm ready to deploy a glass seaside application but this
>>>     problematic stop me at the end of the road.
>>>
>>>     I load SIXX support at the end of 2014, and worked fine.
>>>
>>>     Now in a new stone i found this error.
>>>
>>>     Considerations ?
>>>
>>>     Thanks,
>>>
>>>     Dario
>>>
>>>>
>>>>     Some considerations ?
>>>>
>>>>     Thanks,
>>>>
>>>>     Dario
>>>>
>>>>>
>>>>>     GsDeployer class>>bulkMigrate: wraps your code with an
>>>>>     autoCommit handler, a Warning handler, and instance migrations
>>>>>     are deferred until all of the loading is complete and then
>>>>>     migrations are done with one pass of the db...
>>>>>
>>>>>     Actually, it is not a bad idea to always use GsDeployer
>>>>>     whether or not you are loading in topaz:)
>>>>>
>>>>>     Dale
>>>>>
>>>>>     [1] https://github.com/GsDevKit/GsDevKit/issues/21
>>>>>     On 12/18/2014 04:24 AM, Mariano Martinez Peck via Glass wrote:
>>>>>>
>>>>>>     On Thu, Dec 18, 2014 at 8:10 AM, Dario Trussardi via Glass
>>>>>>     <glass at lists.gemtalksystems.com
>>>>>>     <mailto:glass at lists.gemtalksystems.com>> wrote:
>>>>>>
>>>>>>         I load SIXX support into GLASS 3.1.0.6 with the command:
>>>>>>
>>>>>>         Metacello new
>>>>>>             baseline: 'SIXX';
>>>>>>             repository: 'github://glassdb/SIXX:master/repository';
>>>>>>             load.
>>>>>>
>>>>>>         The system answer :
>>>>>>
>>>>>>         a Halt occurred (error 2709), Debugging: Warning: LOCK
>>>>>>         ENFORCED: Attempt to 'load with conflicts' new project:
>>>>>>         'ConfigurationOfGrease 1.0.3 from
>>>>>>         http://www.squeaksource.com/MetacelloRepository' when
>>>>>>         existing project: 'BaselineOfGrease [baseline] from
>>>>>>         github://GsDevKit/Grease:master/repository' is locked.
>>>>>>         New project not loaded. Use #onLock: to intercept. -
>>>>>>         G/S[Scandella3106:2]
>>>>>>
>>>>>>
>>>>>>     I think I had the same issues.
>>>>>>
>>>>>>     The most robust way I found to load code is the following.
>>>>>>     For your concrete problem, I think the key line is " onLock:
>>>>>>     [:ex | ex honor];"  but maybe you want to adapt all that code:
>>>>>>
>>>>>>     [ [ [ [
>>>>>>
>>>>>>
>>>>>>     Metacello image
>>>>>>     configuration: 'XXX';
>>>>>>     version: YYY;
>>>>>>     onLock: [:ex | ex honor];
>>>>>>             load: #(ZZZ).
>>>>>>
>>>>>>     ]
>>>>>>        on: MetacelloAllowConflictingProjectUpgrade
>>>>>>        do: [ :ex | ex defaultAction ] ]
>>>>>>        on: MetacelloAllowLockedProjectChange
>>>>>>        do: [ :ex | ex disallow ] ]
>>>>>>        on: MetacelloNameNotDefinedError
>>>>>>        do: [ :ex | ex resume ]]
>>>>>>        on: Warning
>>>>>>     do: [ :ex | ex resume ].
>>>>>>
>>>>>>     The only discussion here is to resume upon all warning. This
>>>>>>     may not be good for all cases. Sometimes the warnings are
>>>>>>     important.
>>>>>>     I think I will remove that from mine....
>>>>>>
>>>>>>     Best,
>>>>>>
>>>>>>
>>>>>>         I do some       proced commands.
>>>>>>
>>>>>>         At he end the system answer:
>>>>>>
>>>>>>                 linear load :
>>>>>>                 linear load : baseline [BaselineOfSIXX]
>>>>>>                         linear load : 1.1.8
>>>>>>         [ConfigurationOfXMLSupport]
>>>>>>         linear load : baseline [BaselineOfGrease]
>>>>>>                 atomic load : 0.243 [ConfigurationOfGsMisc]
>>>>>>                         linear load : 1.1.8
>>>>>>         [ConfigurationOfXMLSupport]
>>>>>>                         load : SIXX.310-dkh.183
>>>>>>
>>>>>>
>>>>>>         I can consider correct the loading?
>>>>>>
>>>>>>
>>>>>>         Thanks,
>>>>>>
>>>>>>                         Dario
>>>>>>
>>>>>>         P.S. The GLASS 3.1.06 is create with development kit   
>>>>>>         createTodeStone  command
>>>>>>         _______________________________________________
>>>>>>         Glass mailing list
>>>>>>         Glass at lists.gemtalksystems.com
>>>>>>         <mailto:Glass at lists.gemtalksystems.com>
>>>>>>         http://lists.gemtalksystems.com/mailman/listinfo/glass
>>>>>>
>>>>>>
>>>>>>
>>>>>>     -- 
>>>>>>     Mariano
>>>>>>     http://marianopeck.wordpress.com
>>>>>>     <http://marianopeck.wordpress.com/>
>>>>>>
>>>>>>
>>>>>>     _______________________________________________
>>>>>>     Glass mailing list
>>>>>>     Glass at lists.gemtalksystems.com  <mailto:Glass at lists.gemtalksystems.com>
>>>>>>     http://lists.gemtalksystems.com/mailman/listinfo/glass
>>>>>
>>>>>     _______________________________________________
>>>>>     Glass mailing list
>>>>>     Glass at lists.gemtalksystems.com
>>>>>     <mailto:Glass at lists.gemtalksystems.com>
>>>>>     http://lists.gemtalksystems.com/mailman/listinfo/glass
>>>>
>>>>     _______________________________________________
>>>>     Glass mailing list
>>>>     Glass at lists.gemtalksystems.com
>>>>     <mailto:Glass at lists.gemtalksystems.com>
>>>>     http://lists.gemtalksystems.com/mailman/listinfo/glass
>>>
>>>
>>>     _______________________________________________
>>>     Glass mailing list
>>>     Glass at lists.gemtalksystems.com
>>>     <mailto:Glass at lists.gemtalksystems.com>
>>>     http://lists.gemtalksystems.com/mailman/listinfo/glass
>>>
>>>
>>>
>>>
>>> -- 
>>> Mariano
>>> http://marianopeck.wordpress.com <http://marianopeck.wordpress.com/>
>>
>>
>>
>> _______________________________________________
>> Glass mailing list
>> Glass at lists.gemtalksystems.com
>> http://lists.gemtalksystems.com/mailman/listinfo/glass
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20150305/0cbe22ad/attachment-0001.html>


More information about the Glass mailing list