[Glass] Metacello support

[Dale Henrichs via Glass]

On Fri, Nov 7, 2014 at 5:25 AM, Dario Trussardi via Glass <
glass at lists.gemtalksystems.com> wrote:

> Ciao Dale,
>
> i work around this.
>
> Now after update the system returns the same error
>>
>> When i work on package istance from Gemtools Monticello ( browse or  load
>>> command )  the system erase the error:
>>>
>>> a ArgumentError occurred (error 2718), string contents are ill-formed
>>> Utf8 at byte offset 38, - G/S[MonvisoGruppi3104 IP100 *******:3]
>>>
>>>
>> Now that you're using the latest version of FileTree on both sides and
> you are still getting the error, we can eliminate the known problems (but
> it is still possible that the package was produced by erroneous code) ...
>
>
>> The string decodeFromUTF8 begin with:
>>
>
> Ah you've got a handle on the utf8 bytes. Please send me the undecoded
> utf8 string so that I can figure out what might be going wrong.
>
>
>
> The problem is because the system wrong the reference name of the file
> when it work on package save from Pharo fileTree.
>
> Into GLASS Monticello,
>
> in this case the methodEntry name begins with   < ._ > follow the name of
> the method,   and consequently the system don't found the specific file.
>
> I change for testing:  see  *****  and all works fine
>
> MCFileTreeStCypressReader
>
> addMethodDefinitionsForClass: className methodProperties: methodProperties
> in: entries
> entries do: [ :entry | | classIsMeta | classIsMeta := false. entry name =
> 'class' ifTrue: [ classIsMeta := true ]. (entry name = 'instance' or: [
> entry name = 'class' ]) ifTrue: [ ((self fileUtils directoryFromEntry:
> entry) entries select: [ :each | each name endsWith: '.st' ]) do: [
> :methodEntry | ******* ( methodEntry name beginsWith: #($.) ) ifTrue:[
> methodEntry name: ( methodEntry name copyFrom: 3 to: methodEntry name size)
> . ]. methodEntry readStreamDo: [ :fileStream | | category source timestamp
> self
>
>
> A don't  search where the system creates the error,
>
> but i hope this considerations is enough for solving this problem.
>
> Dario, I am glad that you found a solution to your problem, but frankly I
don't think the utf8 problem was caused by the code that you "fixed".

I asked for the utf8 bytes and I would like to see the utf8 bytes as I
suspect that the utf8 problem is still lurking there for someone else to
trip across. If you give me the utf8 bytes I will have a chance to
partially characterize the problem. Please?

As to the (presumably) new problem. Removing the first three characters
from a DirectoryEntry will not do anything but ignore the file, so the real
question is where did this . file come from? If you send me the contents of
the . file and the path to the . file, we should be able to figure that out
...

I think that the real solution startes with getting my hands on the utf8
bytes and continuing that line of inquiry.

>
>
> Two other consideration:
>
> fileTree save from Pharo     is load into  GLASS Monticello without
> authorization problem.
>
>
> fileTree save from GLASS Monticello   can not load into Pharo.
>
> In this case the Pharo Monticello report for the package saved with GALSS
> Monticello :  fabricated from a Cypress format repository
>
> In the server GLASS Monticello   create the fileTree structures   without
> group authorization  and Pharo can't load it.
>
>  How i can solve this ?  ( i can't change it directly each time )
>

Ah okay, this is something new ... could you describe your setup again
and/or in more detail? I want to know  know what os you are running for
pharo and glass? Are they on the same machine? What user you are running as
for GLASS and Pharo? Sample file permissions (ls -l) after a pharo write
and after a GLASS write?

I will have to think a bit about how I will want to control file
permissions for the filetree repos ...

Dale
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20141107/88063aca/attachment.html>