evanrichter opened a new pull request, #1761: URL: https://github.com/apache/avro/pull/1761
The [cargo-fuzz](https://github.com/rust-fuzz/cargo-fuzz) harness can be run with `cargo +nightly fuzz run roundtrip` from the _lang/rust/avro_ folder. The second commit fixes 1 panic, 1 oom, and 1 infinite loop that the fuzzer found. ### Jira - [ ] My PR addresses the following [Avro Jira](https://issues.apache.org/jira/browse/AVRO/) issues and references them in the PR title. For example, "AVRO-1234: My Avro PR" - https://issues.apache.org/jira/browse/AVRO-XXX - [x] In case you are adding a dependency, check if the license complies with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). Cargo fuzz is dual-licensed under MIT or Apache 2.0 open source license. ### Tests - [x] My PR adds fuzz testing - [x] The code fixes do not break `cargo test` - [x] The code fixes pass fuzz testing and fix all panic/oom/timeout ### Commits - [ ] My commits all reference Jira issues in their subject lines. In addition, my commits follow the guidelines from "[How to write a good git commit message](https://chris.beams.io/posts/git-commit/)": 1. Subject is separated from body by a blank line 1. Subject is limited to 50 characters (not including Jira issue reference) 1. Subject does not end with a period 1. Subject uses the imperative mood ("add", not "adding") 1. Body wraps at 72 characters 1. Body explains "what" and "why", not "how" ### Documentation - [x] In case of new functionality, my PR adds documentation that describes how to use it. - No new functionality -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
