Check for duplicates immediately before creating issue #41
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
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.
Extra fix related to issue https://github.com/duckdblabs/duckdb-internal/issues/4206
Because workflow CI Fuzz runs multiple fuzz jobs in parallel, they can find and register the same issue, resulting in duplicates. This is because the querying of the current issues happens before the fuzzing. If the same issue is found by a parallel fuzz job and registered in this time gap, it is therefore not taken into account when checking for duplicates.
This PR solves that problem by querying for existing issues directly before the issue registered.
Some code clean-up/refactor has also been done.
Test issue created with the code of this PR: duckdb/duckdb-fuzzer#4082