Bring detection timestamp up to beacon object #956
Merged
Conversation
This file contains 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
rlatapy-luna
force-pushed
the
feature/getDetectionTime
branch
2 times, most recently
from
a4c43b4 to
a89c39a
Compare
rlatapy-luna
force-pushed
the
feature/getDetectionTime
branch
from
a89c39a to
0cea58c
Compare
|
Looks great, @rlatapy-luna, thanks! I will run some tests to make sure it works for me before merging. |
|
Yep, this works well. Thank you for the contribution, @rlatapy-luna. |
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.
Allow to retrieve detection time, useful for background detections.
ScanResult::getTimestampNanosand system clock/elapsedRealTime to compute epoch timestamp.Beaconobject inmFirstCycleDetectionTimestampfield andmLastCycleDetectionTimestampwhich correspond respectively to the timestamp of the first and last detected packets.Linked issue #918