Repository navigation
Conversation
…unt or password, so a wrong password cannot lock the account
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A login Share rejects for an unknown account, a wrong password or too many attempts blocks further logins with the same credentials for 15 minutes, as LF Hub does, since Share locks accounts after repeated bad logins. Until then each fetch returns the same login error without contacting Share, so the banner and the Nightscout fallback work as before. Other failures are tried again at the next fetch. The watch's standalone fetch shares the same rule.