Fix Oss Fuzz Build Error #574
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks! |
|
Thanks so much for the PR! That would be awesome. What role on that link did you have in mind? On Oct 29, 2023, at 4:48 AM, Nicco Kunzmann ***@***.***> wrote:
Thanks!
Would you like to become a developer of icalendar? https://icalendar.readthedocs.io/en/latest/maintenance.html
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
I thought either "contributor" or "maintainer" - what would you like to step up to? |
|
Contributor would be great! Thank you Nicco! :)
On Tuesday, October 31, 2023 at 07:33:45 PM EDT, Nicco Kunzmann ***@***.***> wrote:
I thought either "contributor" or "maintainer" - what would you like to step up to?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Can I add your email to the auto-cc's so that you are copied on bug reports and fuzzing updates? Or is there a better one to add?
On Wednesday, November 1, 2023 at 01:31:31 PM EDT, McKenna Dallmeyer ***@***.***> wrote:
Contributor would be great! Thank you Nicco! :)
On Tuesday, October 31, 2023 at 07:33:45 PM EDT, Nicco Kunzmann ***@***.***> wrote:
I thought either "contributor" or "maintainer" - what would you like to step up to?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Maybe, one could add a github discussion. I am replying to this from another email address. If this is visible, one can add a new github discussion.
One thing that needs spreading in knowledge is how to deal with the tests failing and what it means.
|
|
Well I need an email to add to the project.yaml hosted on OSS-Fuzz. Found here: https://github.com/ennamarie19/oss-fuzz/blob/master/projects/icalendar/project.yamlI have an email of a past maintainer on there currently and he asked to be removed. I can definitely explain that. On Nov 2, 2023, at 5:10 AM, Nicco Kunzmann ***@***.***> wrote:
Maybe, one could add a github discussion. I am replying to this from another email address. If this is visible, one can add a new github discussion.
One thing that needs spreading in knowledge is how to deal with the tests failing and what it means.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Hi, you could start a new discussion here:
https://github.com/collective/icalendar/discussions/new?category=general
I will get an email and tell you the email address to add.
|
|
This is live in v5.0.11. Thanks for your contributions! |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm currently working on switching the OSS Fuzz build to use the fuzzing harnesses hosted in icalendar. In doing that, I noticed that this change required updating the find path in the build.sh script. I tested it locally and the fuzz harnesses are able to build.