Name the cause when a watch stops on an auth failure #18
Reference in New Issue
Block a user
Delete Branch "benvin/watchpr-auth-failure"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A 401/403 was handled as one thing, so watchpr re-minted on every rejection and reported "token expired" for a permission boundary or an anonymous run that had no token to expire, sending the reader after the wrong problem.
--onceas well as from the watch loop