Skip to content

Fix container bug#162

Merged
louismerlin merged 3 commits intomainfrom
fix-creation-time
Apr 9, 2026
Merged

Fix container bug#162
louismerlin merged 3 commits intomainfrom
fix-creation-time

Conversation

@louismerlin
Copy link
Copy Markdown
Collaborator

We have seen the following:

thread 'main' (4108434) panicked at /home/vscode/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/ziggy-1.5.4/src/bin/cargo-ziggy/fuzz.rs:329:58:
called `Result::unwrap()` on an `Err` value: Error { kind: Unsupported, message: "creation time is not available for the filesystem" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

This should fix that.

@louismerlin louismerlin merged commit c994192 into main Apr 9, 2026
4 checks passed
@louismerlin louismerlin deleted the fix-creation-time branch April 9, 2026 13:27
chris-srlabs added a commit that referenced this pull request Apr 10, 2026
Follows up on #162, handling filesystems (or platforms) with missing
modification times conservatively. In that case disable early skipping
based on file metadata when syncing corpus or in coverage worker.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant