Closed quipo closed 1 year ago
Thanks for reporting the issue @quipo. Could you share a test file that reproduces this error? I want to understand how is that we return a io.EOF is the documents is valid.
hi @qmuntal, have you had a chance to validate the above file?
I can't reproduce the issue, decoding simple.gltf
gives no io.EOF, at least in my Windows machine. Could you share more details? Maybe a code snippet.
Hi @qmuntal, I misread the error, the problem was not parsing the .gltf file above, but converting it to .glb and trying to open the latter. I raised a ticket here: https://github.com/qmuntal/gltf/issues/63 with a reproducing script
Superseded by https://github.com/qmuntal/gltf/pull/64
When decoding very small files (smaller than one read chunk?), the inner decoder might return io.EOF as error, alongside the document (i.e. the document read might be valid, but it's overwritten with nil in case of io.EOF)