Data Explorer (SEDE)

« first day (652 days earlier) ← previous day next day → last day (1680 days later) »

Feeds

04:32

Q: Why is the users who ended a bounty shown differently in SEDE and in the timeline and the revision history?

Recently I looked at situations where the PostNotices table shows a different OwnerUserId and DeletionUserId. This was based on Glorfindel's advice, who suggested this as a way to find bounties which were cancelled (refunded) by a moderator: When a bounty is returned by moderator, is this shown i...

Martin

04:42

@Glorfindel I have made a post on meta bout this: Why is the user who ended a bounty shown differently in SEDE and in the timeline and the revision history?

We'll see whether somebody will have some idea what is the reason for this behavior.

6 hours later…

Jeff Schaller

11:11

did the refresh break again? :(

most recent refresh in data.stackexchange.com/unix/query/848198/… is 2020-05-03 09:26:33, which matches data.stackexchange.com/unix/query/1232118

4 hours later…

Martin

15:16

Isn't it still in progress?

Sep 16 '18 at 8:10, by rene

but I still see a StackOverflow_Temp db so SEDE is still refreshing: https://data.stackexchange.com/mathoverflow/query/898673

Sep 16 '18 at 8:12, by rene

If you run that query ^ and the first databases is called [some name]_Temp then you know the refreshdatabase.sql script is still running.

1 hour later…

Jeff Schaller

16:46

@Martin yes; I'm just used to it being done earlier. Glad it's working!

1 hour later…

Feeds

18:08

Q: SEDE refresh seems to be stuck (again)

The weekly SEDE refresh doesn't seem to have completed successfully, just like two weeks ago; the Stack Overflow and Super User database are still a week old. If you look at the database timestamps, everything seems to have run smoothly up to 15:00 UTC when it was Super User's turn to be restored...