fix(sites): remediate false positive for Archive.org#2789
fix(sites): remediate false positive for Archive.org#2789The-Khan-Labs wants to merge 3 commits intosherlock-project:masterfrom
Conversation
Adds backend error message matching to correctly identify non-existent Archive.org accounts and prevent false positives.
Automatic validation of changes
Failures were detected on at least one updated target. Commits containing accuracy failures will often not be merged (unless a rationale is provided, such as false negatives due to regional differences). |
|
Thanks for the check. Archive.org returns a 200 response with a backend error message for non-existent users instead of a 404, which causes the F+ check to flag a failure. I manually verified multiple real and random usernames and confirmed that the message "could not fetch an account with user item identifier" only appears for non-existent accounts, while valid profiles are still detected correctly. |
|
Hey @The-Khan-Labs, just an FYI - it doesn't appear that your PR-ed commit includes any changes to the actual check - just to the comment attribute Something may have been left behind in devel |
|
Good catch — you’re right. The previous commit only updated the comment. |
ppfeister
left a comment
There was a problem hiding this comment.
Missing comma throws a parsing error, also just fixing alignment
Automatic validation of changes
Failures were detected on at least one updated target. Commits containing accuracy failures will often not be merged (unless a rationale is provided, such as false negatives due to regional differences). |
|
Seems that this endpoint isn't returning the expected error messages due to a JS requirement --- different outcome on your end? |
Adds backend error message matching to correctly identify non-existent Archive.org accounts and prevent false positives.