feat: require Spark Checker version >=1.17.0 #547
Merged
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.
We have recently introduced a new requirement - when an HTTP retrieval succeeded, the checker is required to test HEAD retrieval request too. The preprocessing step in spark-evaluate discards measurements missing
head_status_code
.Because a large part of the network is running an older version of Spark Checker, measurements from these nodes are rejected as invalid. See CheckerNetwork/spark-evaluate#498.
This patch is moving the validation step earlier to the pipeline by changing the minimum required Spark Checker version to 1.17.0.
Checker nodes running an older version will start receiving a helpful "OUTDATED CLIENT" error response.
A screenshot from the Spark Internal Dashboard showing the correlation between outdated checker client and rejected measurements: