getAllChanges returns incorrect data when DEFLATE is used about automerge HOT 4 CLOSED

Ah removing the wasm test (IOW using the JS backend) fixes the issue for me. It could be a problem in the wasm backend then i suppose 🤔

from automerge.

Confirmed that this happens with the latest wasm backend, but not with the JS backend, so I will transfer this issue to the automerge-rs repository.

The test calls Automerge.applyChanges with an empty Automerge document an a single deflate-compressed change, and then calls Automerge.getAllChanges to read back the change. getAllChanges returns only the deflate-compressed byte array, which is lacking the 11 byte header that a change should have (consisting of 4 magic bytes, 4 bytes checksum, 1 byte chunk type, and 2 bytes chunk length). Looks like case of accidentally failing to add the header.

from automerge.

Hi @nemanja-tosic I've just merged the work that should fix this thanks to @alexjg, if you could maybe pull the latest main and check it again with your test to (hopefully) confirm this fixes it?

from automerge.

As far as i can tell it works fine now.

from automerge.