Open
Conversation
|
I've experienced the same issue with one of my tags and traced the weird timestamp and location to line 207 where the
Because Thanks you for the fix @rkreutz! |
FauconSpartiate
added a commit
to FauconSpartiate/openhaystack
that referenced
this pull request
May 23, 2024
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.
Noticed that on some instances a single report from the results payload might fail to decrypt for reasons I'm not sure why, that is not handled by
FindMyControllerwhich meant that a failing report would actually show as a random location at the Atlantic Ocean (lat 0, long 0).This PR changes that, so the controller keeps track of whatever indexes failed to be decrypted and remove them from the array of results.