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

What to do if issue is raised in dependent library? #4999

Closed
tbeu opened this issue Jan 18, 2021 · 1 comment
Closed

What to do if issue is raised in dependent library? #4999

tbeu opened this issue Jan 18, 2021 · 1 comment

Comments

@tbeu
Copy link
Contributor

tbeu commented Jan 18, 2021

Most of the open matio fuzzing issues seem to be related to the hdf5 v1.12.0 library dependency which is is not being fuzzed by oss-fuzz. What can I do to get these open issues properly addressed. Can I reassign them to the HDF5 developers? Can we add secondary contact to the project.yaml?

@inferno-chromium
Copy link
Collaborator

Most of the open matio fuzzing issues seem to be related to the hdf5 v1.12.0 library dependency which is is not being fuzzed by oss-fuzz. What can I do to get these open issues properly addressed. Can I reassign them to the HDF5 developers? Can we add secondary contact to the project.yaml?

Yes you can add them to any bugs, then they get auto-access to report. Also, you can add devs to project.yaml if that is easier. Unfortunately, we don't have a good solution, other than encouraging those devs to see these reports and then look at trunk integration as a new OSS-Fuzz project.

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

No branches or pull requests

2 participants