vdbergh
vdbergh
Hmm the worker seems to log only successful api calls (which take a few ms), not those that time out (~30s I guess).
It would be nice to understand this though. I wonder if the `dead tasks` scavenging has something to do with it. If this scheduled task (which runs every minute) has...
> pagination needed in both cases > Yes but one should still be able to sort the whole table (not only the current page).
Sounds good. Sorting by username is indeed the only thing I do.
I am not sure about reincluding the bounds information. This is already included in the new_run message (where it logically belongs). It you want to see the history of a...
> as far as im aware, this is the message that now shows up in the events log and in the popup notifications. this is an end-of-run event, which is...
> if we're worried about duplicate information in the event log, then why bother having such notifications at all? Notifications are a different issue. They are implemented via the event...
> > As I told you the bounds and TC information is only two clicks away. > > I don't see why putting the human-readable information two clicks away and...
> LLR+game count is exactly equal to the elo bar, except 10x more readable for humans.) This is because you think you can outsmart statistics. Which is an illusion.