Reported issues are hidden in the new issue tracker

[maflcko]

Steps to reproduce:

• Go to testcase-detail without issue. For example https://oss-fuzz.com/testcase-detail/6582005385461760 didn't have an issue reported.
• Click on "Create an issue" and select "[x] CC me on the issue?"
• Open the issue and get "Access is denied to this issue", even after log-in. The URL would be https://issues.oss-fuzz.com/u/3/issues/369374541 (u3 for me)

[maflcko]

Cross-ref to #12508

[jonathanmetzman]

Since youre already looking into the issue tracker, can you take a look at this when you get a chance Vitor?

[vitorguidi]

@jonathanmetzman is this flow related somehow to oss-fuzz-apply-ccs? It is another cron that is broken

[maflcko]

I think it should not be related to adding new CC's, but I haven't confirmed. For reference, I did receive the email itself normally:

Email:

Replying to this email means your email address will be shared with the team that works on this product.
https://issues.oss-fuzz.com/issues/369374541

Reference Info: 369374541 bitcoin-core:scriptpubkeyman: Timeout in scriptpubkeyman
component:  [Public Trackers > 1362134 > OSS Fuzz](https://issues.oss-fuzz.com/components/1638179)
status:  New
reporter:  ...uxuga@aleeas.com
cc:  [ac...@gmail.com](mailto:ac...@gmail.com), [fa...@gmail.com](mailto:fa...@gmail.com), [jo...@chaincode.com](mailto:jo...@chaincode.com), and 3 more
collaborators:  [co...@oss-fuzz.com](mailto:co...@oss-fuzz.com)
type:  Bug
access level:  Limited visibility
priority:  P2
severity:  S4
hotlist:  [Unreproducible](https://issues.oss-fuzz.com/hotlists/6183475)
retention:  Component default
Project:  bitcoin-core
Reported:  Sep 25, 2024

...

[vitorguidi]

There are two tickets from bitcoin-core that got automatically deleted, I am looking into it to know what triggered, probably some false positive in our automations. This does not seem like a widespread problem.

[vitorguidi]

I undeleted these two bugs, please let me know if you can now access them. If no further concern besides these two issues is raised, I will close the issue.

[maflcko]

Thanks. I'll reopen this issue if it happens again.