-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document how to handle action failures #157
Open
Gallaecio
wants to merge
10
commits into
scrapy-plugins:main
Choose a base branch
from
Gallaecio:action-failure-handling
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 3 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
7cc483b
Document how to handle action failures
Gallaecio 47197ee
Remove an empty line
Gallaecio 00b2c2a
Fix the ZyteAPIFailedActionsRetryMiddleware example code
Gallaecio 20f3715
Merge remote-tracking branch 'scrapy-plugins/main' into action-failur…
Gallaecio deedfff
Implement retries on action error
Gallaecio 75faf68
Make mypy happy
Gallaecio cdc0aa1
Do not assume Zyte API responses have actions
Gallaecio f19e157
Backport get_retry_request for older Scrapy versions
Gallaecio 62c9ae6
Fix test failures due to a nameless spider class
Gallaecio ea2da8f
Update docs/reference/settings.rst
Gallaecio File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,111 @@ | ||
.. _actions: | ||
|
||
====================== | ||
Handling action errors | ||
====================== | ||
|
||
Zyte API responses are considered successful :ref:`even if some browser actions | ||
fail <zyte-api-successful-responses>`. | ||
|
||
If you wish to retry requests whose response contains actions that failed, you | ||
can define a custom Scrapy middleware as follows: | ||
|
||
.. code-block:: python | ||
:caption: myproject/middlewares.py | ||
|
||
from typing import Optional, Type, Union | ||
|
||
from scrapy import Request, Spider | ||
from scrapy.crawler import Crawler | ||
from scrapy.http import Response | ||
from scrapy.downloadermiddlewares.retry import get_retry_request | ||
from scrapy.settings import BaseSettings | ||
from scrapy_zyte_api.responses import ZyteAPIResponse, ZyteAPITextResponse | ||
|
||
class ZyteAPIFailedActionsRetryMiddleware: | ||
|
||
@classmethod | ||
def from_crawler(cls, crawler: Crawler): | ||
return cls(crawler.settings) | ||
|
||
def __init__(self, settings: BaseSettings): | ||
if not settings.getbool("RETRY_ENABLED"): | ||
raise NotConfigured | ||
self.max_retry_times = settings.getint("RETRY_TIMES") | ||
self.priority_adjust = settings.getint("RETRY_PRIORITY_ADJUST") | ||
|
||
def process_response( | ||
self, request: Request, response: Response, spider: Spider | ||
) -> Union[Request, Response]: | ||
if not isinstance(response, (ZyteAPIResponse, ZyteAPITextResponse)): | ||
return response | ||
if request.meta.get("dont_retry", False): | ||
return response | ||
if any("error" in action for action in response.raw_api_response["actions"]): | ||
reason = "An action failed" | ||
new_request = self._retry(request, reason, spider) | ||
if new_request: | ||
return new_request | ||
else: | ||
return response | ||
# Note: If you prefer requests that exceed all retries to | ||
# be dropped, raise scrapy.exceptions.IgnoreRequest here, | ||
# instead of returning the response. | ||
return response | ||
|
||
def _retry( | ||
self, | ||
request: Request, | ||
reason: Union[str, Exception, Type[Exception]], | ||
spider: Spider, | ||
) -> Optional[Request]: | ||
max_retry_times = request.meta.get("max_retry_times", self.max_retry_times) | ||
priority_adjust = request.meta.get("priority_adjust", self.priority_adjust) | ||
return get_retry_request( | ||
request, | ||
reason=reason, | ||
spider=spider, | ||
max_retry_times=max_retry_times, | ||
priority_adjust=priority_adjust, | ||
) | ||
|
||
And enable it in your settings: | ||
|
||
.. code-block:: python | ||
:caption: myproject/settings.py | ||
|
||
|
||
DOWNLOADER_MIDDLEWARES = { | ||
"myproject.middlewares.ZyteAPIFailedActionsRetryMiddleware": 525, | ||
} | ||
|
||
If you use | ||
:class:`~scrapy.downloadermiddlewares.httpcache.HttpCacheMiddleware`, you might | ||
want to use a custom :setting:`HTTPCACHE_POLICY <scrapy:HTTPCACHE_POLICY>` to | ||
prevent responses with failed actions (i.e. after exceeding retries) to be | ||
cached: | ||
|
||
.. code-block:: python | ||
:caption: myproject/extensions.py | ||
|
||
from scrapy import Request | ||
from scrapy.extensions.httpcache import DummyPolicy | ||
from scrapy.http import Response | ||
from scrapy_zyte_api.responses import ZyteAPIResponse, ZyteAPITextResponse | ||
|
||
class ZyteAPIFailedActionsPolicy(DummyPolicy): | ||
|
||
def should_cache_response(self, response: Response, request: Request): | ||
if ( | ||
isinstance(response, (ZyteAPIResponse, ZyteAPITextResponse)) | ||
and any("error" in action for action in response.raw_api_response["actions"]) | ||
): | ||
return False | ||
return super().should_cache_response(response, request) | ||
|
||
And enable it in your settings: | ||
|
||
.. code-block:: python | ||
:caption: myproject/settings.py | ||
|
||
HTTPCACHE_POLICY = "myproject.extensions.ZyteAPIFailedActionsPolicy" |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a lot of code in this section; I wonder if we should make it a part of the library itself instead.
It seems like a general theme: if action failed, should the response be considered a success or a failure? The current default is success, but it seems that making it a failure is better (with an option to get back), as it allows to detect more issues.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
deedfff does this for the middleware. Do we want to do something about the cache policy, or is it OK to keep that documentation-only?