Skip to content
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

Fix #769 - Correctly indicate probe error to user #802

Merged
merged 2 commits into from
Nov 10, 2022
Merged

Fix #769 - Correctly indicate probe error to user #802

merged 2 commits into from
Nov 10, 2022

Conversation

mxsasha
Copy link
Collaborator

@mxsasha mxsasha commented Nov 10, 2022

Before this change, the only check was whether a test was complete,
not whether it was at all successful. After redirect to the result
page, we then presented the most recent result for each probe,
which could silently return results from the distant past.

There may still be some cases where test error handling is not optimal,
but those should be loud, which means #770 will notify us.

Before this change, the only check was whether a test was complete,
not whether it was at all successful. After redirect to the result
page, we then presented the most recent result for each probe,
which could silently return results from the distant past.
@mxsasha mxsasha self-assigned this Nov 10, 2022
@mxsasha mxsasha added this to the v1.7 milestone Nov 10, 2022
@mxsasha mxsasha linked an issue Nov 10, 2022 that may be closed by this pull request
@mxsasha mxsasha merged commit 10ec9b0 into main Nov 10, 2022
@mxsasha mxsasha deleted the fix-769 branch November 10, 2022 16:14
@mxsasha mxsasha mentioned this pull request Dec 13, 2022
2 tasks
mxsasha added a commit that referenced this pull request Dec 13, 2022
Before this change, the only check was whether a test was complete,
not whether it was at all successful. After redirect to the result
page, we then presented the most recent result for each probe,
which could silently return results from the distant past.

There may still be some cases where test error handling is not optimal,
but those should be loud, which means #770 will notify us.

(cherry picked from commit 10ec9b0)
mxsasha added a commit that referenced this pull request Dec 20, 2022
Before this change, the only check was whether a test was complete,
not whether it was at all successful. After redirect to the result
page, we then presented the most recent result for each probe,
which could silently return results from the distant past.

There may still be some cases where test error handling is not optimal,
but those should be loud, which means #770 will notify us.

(cherry picked from commit 10ec9b0)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

security.txt appears to be cached indefinitely
1 participant