Update version for fs-set-times to 3.1

[jlb6740]

Received a compile error:

Compiling wasi-cap-std-sync v0.23.0 (/home/jlbirch/wasmtime_jlb6740/crates/wasi-common/cap-std-sync)
error[E0599]: the method set_times exists for struct cap_std::fs::File, but its trait bounds were not satisfied
--> crates/wasi-common/cap-std-sync/src/file.rs:84:14
|
84 | .set_times(convert_systimespec(atime), convert_systimespec(mtime))?;
| ^^^^^^^^^ method cannot be called on cap_std::fs::File due to unsatisfied trait bounds
|
::: /home/jlbirch/.cargo/registry/src/github.com-1ecc6299db9ec823/cap-std-0.13.7/src/fs/file.rs:32:1
|
32 | pub struct File {
| ---------------
| |
| doesn't satisfy _: unsafe_io::unsafe_handle::AsUnsafeFile
| doesn't satisfy cap_std::fs::File: SetTimes
|
= note: the following trait bounds were not satisfied:
cap_std::fs::File: unsafe_io::unsafe_handle::AsUnsafeFile
which is required by cap_std::fs::File: SetTimes
= help: items from traits can only be used if the trait is in scope
= note: the following trait is implemented but not in scope; perhaps add a use for it:
use fs_set_times::set_times::SetTimes;

warning: unused import: SetTimes
--> crates/wasi-common/cap-std-sync/src/file.rs:2:20
|
2 | use fs_set_times::{SetTimes, SystemTimeSpec};
| ^^^^^^^^
|
= note: #[warn(unused_imports)] on by default

error: aborting due to previous error; 1 warning emitted

For more information about this error, try rustc --explain E0599.
error: could not compile wasi-cap-std-sync

I believe this version bump is the correct solution .. though there is a chance this could just be my system after some recent updates to my environment.

[jlb6740]

Not clear why CI is choking on duplicate crate entry error. Will retrigger in a bit.

[github-actions]

Subscribe to Label Action

cc @kubkon

This issue or pull request has been labeled: "wasi"

Thus the following users have been cc'd because of the following labels:

• kubkon: wasi

To subscribe or unsubscribe from this label, edit the .github/subscribe-to-label.json configuration file.

Learn more.

[sunfishcode]

This is caused by me making what turned out to be semver-incompatible changes, while not bumping the semver versions. The fix is to also update cap-*, unsafe-io, and system-interface to their latest versions as well.

[jlb6740]

@sunfishcode Thanks! I think it's happy.

[sunfishcode]

Thanks for fixing this!

[radu-matei]

Will there be a patch update with this fix, @sunfishcode?

[sunfishcode]

Ah, is this affecting downstream users of wasmtime? If so, I'll do a release.

[sunfishcode]

I've now filed #2707 to start the process for a release.