Seth Call

By the way, I've encountered this scenario at least 20-30 times since this was released, so it's not too rare in practice.

Thanks for the response. Since I don't need to call close in onerror, that will simplify my logic and remove my current 'un-acked' loop. In looking through code, it seems...

oh! Thank you for clarifying that; much appreciated.

I'm also seeing the same thing. Ruby 2.0 and poltergeist 1.5.0 ``` ruby capybara (2.2.0) capybara-screenshot (0.3.14) capybara (>= 1.0, < 3) capybara-webkit (1.1.0) capybara (~> 2.0, >= 2.0.2) capybara...

After debugging it a little, i see that the save method in capybara-screenshot has this: ``` ruby return if capybara.current_path.to_s.empty? ``` This, in my case, is empty. So, save bails,...

Ok, figured it out. I was doing: ``` ruby config.after(:each) do Capybara.reset_sessions! end ``` Instead if I do this, reset_sessions! goes after the screenshot gem. Problem fixed. ``` ruby config.append_after(:each)...

Welll.... It seems to me if the save operation fails, ideally it would say why... And additionally it would be nice if the msg about where the file was saved...

@616slayer616 There seems to be good work in this PR; perhaps though the new test you added should have the @RepeatedIfExceptionsTest removed from the methods to verify with certainty that...

PR: https://github.com/uiri/toml/pull/365

@MattHapner I had the same issue. I believe Wireshark had installed a particular version of libpcap that is troublesome for Pcap4j. Try this: `brew install libpcap` THen run your java...