google
Issue tracker migration
OSS-Fuzz will be changing issue trackers later this week (we must do this and do not have a choice). We expect to do this on Thursday, September 19th. Existing issue links will be redirected to the new issue tracker. We will send out more details in an email to everyone in auto_ccs, vendor_ccs and primary_contacts later this week. There will be some downtime (probably around 8 hours). The issue tracker will be similar to chrome's new issue tracker: https://issues.chromium.org/
We're still in the process of migrating, this will continue until Monday, at least. Sorry for the email flood to those it affected.
Where should issues with the new tracker be reported ? (iam asking because previously i was able to add people to the CC list for FFmpeg and iam not sure how to do this now, it sometimes is usefull when issues are found in external libs or to add a specific maintainer for a component)
Where should issues with the new tracker be reported ? (iam asking because previously i was able to add people to the CC list for FFmpeg and iam not sure how to do this now, it sometimes is usefull when issues are found in external libs or to add a specific maintainer for a component)
I think here (on this issue tracker) is fine. I'll see about that capability as I learn how to use the new tracker.
Regarding the migration, it appears issues marked "publically visible" by bots are still restricted. e.g. bug
Regarding the migration, it appears issues marked "publically visible" by bots are still restricted. e.g. bug
We're looking in to this.
Btw, it seems the mail addresses, to which changes where CCed have changed (decreased). Previously almost all mails where sent to teh auto-cc and primary address but now it seems iam only receiving most on a single address.
Btw, it seems the mail addresses, to which changes where CCed have changed (decreased). Previously almost all mails where sent to teh auto-cc and primary address but now it seems iam only receiving most on a single address.
Is this something your other collaborators noticed or just you? I noticed something about your account (it was treating your two emails as the same) and was told it was an internal implementation detail and there's nothing that can be done
Btw, it seems the mail addresses, to which changes where CCed have changed (decreased). Previously almost all mails where sent to teh auto-cc and primary address but now it seems iam only receiving most on a single address.
Is this something your other collaborators noticed or just you? I noticed something about your account (it was treating your two emails as the same) and was told it was an internal implementation detail and there's nothing that can be done
I think iam the only one from FFmpeg looking at the issues regularly. The reason why I subscribed with 2 addresses was that sometimes mails disappeared in the past (probably spam filtering at the mail server outside my easy control).
Still the primary address (ffmpeg-security) seems to have received fewer mails than the one working auto-cc. ffmpeg-security here has 13 mails, my niedermayer.cc address has 1163 mails from buganizer. While in the past it seemed all mails went to all listed addresses. Note, iam not asking for the 1000+ automated mails to be sent to ffmpeg-security, i just want to point out that their absence is unexpected
Looks like sound-open-firmware's build started failing sometime around the migration but no bug was filed, at least not one that is open. Not sure if its a one off or a reporting bug.
I don't know if this is related to the migration or not, but automation keeps updating the Reported dates on issues in nonsensical ways. For example: https://issues.oss-fuzz.com/issues/42477631
I don't know if this is related to the migration or not, but automation keeps updating the Reported dates on issues in nonsensical ways. For example: https://issues.oss-fuzz.com/issues/42477631
Thanks for the report @alex. Looking into this.
Found a new bug with the migration, it appears like new/modified CCs added to the yaml file are not being reflected in the cc list for the actual issues so new members are not getting access.
Thanks for all the feedback! @vitorguidi is working on addressing some of the issues we've been encountering with CCs. The new issue tracker has some limitations around what emails can be CC'ed, which has been challenging to address.