This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Use Automatic Fuzzing to find bugs (e.g. as part of CI / via github action) #12789
Labels
lifecycle/stale
type/enhancement
The enhancements for the existing features or docs. e.g. reduce memory usage of the delayed messages
Is your enhancement request related to a problem? Please describe.
Quality and Security could always be optimized...
Describe the solution you'd like
Use Automatic Fuzzing to find bugs (e.g. as part of CI / via github action)
OSS-Fuzz: Continuous Fuzzing for Open Source Software
https://github.com/google/oss-fuzz
has found
As of June 2021,
OSS-Fuzz has found over
30,000 bugs
in 500 open source projects (see https://github.com/google/oss-fuzz/tree/master/projects)
now it's available as part of CI via github-actions
https://github.com/google/clusterfuzzlite
ClusterFuzzLite offers the same features as ClusterFuzz while should be very easy to setup and use. It's already said to be in use by projects like systemd and curl.
Doc: https://google.github.io/clusterfuzzlite/
=> Using it for pulsar may help to strength quality and security
going well beyond the already great introduction of spotbugs ( see https://github.com/apache/pulsar/issues?q=enable+spotbugs+) and others
The text was updated successfully, but these errors were encountered: