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.
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
[434] Allow to filter jobs in ZyteJobsComparisonMonitor by close_reason #440
[434] Allow to filter jobs in ZyteJobsComparisonMonitor by close_reason #440
Changes from 9 commits
ee6aa4f
12b4862
74e89e5
6406295
493bb9d
ebb6781
9df1949
2114ca4
0ebe5f9
868566f
92dc72c
cc2c256
7260d08
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
thought: This makes sense since it seems we can't filter by close_reason in
client.spider.jobs.list()
.I wonder if it makes sense to retrieve
MAX_API_COUNT
count jobs each time from the API and append tototal_jobs
the jobs that meet the criteria until we reachnumber_of_jobs
. This should result in fewer API calls, but those calls will be larger. What do you think, @VMRuiz?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.
If the default close reason is
finished
I would keep it as it is. As the most common scenario will be that you fetch the last few jobs and those will have the finished status. Even in the case where a second call is needed - due to a few unexpected failed jobs in between - it could still be faster for lower volumes than making 1 very big call.On the contrary, if it's expected that uncommon close reasons like
timeout
are used, then it makes sense to fetch as many jobs as possible, as they will be few or even none.