LeastFixedPoint / wave-dice-robot

Automatically exported from code.google.com/p/wave-dice-robot
0 stars 0 forks source link

Dicy seems to fail when left in a wave for too long #42

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Start a wave, add dicy to it, make a few rolls
2. leave, come back later
3. Make a few more rolls

What is the expected output? What do you see instead?
It should continue to expand rolls, but it does not.

Please provide any additional information below.
Our group has not been able to get Dicy to last for more than a few rolls, 
or a few rolls at a time, but I'm not sure what causes the failure. Here is 
a wave that demonstrates it though:

https://wave.google.com/wave/#restored:wave:googlewave.com!w%252BidTjj-hud

This is pretty much killing us, but other than this, great work ;-)

Original issue reported on code.google.com by nate.aus...@gmail.com on 26 Nov 2009 at 6:03

GoogleCodeExporter commented 9 years ago
Part of the problem might have been saying 'done' on a wave before dicy had 
expanded 
it, when I've gone back and edited some of these blips, they've expanded 
correctly... I 
guess it was unclear to me that you needed to leave it open in edit mode? (I 
think I'd 
call that a bug too, since it makes behavior dependent on lag) I'm not sure if 
this 
completely explains the problem but I'll keep investigating.

Original comment by nate.aus...@gmail.com on 26 Nov 2009 at 7:02

GoogleCodeExporter commented 9 years ago
Nate, could you please invite me to that wave so I can take a look at it? :)

Original comment by shooshpa...@gmail.com on 27 Nov 2009 at 12:39

GoogleCodeExporter commented 9 years ago
Added shooshpanchick at googlewave, but this wave appears to be working fine 
now. I'm 
no longer reproducing the bug... 

Original comment by nate.aus...@gmail.com on 27 Nov 2009 at 4:59

GoogleCodeExporter commented 9 years ago
nate, the last bug I fixed was about this: if in a blip there was a roll that 
is 
invalid in a particular way, then no rolls in this blip would be executed. 
Maybe, this 
fixed your problem too somehow?

Please let me know if the problem appears again, this is the exact kind of 
problems 
that are difficult to catch but that annoy users the most :)

Original comment by shooshpa...@gmail.com on 27 Nov 2009 at 5:47

GoogleCodeExporter commented 9 years ago
It's possible! Thanks for your help, I'll let you know if I see anything else.

Original comment by nate.aus...@gmail.com on 27 Nov 2009 at 6:53