[racket] Continue: reentrant promises and custodian suicides

Hi Ryan,

On Thu, Jul 14, 2011 at 09:17:39AM -0600, Ryan Culpepper wrote:
> >       force: reentrant promise fun-p
>
> Those look like they're from ryanc/db. I suspect you see them at the
> very beginning, before the "lazy requires" (which are implemented
> with promises) have been forced.

Thanks a bunch for that! It wasn't really a big deal, certainly if it
only happened on startup. Indeed, I probably only saw them happening
while `siege' was still running on the background, when I ctrl+c'd and
reloaded the Racket process after the latter error, and the server was
hit immediately by a request storm upon startup.

> >	thread: the custodian has been shut down: #<custodian>
> 
> I'm not sure about this one. Do you get a context/backtrace with this error?

Unfortunately that is the only message printed to the console. If
there's a way to make this more verbose or helpful I am more than
happy to try and reproduce this. I suspect this is with Continue as it
kills the accepting TCP socket, but I'm no expert.

Cheers,
Dominic