I just now was reading this question - "the-loop-has-arrived-what-does-the-community-think-about-it", then I refreshed the page and it was a 404. What happened to it? Was this question deleted? And if yes, why?

Edit: also another question that might have suffered similar symptom joel-left-se-as-we-know-it-is-dead, as pointed out in comments.

  • 3
    seems to be happening to lot of meta posts in SO and SE at least – Lamak Nov 25 '19 at 20:56
  • I added a bug tag to it. – wha7ever Nov 25 '19 at 20:57
  • 3
    We broke SE. Let's face it. – Frédéric Hamidi Nov 25 '19 at 20:57
  • 1
    Same goes for my question: meta.stackexchange.com/questions/339074/… – Luuklag Nov 25 '19 at 20:57
  • 4
    I'm getting "Oops, something bad happened" errors on most Meta questions. I'm surprised this one opened. – user56reinstatemonica8 Nov 25 '19 at 20:57
  • 17
    We're investigating an issue with a build. – Taryn Nov 25 '19 at 20:58
  • 2
    @Taryn so it's a bug? – dfhwze Nov 25 '19 at 20:58
  • 7
    It's a good thing staff is still reading Meta – Scott Seidman Nov 25 '19 at 20:59
  • 1
    We're investigating an issue with a build....it shouldn't have released YET. – Alex Nov 25 '19 at 21:02
  • 1
    Is the survey still up? – dfhwze Nov 25 '19 at 21:02
  • 1
    As far as I can tell, this affects most meta questions - it's not selective to any one type of question or level of question popularity. – isaacg Nov 25 '19 at 21:02
  • @Alex, I won't repost this, but I very much think it. – Frédéric Hamidi Nov 25 '19 at 21:03
  • 11
    A build went out to meta that had an unexpected null in certain circumstances. We have a fix and it's building out now. – Dean Ward Nov 25 '19 at 21:04
  • 9
    @Luuklag but... it's Monday. Or maybe I slept through the week again? – Dean Ward Nov 25 '19 at 21:10
  • 7
    It's not about any particular question. Just had some ten minutes of being unable to access any questions on Meta Stack Exchange. Tested it, it's not just the "we're unhappy with some things" ones. – Galastel supports GoFundMonica Nov 25 '19 at 21:13

This one's on me! The bug is fixed and all built out.

The tl;dr is that an array passed into a Razor view that should never be null™ turned out to be null (surprise!). We've fixed the code to handle future unexpected nulls and also fixed the source of this null.

Sorry to those of you who've had your day adversely impacted by this!

| improve this answer | |
  • 10
    Things happen. Thank you very much for feedback! – wha7ever Nov 25 '19 at 21:39

Comment from @DeanWard:

A build went out to meta that had an unexpected null in certain circumstances. We have a fix and it's building out now.

| improve this answer | |

You were linking to the error page, with “errorpath” in the URL. Here is the original: The "loop" has arrived, what does the community think about it?

It worked for me on my iPhone a minute ago.

enter image description here

| improve this answer | |
  • 2
    That link does not currently work for me. I'm on Firefox on Ubuntu Linux – isaacg Nov 25 '19 at 21:04

You must log in to answer this question.

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