nickva commented on issue #5129: URL: https://github.com/apache/couchdb/issues/5129#issuecomment-2223996205
Agree with @rnewson. ``` <<131,0,104,2,100,0,7,107,112,95... ``` The first byte `131` looked like a proper initial marker of an uncompressed term. It's not followed by 80, so it's not compressed https://github.com/apache/couchdb/blob/c93940a66e85d5d9600d17cb38e44f62fd91585b/src/couch/src/couch_compress.erl#L22-L26 `0` following `131` seems odd on first look at https://www.erlang.org/doc/apps/erts/erl_ext_dist.html#introduction. The next `104,2` looks like a proper small tuple <img width="675" alt="Screenshot 2024-07-11 at 5 42 53 PM" src="https://github.com/user-attachments/assets/4a1f3f45-31d3-4834-90e4-e35eab5809c5";> Which is probably what we might expect in a kp node. But turning a tuple into a binary doesn't show a 0 after 131 ``` > erlang:term_to_binary({a, b}). <<131,104,2,100,0,1,97,100,0,1,98>> ``` @job-isabai What version of CouchDB, Erlang, OS, architecture you're running? Wonder if you backed up, or restored the data at any point. Of if there is any way to reproduce the issue? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
