A crawler that always works flawlessly in development regularly raises UnknownObjectException other computers. The same navigation done by hand via irb on those machines works.
The website we are crawling has some frames, and the main frame contains yet another frameset so we have two levels. While reading watir.rb I noticed Watir::IE#wait does consider frames, but just one level of them. So my working assumption is that some inner frame is not completely loaded when the bot tries to access some element there. The PCs where it runs OK are slower than the PCs where it crashes. I don't know how that fits in the explanation (if it does), but it is a pattern. I'm gonna patch the method tomorrow to write some stack-based recursion. But before I do that I'd like to ask whether someone else already fixed this, or else if there is any technical reason that prevents that method from being recursive-like. -- fxn _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
