Well just doing a simple
Thread.list.each { |t| t.join }
didn't work (well, it actually hung)
So I will wait to see what the capybara-webkit guys have to say.
On Dec 21, 7:44 am, Jeremy Evans <[email protected]> wrote:
> On Dec 20, 9:34 pm, philly-mac <[email protected]> wrote:
>
> > Just as an update to this issue I have created this issue with the
> > capaybara-webkit guys
>
> >https://github.com/thoughtbot/capybara-webkit/issues/230
>
> I added a comment to that issue.
>
> > Perhaps you can more quickly see what may be happening there, or have
> > some other ideas off the top of your head.
>
> > By the way, I tried the :single_threaded=>true option, and that did
> > not work. It did give me other strange stuff happening though, so I
> > removed it and am just focuses on my current issue.
>
> Strange stuff can definitely occur if you are using the single
> threaded connection pool with simultaneous access by multiple
> threads. Like I said in that issue comment, your issue sounds like a
> race condition.
>
> Jeremy
--
You received this message because you are subscribed to the Google Groups
"sequel-talk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sequel-talk?hl=en.
