Closed luisanevers closed 9 years ago
Probably sliverstatus returned false - cause the server was essentially giving an error.
Trac comment by ahelsing on 10-11-2013 at 12:11
Assigning to 2.5. We should fix this for the next release to print a more friendly explanation.
Trac comment by sedwards (github user: seledwards) on 10-11-2013 at 12:44
I put in some code that looks like it fixed this. I tried three times to reproduce the error and couldn't. Closing.
Trac comment by sedwards (github user: seledwards) on 02-24-2014 at 20:21
While running a test, issued a readyToLogin.py immediately after the sliver creation. This caused an exception captured below. Note that subsequent readyToLogin.py was successful:
Will work on reproducing the problem, but the window when this happens is a few seconds.
Using version gcf 2.4.1, which is not available from the "Version" pull-down.
Imported from trac ticket #399, created by lnevers on 10-11-2013 at 11:54, last modified: 02-24-2014 at 20:21