-
Notifications
You must be signed in to change notification settings - Fork 37
Return file creation times on Linux (using statx) #248
New issue
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
Changes from all commits
1307013
0b7dc95
26270cd
c7f65a2
6112c88
29cd8dd
2eca023
5aa6a77
7cee463
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -872,3 +872,117 @@ fn reopen_fd() { | |
let tmpdir2 = check!(cap_std::fs::Dir::reopen_dir(&tmpdir.as_filelike())); | ||
assert!(tmpdir2.exists("subdir")); | ||
} | ||
|
||
#[test] | ||
fn metadata_vs_std_fs() { | ||
let tmpdir = tmpdir(); | ||
check!(tmpdir.create_dir("dir")); | ||
let dir = check!(tmpdir.open_dir("dir")); | ||
let file = check!(dir.create("file")); | ||
|
||
let cap_std_dir = check!(dir.dir_metadata()); | ||
let cap_std_file = check!(file.metadata()); | ||
let cap_std_dir_entry = { | ||
let mut entries = check!(dir.entries()); | ||
let entry = check!(entries.next().unwrap()); | ||
assert_eq!(entry.file_name(), "file"); | ||
assert!(entries.next().is_none(), "unexpected dir entry"); | ||
check!(entry.metadata()) | ||
}; | ||
|
||
let std_dir = check!(dir.into_std_file().metadata()); | ||
let std_file = check!(file.into_std().metadata()); | ||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This test is much nicer now, I think. However, it's a little funny as is. It does all this setup to extract metadata in various ways from cap_std and std, but then it only compares the created times of the metadata and nothing else. Thoughts? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. On one hand, creation times have an interesting enough implementation landscape that I feel it's justified to have a fair amount of test setup just for that one purpose, so this seems fine. On the other, since we have all this setup here, it'd be nice to expand this to test all of I don't want to bog you down if you're working on a project which just needs the creation times fix. So I'll leave it up to you for now. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ok, I expanded this out for all of the accessible Metadata (with only Unix extensions for now). |
||
match std_dir.created() { | ||
Ok(_) => println!("std::fs supports file created times"), | ||
Err(e) => println!("std::fs doesn't support file created times: {}", e), | ||
} | ||
|
||
check_metadata(&std_dir, &cap_std_dir); | ||
check_metadata(&std_file, &cap_std_file); | ||
check_metadata(&std_file, &cap_std_dir_entry); | ||
} | ||
|
||
fn check_metadata(std: &std::fs::Metadata, cap: &cap_std::fs::Metadata) { | ||
assert_eq!(std.is_dir(), cap.is_dir()); | ||
assert_eq!(std.is_file(), cap.is_file()); | ||
assert_eq!(std.is_symlink(), cap.is_symlink()); | ||
assert_eq!(std.file_type().is_dir(), cap.file_type().is_dir()); | ||
assert_eq!(std.file_type().is_file(), cap.file_type().is_file()); | ||
assert_eq!(std.file_type().is_symlink(), cap.file_type().is_symlink()); | ||
#[cfg(unix)] | ||
{ | ||
use std::os::unix::fs::FileTypeExt; | ||
assert_eq!( | ||
std.file_type().is_block_device(), | ||
cap.file_type().is_block_device() | ||
); | ||
assert_eq!( | ||
std.file_type().is_char_device(), | ||
cap.file_type().is_char_device() | ||
); | ||
assert_eq!(std.file_type().is_fifo(), cap.file_type().is_fifo()); | ||
assert_eq!(std.file_type().is_socket(), cap.file_type().is_socket()); | ||
} | ||
|
||
assert_eq!(std.len(), cap.len()); | ||
|
||
assert_eq!(std.permissions().readonly(), cap.permissions().readonly()); | ||
#[cfg(unix)] | ||
{ | ||
use std::os::unix::fs::PermissionsExt; | ||
// The standard library returns file format bits with `mode()`, whereas | ||
// cap-std currently doesn't. | ||
assert_eq!(std.permissions().mode() & 0o7777, cap.permissions().mode()); | ||
Comment on lines
+934
to
+936
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This was unexpected and a bit surprising to me. Is it intentional? If so, is that documented somewhere? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It's cap-std's intention to match std's behavior at least, so it looks like a bug in cap-std. I filed #249 to track this. |
||
} | ||
|
||
// If the standard library supports file modified/accessed/created times, | ||
// then cap-std should too. | ||
if let Ok(expected) = std.modified() { | ||
assert_eq!(expected, check!(cap.modified()).into_std()); | ||
} | ||
// The access times might be a little different due to either our own | ||
// or concurrent accesses. | ||
const ACCESS_TOLERANCE_SEC: u32 = 60; | ||
Comment on lines
+944
to
+946
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I still don't love this but didn't want to assume we made the cap or std access first, and I wanted to check the access times weren't wildly far into the future either. I guess it's pretty easy to find and update later if it causes trouble. |
||
if let Ok(expected) = std.accessed() { | ||
let access_tolerance = std::time::Duration::from_secs(ACCESS_TOLERANCE_SEC.into()); | ||
assert!( | ||
((expected - access_tolerance)..(expected + access_tolerance)) | ||
.contains(&check!(cap.accessed()).into_std()), | ||
"std accessed {:#?}, cap accessed {:#?}", | ||
expected, | ||
cap.accessed() | ||
); | ||
} | ||
if let Ok(expected) = std.created() { | ||
assert_eq!(expected, check!(cap.created()).into_std()); | ||
} | ||
|
||
#[cfg(unix)] | ||
{ | ||
use std::os::unix::fs::MetadataExt; | ||
assert_eq!(std.dev(), cap.dev()); | ||
assert_eq!(std.ino(), cap.ino()); | ||
assert_eq!(std.mode(), cap.mode()); | ||
assert_eq!(std.nlink(), cap.nlink()); | ||
assert_eq!(std.uid(), cap.uid()); | ||
assert_eq!(std.gid(), cap.gid()); | ||
assert_eq!(std.rdev(), cap.rdev()); | ||
assert_eq!(std.size(), cap.size()); | ||
assert!( | ||
((std.atime() - i64::from(ACCESS_TOLERANCE_SEC)) | ||
..(std.atime() + i64::from(ACCESS_TOLERANCE_SEC))) | ||
.contains(&cap.atime()), | ||
"std atime {}, cap atime {}", | ||
std.atime(), | ||
cap.atime() | ||
); | ||
assert!((0..1_000_000_000).contains(&cap.atime_nsec())); | ||
assert_eq!(std.mtime(), cap.mtime()); | ||
assert_eq!(std.mtime_nsec(), cap.mtime_nsec()); | ||
assert_eq!(std.ctime(), cap.ctime()); | ||
assert_eq!(std.ctime_nsec(), cap.ctime_nsec()); | ||
assert_eq!(std.blksize(), cap.blksize()); | ||
assert_eq!(std.blocks(), cap.blocks()); | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any idea when the rustix version will be updated? I don't have a sense of how big that is, so I didn't want to add it to this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The biggest thing for cap-std is that there are some semver incompatibilities between versions of io-lifetimes, which is tracking changes from I/O safety stabilization. Fortunately, the FCP looks to be almost done. Once it's done, I plan to do an io-lifetimes release and then a rustix 0.35 release, and then update cap-std and various other things.