Just to keep the following in mind: Full access to bug reports and
reproducers requires a Google account (which can be associated with
any existing non-list email address). At least the moderators of the
list would therefore have to be listed explicitly in the project's
YAML file [1] in the OSS-Fuz
On Wed, 14 Apr 2021 at 16:56, Gavin McDonald wrote:
>
> Hi Commons devs.
>
> As you know, the CMS is going away, we have been on hardware that could fail
> at any time, and this really has been dragging on longer than anticipated.
> So, we are accelerating the removal of any CMS related content.
For what it's worth, commons-geometry just added IO functionality so I would be
interested in fuzzing for that as well. I do not have a preference on the email
list question.
Regards,
Matt J
From: Fabian Meumertzheim
Sent: Wednesday, April 14, 2021 12:13 PM
To:
On Wed, Apr 14, 2021, 17:14 Matt Sicker wrote:
> Would the undeclared runtime exceptions be "fixable" for the fuzzing
> tool if the methods declared their runtime exceptions being thrown? Or
> the javadocs? As in, this tool is looking for exceptional conditions
> that don't appear to be intention
Hi Commons devs.
As you know, the CMS is going away, we have been on hardware that could fail at
any time, and this really has been dragging on longer than anticipated. So, we
are accelerating the removal of any CMS related content.
Previously you indicated that the project was no longer using
Would the undeclared runtime exceptions be "fixable" for the fuzzing
tool if the methods declared their runtime exceptions being thrown? Or
the javadocs? As in, this tool is looking for exceptional conditions
that don't appear to be intentional?
I've briefly looked at OSS-Fuzz, and it certainly lo
