51

When I goto https://engineering.meta.stackexchange.com/ and click on any of the links for a question, I get the oops page. So, per the page's request, I'm reporting it here.

It's not just that question. It's every question on that site, and also on many other sites.

3
  • 16
    Purging the comments here since we've established that it's happening on all sites sporadically for different users.
    – animuson StaffMod
    Commented Mar 28, 2016 at 16:46
  • 3
    twitter.com/Nick_Craver/status/714494616821702656 Commented Mar 28, 2016 at 16:51
  • 27
    This was our fault. We noticed that our error pages got appreciably fewer views than everything else, and asked engineering to break everything in order to fix that.
    – user50049
    Commented Mar 28, 2016 at 16:54

2 Answers 2

29

This was a bug in pathing that should never be allowed to bring down question pages anyway - a fix has been deployed and I'll be preventing that code from causing such drastic issues ever again in my next commit.

4
  • 11
    By 'ever again', he means 'ever, ever, ever, ever ever ever again. Finality is this man's specialty.
    – user50049
    Commented Mar 28, 2016 at 17:04
  • Admit it Nick, you missed hitting the rep cap here on MSE. :-D Commented Mar 28, 2016 at 18:04
  • Perhaps this is more of a post-mortem question (haven't had one of those in a while ;)) but why didn't this error show up in dev?
    – hichris123
    Commented Mar 28, 2016 at 19:26
  • 1
    @hichris123 details in the post-mortem at stackstatus.tumblr.com/post/141859797844/…
    – Greg Bray Staff
    Commented Mar 30, 2016 at 3:36
13

According to the @StackStatus Twitter, a new build is being rolled out that corrects this issue:

https://twitter.com/StackStatus/status/714495272127082496

enter image description here

2
  • 4
    It's usually better to let the developers and/or community managers comment on what happened (given they're the ones that fix it...)
    – Quill
    Commented Mar 28, 2016 at 17:02
  • 1
    @Quill I agree. Which is why I only posted from an official source and didn't just write an answer like, "It seems to be fixed now". Commented Mar 28, 2016 at 18:40

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .