Greetings.
Today I went and ran pgimporter ( https://pagure.io/pagure-importer ) on the fedora-infrastructure trac tickets and then imported them into pagure.
Things went pretty smoothly until the import, when we found that even though the 'fedmsg' plugin was off for the main git repo, there's currently no way to disable it for the tickets or docs repos for a project. This meant that the import started sending out fedmsgs to everyone who interacted to fedora-infrastructure trac over the last 10 years or so. ;( We stopped things before too long and managed to wipe out the messages (Thanks patrick!). Sorry for any confusion with old messages.
We will want to sort this out before more projects migrate. There needs to be a way to supress these "rewind of the past" fedmsg storms. ;)
All that said, we are now migrated to pagure, so where you would file tickets before on fedorahosted, you should file issues on pagure.io/fedora-infrastructure.
I will be syncing up the git repo and readme and adding docs over the coming days.
kevin
Yep - I had a mild panic for a second.
How bad would it be if we set up a maintenance window and took the fedmsg gateway down for the migrations?
Sent from [Nylas N1](https://link.nylas.com/link/62fktrnw4nwag1kafi1t5vn3l /local-02a7a7ed-edca/0?redirect=https%3A%2F%2Fnylas.com%2Fn1%3Fref%3Dn1&r=aW5m cmFzdHJ1Y3R1cmVAbGlzdHMuZmVkb3JhcHJvamVjdC5vcmc=), the extensible, open source mail client.
On Sep 24 2016, at 9:52 pm, Kevin Fenzi kevin@scrye.com wrote:
Greetings.
Today I went and ran pgimporter ( https://pagure.io/pagure-importer )
on the fedora-infrastructure trac tickets and then imported them into pagure.
Things went pretty smoothly until the import, when we found that even
though the 'fedmsg' plugin was off for the main git repo, there's currently no way to disable it for the tickets or docs repos for a project. This meant that the import started sending out fedmsgs to everyone who interacted to fedora-infrastructure trac over the last 10 years or so. ;( We stopped things before too long and managed to wipe out the messages (Thanks patrick!). Sorry for any confusion with old messages.
We will want to sort this out before more projects migrate. There needs
to be a way to supress these "rewind of the past" fedmsg storms. ;)
All that said, we are now migrated to pagure, so where you would file
tickets before on fedorahosted, you should file issues on pagure.io/fedora-infrastructure.
I will be syncing up the git repo and readme and adding docs over the
coming days.
kevin
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org
On Sun, Sep 25, 2016 at 12:15 AM, Zach Villers zachvatwork@gmail.com wrote:
Yep - I had a mild panic for a second.
I equally had a mild second of panic when I was like "I'm at a baseball game, not commenting on tickets!" :). Then I saw the content and was like "wow, back to the future!!!!" :)
How bad would it be if we set up a maintenance window and took the fedmsg gateway down for the migrations?
Pretty bad, I think - because then real notifications wouldn't happen.
On Sun, 25 Sep 2016 00:25:55 -0400 Jon Stanley jonstanley@gmail.com wrote:
On Sun, Sep 25, 2016 at 12:15 AM, Zach Villers zachvatwork@gmail.com wrote:
Yep - I had a mild panic for a second.
I equally had a mild second of panic when I was like "I'm at a baseball game, not commenting on tickets!" :). Then I saw the content and was like "wow, back to the future!!!!" :)
Yeah, very sorry about all that. ;(
How bad would it be if we set up a maintenance window and took the fedmsg gateway down for the migrations?
Pretty bad, I think - because then real notifications wouldn't happen.
Right, and the messages would just queue up anyhow normally.
We need to get a way to turn off ticket fedmsgs just at import time.
I'm sure it's just a matter of coding. ;)
kevin
infrastructure@lists.fedoraproject.org
-
Jon Stanley -
Kevin Fenzi -
Zach Villers