-
Notifications
You must be signed in to change notification settings - Fork 63
Spider closes on exception #5
Comments
I've been trying to figure this out, and thought that the issue might be that the lock on the webdriver instance was not getting released when there is an exception in the parse method (It is released when the parse method is successful in the
with no luck. The first exception is clearly getting logged by the |
If you could submit a pull request with a failing test case, that'd be awesome. |
I'll add a test case as soon as I can figure out how to do it. My attempt to add one keeps failing miserably with |
Not that I know of. To make some sense of twisted, I looked at its documentation and at scrapy source code, and googled for specific problems I encountered. This blog post was also useful: http://jessenoller.com/blog/2009/02/11/twisted-hello-asynchronous-programming |
Updated logging strings to unicode
If exception is raised in parse method of a WebdriverResponse/WebdriverRequest whole spider closes/exits and doesnt continue
Steps to reproduce:
In any of your parse methods which parse WebDriverResponses raise an exception
Current result:
Scrapy stops crawling
Expected result:
Scrapy continues crawling next requests / urls
When parsing a normal scrapy Request / Response and you raise an error it seems to just continue. I did some quick testing on this, so I may be wrong though. This is a related error log:
The text was updated successfully, but these errors were encountered: