Denise (
denise) wrote in
dw_maintenance2012-09-22 06:23 pm
![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
Code push tonight
A reminder to all that we will be doing a code push tonight. We'll be starting the prepwork in a few hours (around 6PM PDT/9PM EDT/1AM UTC), and the actual push itself will likely be an hour or two after that.
As I mentioned last time, this is a "higher risk" push. Sometimes we're only pushing frontend changes that have very little chance of causing site-wide problems, and any bugs we didn't catch in testing (because there are always bugs we don't catch in testing!) are only likely to be display bugs or the occasional weird error on a single page. This push has a lot of backend changes, though, and the differences between our production setup (the site itself) and our testing setup mean that there's a greater chance of things going a little wonky. (That's a technical term.)
So, there may be unexpected downtime as part of the push, and there may be weird site-wide errors after we come back up. We will be watching for them, and if they happen, we'll fix them as quickly as we can. Don't worry! We'll be on it.
As I mentioned last time, this is a "higher risk" push. Sometimes we're only pushing frontend changes that have very little chance of causing site-wide problems, and any bugs we didn't catch in testing (because there are always bugs we don't catch in testing!) are only likely to be display bugs or the occasional weird error on a single page. This push has a lot of backend changes, though, and the differences between our production setup (the site itself) and our testing setup mean that there's a greater chance of things going a little wonky. (That's a technical term.)
So, there may be unexpected downtime as part of the push, and there may be weird site-wide errors after we come back up. We will be watching for them, and if they happen, we'll fix them as quickly as we can. Don't worry! We'll be on it.
no subject
no subject
Hi, Denise, an error possibly related to code push...
Re: Hi, Denise, an error possibly related to code push...
Re: Hi, Denise, an error possibly related to code push...
Re: Hi, Denise, an error possibly related to code push...
Re: Hi, Denise, an error possibly related to code push...
Re: Hi, Denise, an error possibly related to code push...
Re: Hi, Denise, an error possibly related to code push...
Re: Hi, Denise, an error possibly related to code push...
Re: Hi, Denise, an error possibly related to code push...
Hmmmm.
(edit: shows up fine on my phone, too! maybe I'm onto something here with it being Win 7 at fault. I don't know if it's worth doing a System Restore to find out, but maybe if I get a lot of free time on my hands this week I'll give that a go, too.)
Re: Hi, Denise, an error possibly related to code push...
When viewed in my style, it breaks the background image, which doesn't resume until about midway through the post (screencap of resumption point: http://i.imgur.com/yZNfm.jpg) . HTML in question is here (2,691 errors, mostly
<wbr>
-related, mostly from the evil github post in question: http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fmarahmarie.dreamwidth.org%2Fread%3Fshow%3DC)Previous 20 on show=C displays background image perfectly even in Firefox so I'm going to presume this problem is solved and close my Support Request - and thanks for the input. :)
Re: Hi, Denise, an error possibly related to code push...
Re: Hi, Denise, an error possibly related to code push...
Re: Hi, Denise, an error possibly related to code push...
When viewed in my style, it breaks the background image, which doesn't resume until about midway through the post (screencap of resumption point: http://i.imgur.com/yZNfm.jpg) . HTML in question is here (2,691 errors, mostly
<wbr>
-related, mostly from the evil github post in question: http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fmarahmarie.dreamwidth.org%2Fread%3Fshow%3DC)Previous 20 on show=C displays background image perfectly even in Firefox so I'm going to presume this problem is solved and close my Support Request - and thanks for the input. :)
no subject
no subject