I've added a bug to pyfuse3; the ability for me to consider a patch depends in very large part on what level of API compatibility you want to break!
Since 64 bits is insufficient to represent a nano-second timestamp, something has to become incompatible. I think the choice is down to: - add numpy (or similar) to the pyfuse dependencies - remove the *_ns properties (or at least make them return a struct/object instead) On Monday, November 23, 2020 at 10:42:47 PM UTC+11 Grunthos wrote: > Further, if my analysis is correct, then it suggests anything that uses > the pyfuse composite (double/float) field may have breakage. > > On Monday, November 23, 2020 at 10:30:52 PM UTC+11 Grunthos wrote: > >> *definitely* looks like a rounding problem with using a double-precision >> value to represent seconds + ns since 1970. For a standard double, only 6 >> decimal digits work...for ns, you need 9 places. >> >> Try this in python: >> >> >>> 1577880000.9999999 >> >> <- this is the source of the problem. >> > -- You received this message because you are subscribed to the Google Groups "s3ql" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/s3ql/0a4a5cb4-bf43-4f72-bacd-69636d26d37en%40googlegroups.com.
