Skip to content

OSS-Fuzz issue 415083663 #1979

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.

Sign up for GitHub

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

Jump to bottom
Closed
oss-fuzz-robot opened this issue May 2, 2025 · 1 comment · Fixed by #1984
Closed

OSS-Fuzz issue 415083663 #1979

oss-fuzz-robot opened this issue May 2, 2025 · 1 comment · Fixed by #1984

Comments

@oss-fuzz-robot
Copy link

OSS-Fuzz has found a bug in this project. Please see https://oss-fuzz.com/testcase?key=6290683537457152 for details and reproducers.

This issue is mirrored from https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=415083663 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.
Byron added a commit that referenced this issue May 3, 2025
@Byron
reproduce fuzz-failure (#1979)
9ccd762 
It's notable that this regression was introduced in `v0.2.11`.

```
❯ cargo update -p jiff
    Updating crates.io index
     Locking 2 packages to latest compatible versions
    Updating jiff v0.2.10 -> v0.2.11
    Updating jiff-static v0.2.10 -> v0.2.11
note: pass `--verbose` to see 10 unchanged dependencies behind latest
```

Thus, the issue didn't reproduce in v0.2.10.
@Byron Byron mentioned this issue May 3, 2025
Merged
1 task
Byron added a commit that referenced this issue May 3, 2025
@Byron
reproduce fuzz-failure (#1979)
6bf1be6 
It's notable that this regression was introduced in `v0.2.11`.

```
❯ cargo update -p jiff
    Updating crates.io index
     Locking 2 packages to latest compatible versions
    Updating jiff v0.2.10 -> v0.2.11
    Updating jiff-static v0.2.10 -> v0.2.11
note: pass `--verbose` to see 10 unchanged dependencies behind latest
```

Thus, the issue didn't reproduce in v0.2.10.
EliahKagan added a commit to EliahKagan/gitoxide that referenced this issue May 4, 2025
@EliahKagan
Further upgrade jiff to fix fuzz failures (GitoxideLabs#1984)
0be4dd4 
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-robot
Copy link
Author

OSS-Fuzz has closed this bug. Please see https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=415083663 for details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

reproduce fuzz-failures GitoxideLabs/gitoxide
1 participant
@oss-fuzz-robot