[Glass] Updating Zinc for Gemstone

[Dale K. Henrichs]

Johan,

The pull request[1] gets past the loading problem ... the ill-formed utf8 character wa since in the version file and there was an older fileTree bug[2] where gemstone was not encoding the monticello meta data files in utf8. 

Dale

[1] https://github.com/jbrichau/zinc/pull/4
[2] https://github.com/dalehenrich/filetree/issues/72

----- Original Message -----
| From: "Dale K. Henrichs" <dale.henrichs at gemtalksystems.com>
| To: "Johan Brichau" <johan at yesplan.be>
| Cc: glass at lists.gemtalksystems.com
| Sent: Monday, November 18, 2013 12:37:33 PM
| Subject: Re: [Glass] Updating Zinc for Gemstone
| 
| ... I turned on 3.1.0.4 just for grins and it turns out that the
| default Metacello loaded into 2.1.0.4 has a better error message[1]:
| 
|   --transcript--'travis---->travisCI.st'
|   --transcript--'...RETRY->BaselineOfZinc'
|   --transcript--'...RETRY->BaselineOfZinc'
|   --transcript--'gofer repository error: ''GoferRepositoryError:
|   string contents are ill-formed Utf8 at byte offset
|   76507''...ignoring'
|   --transcript--'...FAILED->BaselineOfZinc'
| 
| So there's some invalid utf8 encountered while reading in the
| BaselineOfZinc ... will investigate further and issue a pull request
| when I have a solution..
| 
| Dale
| 
| [1] https://travis-ci.org/dalehenrich/zinc/jobs/14160177#L417
| 
| ----- Original Message -----
| | From: "Dale K. Henrichs" <dale.henrichs at gemtalksystems.com>
| | To: "Johan Brichau" <johan at yesplan.be>
| | Cc: glass at lists.gemtalksystems.com
| | Sent: Monday, November 18, 2013 12:33:17 PM
| | Subject: Re: [Glass] Updating Zinc for Gemstone
| | 
| | I've merged your gemstone2.4 into my zinc repo (travis_trouble
| | branch) and I'll see if I can get to the bottom of the baseline
| | load
| | failure ... it's a "familiar problem" but I'm failing to remember
| | the "familiar solution":)
| | 
| | Dale
| | 
| | ----- Original Message -----
| | | From: "Johan Brichau" <johan at yesplan.be>
| | | To: "Dale K. Henrichs" <dale.henrichs at gemtalksystems.com>
| | | Cc: glass at lists.gemtalksystems.com
| | | Sent: Monday, November 18, 2013 11:32:24 AM
| | | Subject: Re: [Glass] Updating Zinc for Gemstone
| | | 
| | | 
| | | On 17 Nov 2013, at 19:35, Dale K. Henrichs
| | | <dale.henrichs at gemtalksystems.com> wrote:
| | | 
| | | > Could you point to me to some examples of "Method conflicts are
| | | > showing up where no conflict exists" I just went through a
| | | > major
| | | > reshuffling of code with ston, so I might have seen something
| | | > like
| | | > this already ...
| | | 
| | | I'm currently busy merging and fixing in my fork. I cannot
| | | remember
| | | exactly which methods I was confused about yesterday, but today I
| | | hit the following problem:
| | | 
| | | The class ZnChunkedReadStreamTests was removed entirely in the
| | | master
| | | branch. Because an #expectedFailures method was added to that
| | | class
| | | in the gs branch, the merge showed a conflict on the
| | | methodProperties.json. While running through the changes and
| | | conflicts, it was not apparent to me that the class was actually
| | | removed from the master branch. So I made a wrong merge, leading
| | | to
| | | a corrupt filetree format.
| | | 
| | | Now, I get built errors on travis
| | | (https://travis-ci.org/jbrichau/zinc) I cannot make sense of,
| | | since
| | | the load happens just fine locally. On travis I get:
| | | 
| | | TravisCIHarness
| | |   value: #( 'BaselineOfZinc' )
| | |   value: 'TravisCISuccess.txt'
| | |   value: 'TravisCIFailure.txt'.
| | | %
| | | --transcript--'travis---->travisCI.st'
| | | --transcript--'...RETRY->BaselineOfZinc'
| | | --transcript--'...RETRY->BaselineOfZinc'
| | | --transcript--'gofer repository error:
| | | #''GoferRepositoryError''...ignoring'
| | | --transcript--'...FAILED->BaselineOfZinc'
| | | -----------------------------------------------------
| | | GemStone: Error         Nonfatal
| | | #'MetacelloPackageSpecResolutionError'
| | | Error Category: [User] Number: 1 Arg Count: 1
| | | Arg 1: MetacelloPackageSpecResolutionError
| | 
|