I have a very big test suite that runs for a long time without any problems, and with the update to 2.6.7, it gets an error. It's the same error on MacOS and Linux (arm/x86) If I run it with 2.6.6 all good, if it's 2.6.7 it fails. I added a checksum in the write and read methods. (there are only uint8 buffer written) I'm sorry to been lazy not to track it down to the root cause: filtered result of the file x for 2.6.6 β¨β¨β¨
out.2.6.6:DenoFileSystem-writefile x object 188 04b785c8bab9ffe982fd0ffea850eca7af1fd483b0e94f4f0ab6b935c6ba80b1 out.2.6.6:DenoFileSystem-readfile x object 188 04b785c8bab9ffe982fd0ffea850eca7af1fd483b0e94f4f0ab6b935c6ba80b1
out.2.6.6:DenoFileSystem-writefile x object 188 04b785c8bab9ffe982fd0ffea850eca7af1fd483b0e94f4f0ab6b935c6ba80b1 out.2.6.6:DenoFileSystem-readfile x object 188 04b785c8bab9ffe982fd0ffea850eca7af1fd483b0e94f4f0ab6b935c6ba80b1
out.2.6.7:DenoFileSystem-writefile x object 188 04b785c8bab9ffe982fd0ffea850eca7af1fd483b0e94f4f0ab6b935c6ba80b1 out.2.6.7:DenoFileSystem-readfile x object 188 2e1c1161d02762d89690689df5c1e7e625d5ec32d2c300571ea84ca5883a2d7f
out.2.6.7:DenoFileSystem-writefile x object 188 04b785c8bab9ffe982fd0ffea850eca7af1fd483b0e94f4f0ab6b935c6ba80b1 out.2.6.7:DenoFileSystem-readfile x object 188 2e1c1161d02762d89690689df5c1e7e625d5ec32d2c300571ea84ca5883a2d7f