Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

multiBitFlag rollover to 0 once max is reached #87

Merged
merged 5 commits into from
Jan 18, 2025
Merged

Conversation

cosmiccodon
Copy link
Contributor

@cosmiccodon cosmiccodon commented Jan 9, 2025

Currently the multiBitFlag class is capable of counting from 0 to the maximum value of the number of bits requested. Once at the maximum value it would not change if incremented.

This PR changes the behavior so that the multiBitFlag class always rolls over to 0 after reaching its maximum. We have checked the variables assigned as the multiBitFlag class and believe this is not a breaking change. It's different behavior that we need to expect when reading satellite logs but no functionality should break.

@nateinaction nateinaction mentioned this pull request Jan 9, 2025
@nateinaction nateinaction changed the title Bitflag merge multiBitFlag rollover to 0 once max is reached Jan 10, 2025
cosmiccodon and others added 2 commits January 14, 2025 19:04
Co-authored-by: Alan De La Torre <[email protected]>
…BitFlag in line 85. It tries to type hint during an assignment. Removed : multiBitFlag
Copy link
Member

@nateinaction nateinaction left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good teamwork here. Going to merge this in so I can rebase the bigflag refactor PR.

@nateinaction nateinaction merged commit eea2381 into main Jan 18, 2025
3 checks passed
@nateinaction nateinaction deleted the bitflag-merge branch January 18, 2025 21:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants