8

As we all know, SEDE is refreshed every Sunday morning, but immediately after it finished (Stack Overflow is the last site, always somewhere before noon UTC), it seems to have triggered a new refresh cycle, as this query shows:

enter image description here

(Solana is the newest site and hence the first one to be refreshed).

This query just lists the creation date of the database, but I spot checked a few other things (e.g. what time was the most recent post created) and that's consistent.

While it's nice to have a continually refreshing SEDE, I doubt this is intentional, and it would require me and some others to rewrite a couple of cross-database queries to filter out the temporary databases we can't access.

Now that we're at Sunday evening (UTC), the refresh cycle seems to have triggered another time.

10
  • 4
    Oh that is fun: We now have two Temp databases: i.sstatic.net/yUQ0L.png ... So ... either a restore now goes twice as fast ... or restore tasks are spawning out of control. In the next run we have 4 temp databases ....
    – rene
    Commented Dec 4, 2022 at 13:40
  • 1
    Had to fix my status query as well: data.stackexchange.com/stackoverflow/query/1239509/… it didn't like having two temp databases.
    – rene
    Commented Dec 4, 2022 at 13:44
  • 2
    Things appear to go downhill since bluefeet left. Or more likely, that's why she couldn't stay in the first place. Commented Dec 4, 2022 at 13:57
  • 5
    @ShadowTheKidWizard I do miss bluefeet as well but I don't think it is fair to attribute the current problems to Taryn leaving the team. Aaron did promise to look into better error handling for failing SEDE tasks. I think this is a case where his automation couldn't handle success ....
    – rene
    Commented Dec 4, 2022 at 14:10
  • @rene nah, it's just nostalgic rant, Aaron is awesome. Commented Dec 4, 2022 at 14:32
  • 1
    Oops, it did it again! evidence: i.sstatic.net/OHUVJ.png
    – rene
    Commented Dec 4, 2022 at 20:18
  • 8
    When the refresh process doesn't run, you complain; so, it goes over the top and runs multiple times, and you still complain. I have to say, you're very hard to please, @Glorfindel :-P
    – 41686d6564
    Commented Dec 4, 2022 at 21:35
  • Looks like that without a status-review it's below SE radar. Commented Dec 8, 2022 at 9:05
  • @ShadowTheKidWizard at least it stopped refreshing later on Monday. Mabye it ends up as [status-norepro] ...
    – Glorfindel Mod
    Commented Dec 8, 2022 at 9:19
  • No-repro doesn't fit because it clearly happened. Ideally, they'd look into what happened, do something to prevent it in the future, and then it can get the good old status-completed. ;) Commented Dec 8, 2022 at 9:21

0

You must log in to answer this question.

Browse other questions tagged .