OSS-Fuzz issue 415083611 #1982
Comments
1 task
EliahKagan
added a commit
to EliahKagan/gitoxide
that referenced
this issue
May 4, 2025
This upgrades `jiff` to 0.2.12 to fix fuzzing failures. The test case introduced in the previous commit now passes. Upgrading `jiff` past 0.2.11 gets the fix for BurntSushi/jiff#359, fixed in BurntSushi/jiff#360. To avoid declaring compatibility with a version that has the bug, this advances `jiff` from 0.2.10 to 0.2.12 in the `gix-archive` and `gix-date` manifests. (The changes in `Cargo.lock` are those that occur automatically when `cargo check --workspace` is run after those changes.) Fixes GitoxideLabs#1979 Fixes GitoxideLabs#1982
|
OSS-Fuzz has closed this bug. Please see https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=415083611 for details. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
OSS-Fuzz has found a bug in this project. Please see https://oss-fuzz.com/testcase?key=4683779740598272 for details and reproducers.
This issue is mirrored from https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=415083611 and will auto-close if the status changes there.
If you have trouble accessing this report, please file an issue at https://github.com/google/oss-fuzz/issues/new.
The text was updated successfully, but these errors were encountered: