Skip to content
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.

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

fix(replayer): replay corpus files in hidden dirs #254

Merged
merged 2 commits into from
Sep 15, 2024

Conversation

simonresch
Copy link
Contributor

The replayer would not execute hidden corpus files or files in hidden directories if they were in the bazel project root (#253).

The replayer would not execute hidden corpus files or files in hidden
directories if they were in the bazel project root (bazel-contrib#253).
@simonresch simonresch changed the title fix(replay): replay corpus files in hidden dirs fix(replayer): replay corpus files in hidden dirs Sep 12, 2024
Copy link
Member

@fmeum fmeum left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The fix looks good to me. Hidden files can always be filtered out with a glob in Bazel, which is far more flexible.

Wouldn't hidden files in subdirectories also have been filtered out though? This doesn't look specific to the root (d_name should just contain the basename of an entry).

@stefanbucur Could you review this for approval?

@simonresch
Copy link
Contributor Author

The fix looks good to me. Hidden files can always be filtered out with a glob in Bazel, which is far more flexible.

Wouldn't hidden files in subdirectories also have been filtered out though? This doesn't look specific to the root (d_name should just contain the basename of an entry).

@stefanbucur Could you review this for approval?

Thanks for taking a look @fmeum!

I think hidden files in sub directories works for me since the replayer is started with a prepared corpus directory with file names based on the full path inside the bazel project. E.g. src/.hidden/foo end up in the corpus directory as src-.hidden-foo which was not filtered out (see https://github.com/bazelbuild/rules_fuzzing/blob/691c8938ff87681f7281cc4ba840e74e3b63c54b/fuzzing/tools/make_corpus_dir.py#L63).

Copy link
Collaborator

@stefanbucur stefanbucur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the fix!

`actions/upload-artifact` v1 and v2 are no longer supported.
@simonresch
Copy link
Contributor Author

@stefanbucur I added a second commit to update the upload-artifact action. This should get the OSS Fuzz github workflow going again. Could you take another look?

@stefanbucur stefanbucur merged commit a8d424d into bazel-contrib:master Sep 15, 2024
22 checks passed
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.

3 participants