Repository navigation
Conversation
Signed-off-by: Sai Asish Y <say.apm35@gmail.com>
This branch has not been deployed
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.
Change Summary
Overview
The source sequence counter comes out of packet parsing as an unsigned integer, so the gap subtraction in
_check_source_sequence_counterwraps and emitsRuntimeWarning: overflow encountered in scalar subtractwhenever the counter rolls over, as seen in the SWAPI logs. Casting the counter to int32 before the arithmetic removes the warning and keeps the missing packet count the same.File changes
imap_processing/utils.py: castsrc_seq_ctrto int32 in_check_source_sequence_counter.Testing
Added
test_check_source_sequence_counter_unsigned_rollover, which uses a uint16 counter with a rollover gap and fails on the RuntimeWarning without the change.Closes #3436