[Glass] Problem with UTF8 encoding and Monticello after GLASS update

[Mariano Martinez Peck]

Ok Dale.... I am analyzing the history of Core package.  It seems that from
version Core.v3-dkh.86 to Core.v3-dkh.89 you have been working in exactly
the problem I am having with UTF8 and ByteArray' asString. So it is related
to this.

Second... in Core.v3-dkh.85 I read "*put the compression support classes
into a separate *
*  package that is common for GemStone2.4 and *
*  GemStone3.x*
*- this commit is from a 3.1 stone (which is compatible*
*  with 3.2) ... need to finish up with updates to 2.4*
*  and 3.0.1*

"

I doubt this external package is being loaded....Do you know if
configurationOf was updated?


Finally...how can I load an older version of github from gemtools? I can
browse with "History", but I cannot find a way to load them :(

Of course...in the OLD stone where it was working, I am
using Core.v3-dkh.77.



On Mon, Aug 25, 2014 at 10:25 PM, Mariano Martinez Peck <
marianopeck at gmail.com> wrote:

> Uffff...then I ignore for a minute the utf8 stuff (I let it without
> encoding) and yet another problem...
>
> MCMczReader >> zip
> zip ifNil:
>  [zip _ ZipArchive new.
> zip readFrom: stream].
> ^ zip
>
> Fails because ZipArchive doesn't exist. WTF??   Now I am comparing
> Core-Squeak and in the OLD stone I have lots of classes and in new stone
> only a few... In fact...it looks like I miss all Zip classes in the new
> stone. Maybe they were moved to a separate package yet that package is not
> included in the conf?
>
>
> On Mon, Aug 25, 2014 at 7:19 PM, Mariano Martinez Peck <
> marianopeck at gmail.com> wrote:
>
>>
>>
>>
>> On Mon, Aug 25, 2014 at 6:40 PM, Dale Henrichs <
>> dale.henrichs at gemtalksystems.com> wrote:
>>
>>> Mariano,
>>>
>>> It could be because I am jet-lagged and trying to read code ... but when
>>> i read the UTF8Encoding  code ( Utf8Encoding.310-dkh.31), I don't see
>>> how you are getting the ArgumentTypeError,
>>>
>>
>> No, the error is not there. The error is because in the OLD (broken)
>>
>> (UTF8Encoding newEncoder encode: 'ConfigurationOfIAM-MarianoMartinezPeck.68.mcz')
>>
>>
>> answers a Utf8 instance rather than a string (which is what happens in
>> the new).
>>
>> Then,..the type error is in the #asString.
>>
>> (UTF8Encoding newEncoder encode: 'ConfigurationOfIAM-MarianoMartinezPeck.68.mcz')
>>  asString
>>
>> Btw,...when loading from MC, the error is from
>> #encodeForHTTPWithTextEncoding: encodingName conditionBlock: conditionBlock
>>
>> where it does:
>>
>> ((GRCodec forEncoding: encodingName) encode: self) asString
>>
>> so I guess I need to see a full stack ... also verify that you have
>>> Utf8Encoding.310-dkh.31 loaded in both OLD and NEW ...
>>>
>>>
>> How can I get a string full stack from GemTools?
>>
>> Thanks
>>
>>
>>> Dale
>>>
>>>
>>>
>>> On Mon, Aug 25, 2014 at 1:47 PM, Mariano Martinez Peck <
>>> marianopeck at gmail.com> wrote:
>>>
>>>> Hi guys.
>>>>
>>>> I have a strange situation. I have 2 stones. Both using 3.1.0.5. One
>>>> stone (let's call it the OLD), was created several months ago. The other
>>>> site, let's call it the NEW, was built a week ago.
>>>>
>>>> I have just updated GLASS in both of them, using this expression:
>>>>
>>>> Metacello new
>>>>   baseline: 'GLASS1';
>>>>   repository: 'github://glassdb/glass:master/repository';
>>>>   onConflict: [ :ex | ex allow ];
>>>>   onWarning: [ :ex |
>>>>         Transcript
>>>>           cr;
>>>>           show: ex description.
>>>>         ex resume ];
>>>>   load: 'default'.
>>>>
>>>> After that... the NEW works ok. But the LAST, I cannot read any more
>>>> packages from Monticello, since I am getting a UTF error. I debug it and I
>>>> arrive to this difference:
>>>>
>>>> In NEW stone (the one that works), this works:
>>>>
>>>> (UTF8Encoding newEncoder encode:
>>>> 'ConfigurationOfIAM-MarianoMartinezPeck.68.mcz') asString
>>>>
>>>> In OLD stone, it yields a:   "a ArgumentTypeError occurred (error
>>>> 2719), for aCollection  expected a anArray( String, ByteArray), arg is a
>>>> Utf8"  when it tries to do the #asString.
>>>>
>>>> The difference is that NEW #encode: answers a string. While the OLD
>>>> answers a Utf8 instance.
>>>>
>>>> So....any workaround?
>>>>
>>>> Thanks,
>>>>
>>>>
>>>>
>>>> --
>>>> Mariano
>>>> http://marianopeck.wordpress.com
>>>>
>>>> _______________________________________________
>>>> Glass mailing list
>>>> Glass at lists.gemtalksystems.com
>>>> http://lists.gemtalksystems.com/mailman/listinfo/glass
>>>>
>>>>
>>>
>>
>>
>> --
>> Mariano
>> http://marianopeck.wordpress.com
>>
>
>
>
> --
> Mariano
> http://marianopeck.wordpress.com
>



-- 
Mariano
http://marianopeck.wordpress.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20140825/4c726f53/attachment.html>