[07:33] good morning [10:28] dpm, dholbach, heads-up, the Community page on d.u.c is dead (https://developer.ubuntu.com/community/) for en and zh-cn. Could be the result of changes made to the zh-cn version today but... Django, you are not supposed to do this! [10:28] You can view it in edit mode, but it's not publishable anymore as well. [10:29] davidcalle, argh. Does the history tell anything? [10:29] it'd be interesting to see the error message [10:29] it says "... will be notified" [10:29] "we have been notified" [10:31] dpm: revision log is in chinese, but nothing odd looking there, regular edits, I've been actually pinged by Liam who is doing these modifications and discovered the issue. I assume the page was working before he started working on it. [10:31] dholbach: I'm asking logs [10:31] "we have been notified, somehow" [10:34] ok [10:46] dpm: dholbach: rt filed #89693 with a request for logs and further assistance if needed. [10:46] And conversations started in #webops [10:47] *Monday* :) [10:47] thanks davidcalle [10:50] * dholbach hugs davidcalle [14:36] dpm: dholbach mhall119 , re: community pages (Mike, see log ^), the error is "DoesNotExist: Page has no publisher_draft". Have you already seen this? In any case, for starters, I'll back up the content to a new page and see if I can change the path of the broken one. [14:36] wow [14:36] how did the db get that inconsistent? [14:36] every page should have a draft page as well [14:37] dholbach: no idea, as far as I can tell, the issue appeared when Liam was updating the zh-cn version. [14:38] I guess we can't run "./manage.py shell" on the machine? :) [14:38] dholbach: even if we could, I would be worried about running any command :D [14:39] hm [15:38] On d.u.c switching for the last hour betwen en, zh-cn, live, draft, and guessing if I'm seeing an old server cached version or not is a trippy experience, anyway, fixed! [15:38] dpm: dholbach: mhall119 ^ [15:39] \o/ [15:39] wow... so you "just" played around with the site and after a short trip it was fixed? [15:39] any idea what broke it in the first place? [15:42] dholbach: mhall119: no i actually recreated the community sections for en and zh-cn, renamed the existing community path to community-old and the new one community. The error was appearing on the new pages as well! It disappeared when I actually deleted "community-old". [15:43] great work! [15:43] There is still some cache of the mess on the site, so if you visit and see weird things, make sure you reload a couple times. [15:44] mhall119: nope. Liam did nothing out of the ordinary. I can only assume the db went corrupted when saving an update. [15:45] :/ [15:45] hopefully the upgrades in the pipeline will make that happen less easily [15:45] how's the migration testing going? [15:47] mhall119: not tried on the server because of ^ and showdown judges coordination. I'm starting on it now. [15:51] davidcalle: ok, if we can get this rolling out into production this week I'd be very happy, I keep getting pinged about the API docs being wrong [15:52] mhall119, does that mean you want trunk + the current MPs landed? [15:54] dholbach: I'd like to at least get current staging branch into production [15:54] hum [15:54] what's in staging then? [15:54] the django upgrade [15:55] but your api branch is not on there or is it? [15:55] once that's gone into production, we can do smaller, more frequent updates for all the current MPs [15:56] dholbach: no, but that will be easy to land once the big upgrade is done [15:56] ok