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

[Mariano Martinez Peck]

On Mon, Aug 25, 2014 at 10:50 PM, Dale Henrichs <
dale.henrichs at gemtalksystems.com> wrote:

>
>
>
> On Mon, Aug 25, 2014 at 3: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?
>>
>
> There's a 'copy stack' menu item ... when the popup comes up use the
> 'copy' menu item to copy the text ... then paste should contain the
> stack...
>
> The correct Utf8>>asString method is in the package Core31x-dkh.4 ...
> double check that you've got that package loaded
>
>>
>>
Hi Dale,

Thanks for your answer. Core31x package is loaded in NEW stone, but not in
 the OLD (failing). Do you know if it should be loaded automatically?
I guess yes...but then I am not sure what it hasn't been loaded.
BTW...we agree we are talking about gemstone 3.1 right? and not seaside
3.1? because I am still using seaside 3.0.9.

Thanks




> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20140825/5bcceb45/attachment-0001.html>