Timeline for Improvements to 'Data updated x hours/days ago' message in SEDE
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Sep 16, 2020 at 15:21 | history | bounty ended | 202324 | ||
| S Sep 16, 2020 at 15:21 | history | notice removed | 202324 | ||
| S Sep 15, 2020 at 14:25 | history | bounty started | 202324 | ||
| S Sep 15, 2020 at 14:25 | history | notice added | 202324 | Reward existing answer | |
| Sep 12, 2020 at 15:40 | answer | added | rene | timeline score: 3 | |
| Sep 4, 2018 at 14:52 | comment | added | Taryn | @rene It looks like that's the current version being used. | |
| Sep 4, 2018 at 14:42 | comment | added | rene | @Taryn Is the sp_refreshDatabase.sql updated and if it is would it be possible to share that newer version? I find myself trying to guess what is in the black-box and I realize it is easier if I know which scripts run and what they touch in SEDE so I can make a better judgement call on what is going on and on which end the work needs to be done to have the simplest solution that might work. | |
| Sep 4, 2018 at 14:21 | comment | added | rene | It is clear that our multi-db scripts need to handle the existence of these _temp db's nicely. | |
| Sep 4, 2018 at 14:19 | comment | added | rene |
@Taryn I don't think you can or you have to move the update of that LastPost field for all sites (databases) to the end of the job, no? Then it still is inaccurate as some sites got their refresh already... Maybe I should add that LastPost field to show in an hover for each site in the SEDE front page. Alternatively/additionally we could add an extra appsetting to indicate if the data is being updated. At the start of the job it has to be set to true, at the end to false.
|
|
| Sep 4, 2018 at 13:49 | comment | added | Taryn | @rene There was no failure, the job ran successfully. As far as the 'updated x' time, I'll see what we can do about fixing it. | |
| Sep 2, 2018 at 8:10 | comment | added | rene | I would like to hear if the SRE team did get their email ... or if this is caused by another not yet known fail case | |
| Sep 2, 2018 at 7:35 | history | asked | GlorfindelMod | CC BY-SA 4.0 |