8000 fix: fuzzer repeat issue tracking by joseph-isaacs · Pull Request #6577 · vortex-data/vortex · GitHub
[go: up one dir, main page]

Skip to content

fix: fuzzer repeat issue tracking#6577

Merged
joseph-isaacs merged 3 commits intodevelopfrom
ji/fixup-fuzzer-seen
Feb 19, 2026
Merged

fix: fuzzer repeat issue tracking#6577
joseph-isaacs merged 3 commits intodevelopfrom
ji/fixup-fuzzer-seen

Conversation

@joseph-isaacs
Copy link
Contributor
@joseph-isaacs joseph-isaacs commented Feb 18, 2026

Fixes the fuzzer comment dedup so that when a fuzzer find the same bug multiple times it increments the seen count.

Tested by running

u
Signed-off-by: Joe Isaacs <joe.isaacs@live.co.uk>
@joseph-isaacs joseph-isaacs changed the title u fix: fuzzer repeat issue tracking Feb 18, 2026
@joseph-isaacs joseph-isaacs added the changelog/fix A bug fix label Feb 18, 2026
u
Signed-off-by: Joe Isaacs <joe.isaacs@live.co.uk>
u
Signed-off-by: Joe Isaacs <joe.isaacs@live.co.uk>
@joseph-isaacs joseph-isaacs marked this pull request as ready for review February 18, 2026 15:37
@joseph-isaacs joseph-isaacs enabled auto-merge (squash) February 18, 2026 15:38
@joseph-isaacs joseph-isaacs merged commit 9aa98d1 into develop Feb 19, 2026
50 checks passed
@joseph-isaacs joseph-isaacs deleted the ji/fixup-fuzzer-seen branch February 19, 2026 11:13
fastio pushed a commit to fastio/vortex that referenced this pull request Mar 10, 2026
<!--
Thank you for submitting a pull request! We appreciate your time and
effort.

Please make sure to provide enough information so that we can review
your pull
request. The Summary and Testing sections below contain guidance on what
to
include.
-->

## Summary

<!--
If this PR is related to a tracked effort, please link to the relevant
issue
here (e.g., `Closes: vortex-data#123`). Otherwise, feel free to ignore / delete
this.

In this section, please:

1. Explain the rationale for this change.
2. Summarize the changes included in this PR.

A general rule of thumb is that larger PRs should have larger summaries.
If
there are a lot of changes, please help us review the code by explaining
what
was changed and why.

If there is an issue or discussion attached, there is no need to
duplicate all
the details, but clarity is always preferred over brevity.
-->

Close
79D5
s: #000

<!--
## API Changes

Uncomment this section if there are any user-facing changes.

Consider whether the change affects users in one of the following ways:

1. Breaks public APIs in some way.
2. Changes the underlying behavior of one of the engine integrations.
3. Should some documentation be updated to reflect this change?

If a public API is changed in a breaking manner, make sure to add the
appropriate label. You can run `./scripts/public-api.sh` locally to see
if there
are any public API changes (and this also runs in our CI).
-->

## Testing

<!--
Please describe how this change was tested. Here are some common
categories for
testing in Vortex:

1. Verifying existing behavior is maintained.
2. Verifying new behavior and functionality works correctly.
3. Serialization compatibility (backwards and forwards) should be
maintained or
   explicitly broken.
-->

---------

Signed-off-by: Joe Isaacs <joe.isaacs@live.co.uk>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog/fix A bug fix

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

0