On 25 November 2015 at 14:54, Robby Findler <ro...@eecs.northwestern.edu> wrote: > I'm still not completely > sure, but since you seem to be able to provoke the error, that > emboldens me to suggest you apply the diff below and see if it goes > away.
I'm doing this. Annoyingly, I can't force the crash at will yet, and an automated handin-server stress-tester is not in our plans yet :-|. > That diff is probably not what we'd want in the end, since it is too > much locking (we would want a namespace-specific lock not a global > one) but if the error does go away, that means that this is probably > the right place to put the lock in. Makes sense. But for my production environment, I guess that this patch won't overly restrict concurrency: I guess namespaces correspond to checkers in the handin-server, right? So, since I only ever open one assignment, I should only have one namespace anyway? Cheers, Paolo -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
