Handle errors from sageranger due to invalid authorization token - #90
Open
montse-jara wants to merge 28 commits into
Open
Handle errors from sageranger due to invalid authorization token#90montse-jara wants to merge 28 commits into
montse-jara wants to merge 28 commits into
Conversation
…d optional print for last synced.
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
1 participant
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.
This pull request originally was created to handle errors due to invalid authorization tokens but now also contains edits to work with an updated version of the sageranger repository which shifts the logic of unpacking config values into sageranger instead and then importing those functions (parse_args, get_info...) in cougarvision. This version of cougarvision also contains edits to the strikeforce get functions. Strikeforce get ids now prints each camera to associated id.