-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Issue incorrectly marked as fixed #12682
Comments
@oliverchang @DavidKorczynski Sorry for the ping, but I do need help with this. I'm worried the detailed report will become public with some time and that must not happen. If you can also please add an extension for disclosure (e.g. from Jan 8 to Jan 22), I would appreciate it. |
Thanks @micahsnyder -- did you verify the bug still reproduces with the reproducer from OSS-Fuzz? I'm curious why it's marked fixed |
We can switch communication to the bug tracker, which may be nicer |
Done |
@jonathanmetzman can you please also extend the disclosure date by 14 days? We have a product integration team that has asked us for additional time in order to include the fix in a maintenance release for their users. |
@jonathanmetzman @DavidKorczynski the issue marked itself as fixed/open again just 10 minutes ago. 😕 |
Sorry for the mistake. It was due to my unfamiliarity with the new bug tracker. |
I've added the 14 extension |
Oh no it happened again. |
@jonathanmetzman I hate to pester, but it didn't seem to stick |
Apologies, we've re-restricted the issue. |
https://issues.oss-fuzz.com/issues/372544101 has been incorrectly marked as fixed. Please help.
The text was updated successfully, but these errors were encountered: