We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
Thank you for this library, it's extremely useful.
In some cases I found that the reported FileInfo.ModTime() is extremely large (e.g. got 3850511446000000000, expected 1703027798)
Should the timestamp be converted to the correct epoch? XFS uses Dec 1901 instead of Jan 1970, it's an offset of 2^31 (signed vs unsigned)
Should the timestamp be converted to the correct units? XFS uses nanosecond precision, it's a factor of 10^9.
The XFS filesystem was created today with xfsprogs 6.1. Probably that means it uses bigtime feature. Does this library support bigtime?
bigtime
The text was updated successfully, but these errors were encountered:
I will check... soon
Sorry, something went wrong.
No branches or pull requests
Hi,
Thank you for this library, it's extremely useful.
In some cases I found that the reported FileInfo.ModTime() is extremely large (e.g. got 3850511446000000000, expected 1703027798)
Should the timestamp be converted to the correct epoch? XFS uses Dec 1901 instead of Jan 1970, it's an offset of 2^31 (signed vs unsigned)
Should the timestamp be converted to the correct units? XFS uses nanosecond precision, it's a factor of 10^9.
The XFS filesystem was created today with xfsprogs 6.1. Probably that means it uses
bigtime
feature. Does this library supportbigtime
?The text was updated successfully, but these errors were encountered: