10

Last week's SEDE update left out poor Stack Overflow. And it did it again this week.

This SO query only returns results up to 8/25/2015, while it seems for every other site it correctly returns results up to 8/30/2015.

Improve this question
11
  • 1
    Why the help page says "The data is updated early every Monday morning around 3:00 UTC" – HackerKarma Aug 30 '15 at 11:38
  • 1
    @HackerKarma: the help page is notoriously out of date; it has been updating on Sundays for ages now. – Martijn Pieters Sep 3 '15 at 21:43
  • @MartijnPieters May be I should make a fea-req then – HackerKarma Sep 3 '15 at 21:45
  • @HackerKarma: SEDE FAQ - small discrepancy - update day – Martijn Pieters Sep 3 '15 at 21:48
  • @MartijnPieters thanks for the link... avoided one dupe. – HackerKarma Sep 3 '15 at 21:49
  • @HackerKarma: and read rene's answer carefully. :-) – Martijn Pieters Sep 3 '15 at 21:50
  • 1
    @Geoff by removing the bug tag it means you won't be fixing it? (i.e. it might be long weeks befoe SEDE is updated again for SO), or did I miss something? – Shadow Wizard is Vaccinating Sep 3 '15 at 22:10
  • 1
    No, it's not a bug. We will be switching back to NY here this evening and have our primary server available for SEDE which will fix this issue. – Geoff Dalgas Sep 3 '15 at 22:16
  • @Geoff why all the switching between locations? Is this explained somewhere? (just curious :)) – Shadow Wizard is Vaccinating Sep 3 '15 at 22:32
  • stackstatus.net is where we post most of our updates. We are also making sure that both data centers are ready to roll in the event of a natural disaster. There's no better way than by actually running our sites in the backup location for awhile. – Geoff Dalgas Sep 3 '15 at 22:36
  • Also: twitter.com/StackStatus is a good place to find updates. – Geoff Dalgas Sep 3 '15 at 22:37
10

Let me answer on behalf of Nick Craver:

Though we'll be a little rocky making this time until we're back in New York - it's when it should happen!

For the curious:
We have a kerberos pass-through auth issue that's ~ 60% likely to fail in the refresh for complicated reasons. Ultimately we need to restart the Colorado SQL servers to use the correct SPNs for Kerberos...and we don't want to do that while they're live for hopefully obvious reasons :)

This was left as a comment on my pull request to fix the day mentioned in the FAQ: Change the FAQ to mention Sunday as the update date

Improve this answer
4
  • +1 rene == SQL. You must have some kinda 'alert' system for SQL related questions. – HackerKarma Aug 30 '15 at 11:45
  • @HackerKarma not in the top 3 all-time yet... – rene Aug 30 '15 at 11:51
  • No worry... you will get there soon. Also, if I exclude SE team then you're a topper in the all-time list. – HackerKarma Aug 30 '15 at 11:57
  • 2
    @HackerKarma Tim Stone isn't part of SE team and never was. :) – Shadow Wizard is Vaccinating Aug 30 '15 at 13:15

You must log in to answer this question.

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