[Twisted-Python] Trac downtime
Hello Twisted users, David Reid and I are attempting to upgrade our production Trac instance to version 1.0.1 today, in order to address the spam and many other issues. While we will attempt to minimize the downtime, knowing Trac, you should expect at least 6 hours of downtime beginning as soon as 20 minutes (18:00 UTC). -glyph
On 05:38 pm, glyph@twistedmatrix.com wrote:
Hello Twisted users,
David Reid and I are attempting to upgrade our production Trac instance to version 1.0.1 today, in order to address the spam and many other issues.
While we will attempt to minimize the downtime, knowing Trac, you should expect at least 6 hours of downtime beginning as soon as 20 minutes (18:00 UTC).
Looks like some cool stuff happened. Thanks! I'm not sure if you're done or not. In case not, here are some things I noticed: The front page says "wiki:WikiStart" at the top of the wiki content. Other pages similarly have their own name at the top as well. The tabs on "Code Examples" on the front page don't work (clicking them doesn't switch to a different example) The "Owner" dropdown list on the ticket page is quite short. This is rather nice, but it is maybe slightly too short. :) The IDs for entries in the various RSS feeds have changed (so the last N entries appear as duplicates). Again, thanks! Jean-Paul
On Jun 19, 2014, at 4:31 PM, exarkun@twistedmatrix.com wrote:
On 05:38 pm, glyph@twistedmatrix.com wrote:
Hello Twisted users,
David Reid and I are attempting to upgrade our production Trac instance to version 1.0.1 today, in order to address the spam and many other issues.
While we will attempt to minimize the downtime, knowing Trac, you should expect at least 6 hours of downtime beginning as soon as 20 minutes (18:00 UTC).
Looks like some cool stuff happened. Thanks!
You're welcome. This was really like 99% David, I just helped push things towards a conclusion ;).
I'm not sure if you're done or not. In case not, here are some things I noticed:
Sorry I didn't send out an announcement when we were finished. It was all pretty exhausting :-).
The front page says "wiki:WikiStart" at the top of the wiki content. Other pages similarly have their own name at the top as well.
This is a new feature of Trac 1.0, a breadcrumbs bar, which we don't have nice styling for yet. We should probably add some CSS for it. (Notice "wiki" is a link to WikiStart from all pages.)
The tabs on "Code Examples" on the front page don't work (clicking them doesn't switch to a different example)
I imagine you have an adblocker or a tracking-blocker or something like that. The tabs actually work fine, unless you block google analytics, which causes a JavaScript which I believe halts further script execution on the page. We should add a try/catch around the thing that loads the analytics thing so it doesn't disrupt further script execution.
The "Owner" dropdown list on the ticket page is quite short. This is rather nice, but it is maybe slightly too short. :)
Augh. That definitely looks too short. I have no idea why it looks that way. I don't think it looked that way when I examined dreid's test instance. Any ideas?
The IDs for entries in the various RSS feeds have changed (so the last N entries appear as duplicates).
I don't think there's anything we can do about that.
Again, thanks!
Thanks for looking into it. Now that we're over this huge hurdle, hopefully we can address issues like these more quickly now. One thing you didn't notice is the weird description on the styling in the "Description" box in the ticket-edit area, we should fix that as well. -glyph
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Can you install pytz on the trac instance as well, it improves the options on the https://twistedmatrix.com/trac/prefs/datetime page. Cheers, Thijs On 19-06-14 19:38, Glyph Lefkowitz wrote:
Hello Twisted users,
David Reid and I are attempting to upgrade our production Trac instance to version 1.0.1 today, in order to address the spam and many other issues.
While we will attempt to minimize the downtime, knowing Trac, you should expect at least 6 hours of downtime beginning as soon as 20 minutes (18:00 UTC).
-glyph
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) iEYEARECAAYFAlOjeo0ACgkQBRbMGagbo3n0AACfYqoD+BRkbCEVVw0XJ/iUtMdK AeQAn2f0XyM8EV4RAXmr7SKMqVm94IZr =4Np4 -----END PGP SIGNATURE-----
On Jun 19, 2014, at 5:04 PM, Thijs Triemstra <lists@collab.nl> wrote:
Can you install pytz on the trac instance as well, it improves the options on the https://twistedmatrix.com/trac/prefs/datetime page.
Would you mind submitting this as a pull request to <https://github.com/twisted-infra/trac-config>? -glyph
Hi, The web server version string says Twisted 11.1 — maybe we should upgrade that too? :) -hawkowl On 20 Jun 2014, at 1:38, Glyph Lefkowitz <glyph@twistedmatrix.com> wrote:
Hello Twisted users,
David Reid and I are attempting to upgrade our production Trac instance to version 1.0.1 today, in order to address the spam and many other issues.
While we will attempt to minimize the downtime, knowing Trac, you should expect at least 6 hours of downtime beginning as soon as 20 minutes (18:00 UTC).
-glyph
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
I was going to do that, but I do not understand where it is in braid :( - hawkowl On 21 Jun 2014, at 8:43, Glyph <glyph@twistedmatrix.com> wrote:
On Jun 20, 2014, at 2:40 AM, HawkOwl <hawkowl@atleastfornow.net> wrote:
Hi,
The web server version string says Twisted 11.1 — maybe we should upgrade that too? :)
Sounds like somebody should send a PR to Braid? :-)
-glyph _______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
On Jun 20, 2014, at 10:10 PM, HawkOwl <hawkowl@atleastfornow.net> wrote:
On 21 Jun 2014, at 8:43, Glyph <glyph@twistedmatrix.com> wrote:
On Jun 20, 2014, at 2:40 AM, HawkOwl <hawkowl@atleastfornow.net> wrote:
The web server version string says Twisted 11.1 — maybe we should upgrade that too? :)
Sounds like somebody should send a PR to Braid? :-)
I was going to do that, but I do not understand where it is in braid :(
(Note: On this mailing list, please don't top-post, we prefer a trimmed and interleaved reply; it's easier to follow discussions if you show up in the middle.) It looks like the relevant place is in braid.twisted.service.Service.bootstrap... although really, we ought to be using virtualenvs for this stuff, so I don't know how deep you want to go into refactoring :-). Or perhaps you could just make <https://github.com/twisted-infra/braid/blob/master/braid/pip.py> always do a pip install --upgrade, if we're always going for a recent version, or add support for pinning versions of things. -glyph
On 22 Jun 2014, at 11:54, Glyph <glyph@twistedmatrix.com> wrote:
On Jun 20, 2014, at 10:10 PM, HawkOwl <hawkowl@atleastfornow.net> wrote:
On 21 Jun 2014, at 8:43, Glyph <glyph@twistedmatrix.com> wrote:
On Jun 20, 2014, at 2:40 AM, HawkOwl <hawkowl@atleastfornow.net> wrote:
The web server version string says Twisted 11.1 — maybe we should upgrade that too? :)
Sounds like somebody should send a PR to Braid? :-)
I was going to do that, but I do not understand where it is in braid :(
(Note: On this mailing list, please don't top-post, we prefer a trimmed and interleaved reply; it's easier to follow discussions if you show up in the middle.)
Right. I was just hitting reply and typing words in mail.app :D
It looks like the relevant place is in braid.twisted.service.Service.bootstrap... although really, we ought to be using virtualenvs for this stuff, so I don't know how deep you want to go into refactoring :-).
Or perhaps you could just make <https://github.com/twisted-infra/braid/blob/master/braid/pip.py> always do a pip install --upgrade, if we're always going for a recent version, or add support for pinning versions of things.
When I get a moment, I’ll have a look at all this. Moving parts :(
-glyph
-hawkowl
On Jun 23, 2014, at 3:49 AM, Itamar Turner-Trauring <itamar@itamarst.org> wrote:
Can we re-enable general commenting now? Or is the spam setup still in progress?
Currently no spam setup is in progress. In a sense, the Trac upgrade is orthogonal to the spam problem. Upgrading Trac didn't change anything about the spam. However, the Trac upgrade provides access to a lot more Trac plugins, including more recent authentication and registration and signup and spam filtering plugins, so there are many more options now available. If someone wanted to tackle this problem we now have a path forward for them to do so, without having to deal with the mess of a Trac schema upgrade :). -glyph
On 19 June 2014 18:38, Glyph Lefkowitz <glyph@twistedmatrix.com> wrote:
Hello Twisted users, David Reid and I are attempting to upgrade our production Trac instance to version 1.0.1 today, in order to address the spam and many other issues. While we will attempt to minimize the downtime, knowing Trac, you should expect at least 6 hours of downtime beginning as soon as 20 minutes (18:00 UTC).
Thanks David and Glyph. A few bugs I noticed since the trac upgrade: * I don't think I'm receiving ticket modification updates (for tickets where I've participated). For example I didn't receive an email about this comment from JP https://twistedmatrix.com/trac/ticket/7527#comment:1 * There's an extra "delete" link alongside the ticket delete button when I view existing tickets * The new ticket description textarea floats to the right of the text "You may use WikiFormatting here." instead of above it. -RichardW.
On Jun 23, 2014, at 3:59 AM, Richard Wall <m-lists@the-moon.net> wrote:
On 19 June 2014 18:38, Glyph Lefkowitz <glyph@twistedmatrix.com> wrote:
Hello Twisted users, David Reid and I are attempting to upgrade our production Trac instance to version 1.0.1 today, in order to address the spam and many other issues. While we will attempt to minimize the downtime, knowing Trac, you should expect at least 6 hours of downtime beginning as soon as 20 minutes (18:00 UTC).
Thanks David and Glyph.
A few bugs I noticed since the trac upgrade:
Hi Richard, Thanks for noting these, but I think they're likely to disappear into the ether :-). Would you mind filing these as issues against Braid? -glyph
participants (7)
-
exarkun@twistedmatrix.com
-
Glyph
-
Glyph Lefkowitz
-
HawkOwl
-
Itamar Turner-Trauring
-
Richard Wall
-
Thijs Triemstra