Skip to content

Fix NPE when generated fuzzer class is package-private #2005

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

Conversation

Markoutte
Copy link
Collaborator

Description

Fixes #2001

The NPE occurred for every type that is package-private. This fixes the problem by removing excess declaringClass call.

How to test

Automated tests

There's no implementation at the moment but there's a task to do it.

Manual tests

The example from the issued must work.

Self-check list

  • I've set the proper labels for my PR (at least, for category and component).
  • PR title and description are clear and intelligible.
  • I've added enough comments to my code, particularly in hard-to-understand areas.
  • The functionality I've repaired, changed or added is covered with automated tests.
  • Manual tests have been provided optionally.
  • The documentation for the functionality I've been working on is up-to-date.

@Markoutte Markoutte added comp-fuzzing Issue is related to the fuzzing ctg-bug-fix PR is fixing a bug labels Mar 22, 2023
@Vassiliy-Kudryashov Vassiliy-Kudryashov merged commit 6a8d6e3 into main Mar 23, 2023
@Vassiliy-Kudryashov Vassiliy-Kudryashov deleted the pelevin/2001_NPE_from_Fuzzing_providers_for_static_code_block branch March 23, 2023 08:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
comp-fuzzing Issue is related to the fuzzing ctg-bug-fix PR is fixing a bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

NPE from Fuzzing providers for static code block with File operations
2 participants