#101 · ypercube
30 Sep 2009
My yoyoing opponent is named thriller :)
Public forum discussion.
30 Sep 2009
My yoyoing opponent is named thriller :)
18 Oct 2009
negative times are showing again and the monthly cups are not starting. I noticed that on Oct 16 that Richard temporarily shut down LG to do some updating, and that is probably when the problem began....
4 Nov 2009
*bump* -sigh-
5 Nov 2009
negative time has been ticking for almost 24 hours
22 Nov 2009
Monthly cup sections and the chess championship are being held up.
5 Feb 2010
bump 1148858
24 Feb 2010
bump
24 Feb 2010
negative times...
25 Feb 2010
-15 hours!!
25 Feb 2010
my opponent has -24.
13 Apr 2010
bump
13 Apr 2010
-16
18 Apr 2010
bump
18 Apr 2010
-14
18 Apr 2010
-15 :(
18 Apr 2010
I have -1 days of vacation left :P
18 Apr 2010
A known bug.
18 Apr 2010
oh ok
11 May 2010
bump
11 May 2010
:)
12 May 2010
I wonder - if you are at -37 hours, and you make a move, do you lose immediately on time? or will you have -1 hour? or 36?
Anyone ever tried?
13 May 2010
Can you change empathy answers after the time limit?
13 May 2010
Yes, until the game actually ends.
13 May 2010
Aganju, if you are at -37, or -377 or minus -3777, it doesn't matter, I think that your clock is set to +36.
So, if you have a game at -something, hurry up and play :)
13 May 2010
are you kidding? I never get below +200 in my games (except in special circumstances).
14 May 2010
bump
14 May 2010
bump
14 May 2010
I've said this before. If it were me and the "daemon" stopped working this often (i.e. once every few months), I'd be looking for a daemon-free alternative, or rewriting the daemon to have error recovery.
I guess the way it works now is, for example, the software writes records to some database as players sign up for a monthly tournament in some particular game. Then the daemon looks at the records every hour or so, and while there are 5 or more records for that game, it starts a tournament for 5 players who have signed up but not yet been assigned a tournament.
A daemon-free alternative would be to make the software that inserts a new waiting-player record check to see if there are now 5 players waiting, and if there are, start a new tournament immediately without waiting for any daemon. Yes, you need serialization for this approach (more than a single-threaded daemon needs), but I've always been able to come up with a design that makes the database's serialization facilities suffice (e.g. all conflicts can be resolved by using the database's property that only one insert of a new record with the same primary index field values can succeed.).
Granted, if the problem is an error encountered by the tournament-start code, the daemon-free code would have the same problem. But I think it's fairly unlikely that all the daemon's activities that could be made daemon-free would be encountering errors at the same time, while when the daemon stops, everything it does comes to halt, not just the activity encountering an error.
14 May 2010
And who's triggering a new Empathy round then ?
Granted, you can turn this into a daemon-free user-interaction as well. Whenever somebody thinks some action should have started, "they" (thanks, FatPhil for bringing 'singular they' to my attention ;) could click a link and get a response like " no action required now, but thanks for keeping Little Golem alive " or " thanks for reminding me to start new tournaments "
14 May 2010
Well, on first glance I see a risk and a difference:
- The difference is that currently, after the fifth player signed up, it takes some minutes for the tournament to start, so you can use that to sign up and remove yourself within seconds to see your current rating (I do that sometimes). With the new technique, you clicked it, you bought it. But I can see that this is not a relevant loss, you learn quickly (in the office, we would call that 'a training issue'...)
- the risk (also not sooo severe): if the code starting a tournament is running behind a players click, it is a little bit more open for hacks. Right now, all you hack into is your name getting in the list.
Another simple solution would be to run the demon under 'cron', or run a code under 'cron' that restarts the demon if its not answersing. Or kill and restart the demon every midnight. It should be relatively easy to stabilize this thing?
And before you ask, yes, windows does have 'cron' too. It's called differently but provides the equivalent functionality.
14 May 2010
@Michael: The jsp that displays your answers could trigger the new game if the old game's time limit has passed. If no one's looking at the GoE page then the new game wouldn't start "on time", but that fact would be unobservable. (Well, almost unobservable. You could also put triggers in the detailed-results page and the past-games page.)
@Phil: You've been justifying singular 'they'? You're younger than I thought.
@Aganju: The current daemon may well be being started every midnight or every 10 minutes, by cron or Scheduled Tasks or otherwise. If it checks the activities it can perform in some deterministic order, and the first activity it attempts is the one in which it encounters the error that causes it to quit or wait forever or loop forever or whatever, we'd see the same symptoms as a daemon which is started manually only.
14 May 2010
@MarleysGhost: [first paragraph] I like that idea, 'unobservable'. It's a bit like in quantum mechanics, if nobody looks (=measures), the system all all kind of contradicting stuff in parallel (superpositioned). But you are right. Except that if someone clicks on the page after a long time, it would maybe take a moment as it has to complete all the things first. But that would be ok.
[last paragraph] Ok. I would have assumed that such simple errors ('simple' like in 'infinitely reproducible with a known activity sequence') would be simple to debug and remove, and therefore already removed. But that might not be the case.
14 May 2010
@Aganju, yes, the player whose click triggers the next GoE game would have to wait for some processing to complete. But surely not the 70 hours that we've been waiting for the daemon!
15 May 2010
maybe the demon comes by every 72 hours, and at -72, he will come again and finish that round of empathy? Let's hope for it.
15 May 2010
@MG - Supporting a construction attested in the KJV makes me young? I wonder what I'd have to do in order to come over as old?
Turn that music down! Not that that noise is "music" anyway!
15 May 2010
My time isn't getting updated I should have got an extra 36 hours for making a move :(
15 May 2010
:(
15 May 2010
guess Richard is gone for the long weekend...
I'm getting low on games to play now, as nothing new is starting... :-(
15 May 2010
I just this minute got a reply from Richard concerning the problem:
"There is some new problem. I am solving this. Thanks."
16 May 2010
@aganju
If you get desperately short of games RoRoRo accepts challenges.
16 May 2010
I can play too ;)
20 May 2010
once again
21 May 2010
although games work again, Empathy is stuck (as before)
21 May 2010
wrong, everything is hung again.
21 May 2010
-4
21 May 2010
-10 hours -44 minutes
That is also wrong, because it should be 13 hours 12 minutes! It's counting until today midnight instead of yesterday midnight!
21 May 2010
?? consider a) the server is in a different time zone, and b) the server clock is at least 11 minutes off (I know because of the 'hit-new-year-midnight'-thread)
21 May 2010
yeah I know the zones. but the minutes don't fit, even including the 11 minutes. simple maths ;)
22 May 2010
I see your point.
Well, the code was probably not made to handle negative numbers correctly, so it messes up.
It gets a bit obnoxious... second week in a row where more than 50% of the time timeouts don't work, and no new tournaments start. I struggle to imagine that there are so many different errors in that code, so it's probably not fixed at all, just restarted.
23 May 2010
:((