[Glass] SIXX load conflict

[Dario Trussardi via Glass]

Dale,

> 
> On 03/06/2015 02:19 AM, Dario Trussardi via Glass wrote:
>> Dale,
>> 
>>> Dario,
>>> 
>>> I did a fresh createTodeStone using the latest gsDevKitHome release (SHA: 8fdc73fb176cf7e0ce33ad7d21eb448ba94ef5a6) and running the GsUpgrader-Core load multiple times does not run out of memory ..
>> 
>> I do test in a new clean tODE stone.   All works fine without error.
>> 
>> In the stone where the system erase the out of memory error   i loaded :
>> 
>> GsDeployer
>> 
>>             bulkMigrate: [ {#('Seaside3' '3.0.13' 'http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main').
>> 
>>             #('ZincHTTPComponents' '1.1' 'http://www.squeaksource.com/ZincHTTPComponents').
>> 
>>             #('Magritte3' '3.0' 'http://www.squeaksource.com/MetacelloRepository').
>> 
>>             #('Magritte3AddOns' '3.0.0' 'http://www.squeaksource.com/MetacelloRepository').
>> 
>>             #('Pier3' '3.0.0' 'http://www.squeaksource.com/MetacelloRepository').
>> 
>>             #('Pier3AddOns' '3.0.3' 'http://www.squeaksource.com/MetacelloRepository')}
>> 
>>             do: [ :ar | 
> 
> So Dario, I want to START here ... please supply the full load statement that you are using ... you have cut off this expression so I cannot see how you  are actually doing the load .... When I asked you to "add" the following:
> 
>   #( 'XMLSupport' '1.2.2' 'http://seaside.gemtalksystems.com/ss/MetacelloRepository')

GsDeployer
  bulkMigrate: [ 
    {#('Seaside3' '3.0.13' 'http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main').
    #('ZincHTTPComponents' '1.1' 'http://www.squeaksource.com/ZincHTTPComponents').
    #('Magritte3' '3.0' 'http://www.squeaksource.com/MetacelloRepository').
    #('Magritte3AddOns' '3.0.0' 'http://www.squeaksource.com/MetacelloRepository').
    #('Pier3' '3.0.0' 'http://www.squeaksource.com/MetacelloRepository').
    #('Pier3AddOns' '3.0.3' 'http://www.squeaksource.com/MetacelloRepository').
	#( 'XMLSupport' '1.2.2' 'http://seaside.gemtalksystems.com/ss/MetacelloRepository')}
      do: [ :ar | 
        | projectName version repository |
        projectName := ar at: 1.
        version := ar at: 2.
        repository := ar at: 3.
        Metacello new
          configuration: projectName;
          repository: repository;
          get.
        Metacello new
          configuration: projectName;
          version: version;
          repository: repository;
          onUpgrade: [ :ex :existing :new | 
                existing locked
                  ifTrue: [ ex disallow ]
                  ifFalse: [ ex allow ] ];
          onConflict: [ :ex | ex disallow ];
          load.
        Metacello new
          configuration: projectName;
          version: version;
          repository: repository;
          lock ] ]

It work fine in a new tODE stone  ( N.B.  i add the #( 'XMLSupport' '1.2.2' 'http://seaside.gemtalksystems.com/ss/MetacelloRepository') )

After i do:

GsDeployer bulkMigrate: [
  Metacello new
      baseline: 'SIXX';
      repository: 'github://glassdb/SIXX:master/repository';
      load ].

SixxExamples example2   		also work fine.

Thanks.

I submit the all same commands into a tODE stone where i found SIXX error.

On it when i do:		 SixxExamples example2   

	the system go into error :

	nextWhitespace
	| nextChar |

	writeBuffer reset.
	[(nextChar := self peek) notNil
		and: [SeparatorCharacters includes: nextChar]]
		whileTrue: [writeBuffer nextPut: self next].
	^ writeBuffer stringContents.

where SeparatorCharacters is not defined .

I can work with new tODE stone if it is complicate solving this.

Question :

	a) for remove a tODE stone is sufficient  remove the relative   ..... /stones/ xyz  directory ?

	b) for my first deploy environment i refer to the latest  gsDevKit release.  it's good

Ciao,

	Dario

> 
> I was referring to your list of load statements above ... I still want to see the full expression, so that I can make sure that you suing `Metacello new` to load things and I'm pretty sure that the `lock` statements should be visible as well, but I want to see what you are actually using ...
> 
> With regards to getting the latest gsDevKit release ... yes the `git pull` command is the proper thing to do ... 
> 
> ....
> 
> But I want to emphasize that if you don't `lock` XMLSupport to version 1.2.2, then it is likely that SIXX will fail. I haven't seen this myself, but I have confirmed that recently the XMLSupport configuration was changed to load the very latest XML code and that code may not have been properly ported to GemStone ....
> 
> Let's get everything working including SIXX based on using a freshly built tODE stone and then go from there...
> 
> Dale
> 
> _______________________________________________
> 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/20150306/5f290b8b/attachment-0001.html>