> > Yeah, you would think. And you'd probably be right. But I'd started off
> > with a more aggressive change (rescue Object => detail) and printing the > > class of detail. At this level it was coming back with an Errno::XXXXX > > depending on what I'd done to disrupt thing. I scaled it back to this > > minimal patch which causes all my test cases to work (they loop, as they > > should). > > > > I am not thrilled with the patch as it stands, but I wanted to get > something > > out there for people to look at, talk about, and try while I cycled to > > another problem for a bit. > > > > > > So where are we on this? It looks a little ugly (I should know - > pretty sure I've channeled that code at some point) but it's a bug fix > not a refactor. I'm for pushing this. > I'd like to take one more stab and see if I can nail down any more cases/code paths, and probably loosen up the rescue so that non-StandardError exceptions will get trapped. I can't reproduce that state but I can't prove that it never happens, and so it's arguably better to just trap everything, circle around and retry than to crash and burn. -- Markus --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" 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/puppet-dev?hl=en -~----------~----~----~----~------~----~------~--~---
