Open brunobuzzi opened 4 years ago
Modifying the FileStream (https://github.com/jgfoster/Jade/blob/master/sources/MCRepositoryBrowser.cls#L235) to be text: true it seem that fix the issue but it need more testing in order to do a Pull Request.
I believe that the difference between text and binary is that with text Windows will add a CR before every LF output. I think that a Topaz File-in would not expect to have those extra characters (though they might not hurt; not sure). But my inclination would be to leave the text just the way GemStone expects. Of course, it would be helpful to avoid the walkback, and clearly something is wrong. Do you have a simple Monticello repository that reproduces the problem?
This is still not working. It happens with all repositories I trie Jade.ERRORS.txt d
Here is the stack: 21/01/2020 17:14:48: 'Primitive failed: Se pasó un parámetro no válido a un servicio o función como segundo argumento.' ByteArray(Object)>>primitiveFailed: ByteArray(Object)>>_primitiveError:at:put: ByteArray(Object)>>basicAt:put: FileStream>>primitiveBasicNextPut: FileStream>>basicNextPut: ByteArray(SequenceableCollection)>>encodeOn:put: FileStream>>primitiveNextPut: FileStream>>nextPut: Utf8String(String)>>appendToStream: FileStream>>nextPutAll: MCRepositoryBrowser>>saveAsTopazFileIn