Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also orlearn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also.Learn more about diff comparisons here.
base repository:DaveLak/oss-fuzz-inputs
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base:main
Choose a base ref
Loading
...
head repository:gitpython-developers/qa-assets
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare:main
Choose a head ref
Loading
Checking mergeability… Don’t worry, you can still create the pull request.
  • 14commits
  • 354files changed
  • 3contributors

Commits on May 7, 2024

  1. Remove assets for unrelated projects

    This repository was forked from a repo that houses assets for severalprojects that are not maintained by, nor related to, GitPython orGitPython's maintainers. As such, they do not belong in this repository.
    @DaveLak
    DaveLak committedMay 7, 2024
    Configuration menu
    Copy the full SHA
    6fe6924View commit details
    Browse the repository at this point in the history

Commits on May 8, 2024

  1. Configuration menu
    Copy the full SHA
    497d618View commit details
    Browse the repository at this point in the history

  2. Restructure Fuzzer Seed Data

    **Merging this change requires a corresponding PR to be merged at the same timein the GitPython repo to update the OSS-Fuzz scripts to prevent breaking thebuilds.**The most significant change introduced here is replacing the `.zip` filescontaining seed corpora with sub-directories for each fuzz target containing anuncompressed corpus. This change makes it easier to update each corpus on aper-input-blob basis, as well as making the content of each corpus easier toinspect manually.The inputs added in this commit are taken directly from the corpora backupsgenerated by ClusterFuzz/OSS-Fuzz and can (and should) likely be reduced totheir minimal sets in a follow-up PR.Other changes:- Renamed the `dict` sub-directory to `dictionaries` for clarity.- Updated the README to better document what this repository contains. The README  could use some improvement as well, including instructions for contributing and  generating new inputs, but for now it should be good enough (I hope.) The  "Dictionaries" section was migrated from the GitPython fuzzing README.
    @DaveLak
    DaveLak committedMay 8, 2024
    Configuration menu
    Copy the full SHA
    bdf5a5dView commit details
    Browse the repository at this point in the history

  3. Merge pull request#2from gitpython-developers/refactor-gitpython-di…

    …r-and-improve-readmeRestructure Fuzzer Seed Data
    @Byron
    Byron authoredMay 8, 2024
    Configuration menu
    Copy the full SHA
    c1a5b83View commit details
    Browse the repository at this point in the history

  4. Use LibFuzzer's-merge=1 option to prune fuzz_config corpus

    This change reduces the corpus to a minimal set test inputs thatgenerate the same coverage as they did before this change, meaningthe deleted inputs were redundant.
    @DaveLak
    DaveLak committedMay 8, 2024
    Configuration menu
    Copy the full SHA
    a2c789eView commit details
    Browse the repository at this point in the history

  5. Use LibFuzzer's-merge=1 option to prune fuzz_repo corpus

    This change reduces the corpus to a minimal set test inputs thatgenerate the same coverage as they did before this change, meaningthe deleted inputs were redundant.Two new inputs were discovered and added.
    @DaveLak
    DaveLak committedMay 8, 2024
    Configuration menu
    Copy the full SHA
    94d9539View commit details
    Browse the repository at this point in the history

  6. Use LibFuzzer's-merge=1 option to prune fuzz_blob corpus

    This change reduces the corpus to a minimal set test inputs thatgenerate the same coverage as they did before this change, meaningthe deleted inputs were redundant.
    @DaveLak
    DaveLak committedMay 8, 2024
    Configuration menu
    Copy the full SHA
    e9d1264View commit details
    Browse the repository at this point in the history
  7. Configuration menu
    Copy the full SHA
    2eb9594View commit details
    Browse the repository at this point in the history

  8. Add corpus for newfuzz_diff.py fuzz target

    The `fuzz_diff` target is introduced in:gitpython-developers/GitPython#1914
    @DaveLak
    DaveLak committedMay 8, 2024
    Configuration menu
    Copy the full SHA
    315fec1View commit details
    Browse the repository at this point in the history

Commits on May 9, 2024

  1. Configuration menu
    Copy the full SHA
    60c8183View commit details
    Browse the repository at this point in the history

Commits on May 30, 2024

  1. Configuration menu
    Copy the full SHA
    1582d2fView commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    505e9e5View commit details
    Browse the repository at this point in the history

Commits on Aug 13, 2024

  1. Updatefuzz_submodule's seed corpus with new inputs

    Use these seed inputs are a combination of data generated by localand remote ClusterFuzz runs of the fuzz target that have beenpruned/minimized with LibFuzzer's -merge=1 option.
    @DaveLak
    DaveLak committedAug 13, 2024
    Configuration menu
    Copy the full SHA
    f93ac2aView commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    85fc51fView commit details
    Browse the repository at this point in the history
Loading
[8]ページ先頭
©2009-2025 Movatter.jp