Fix GMC-800 history flash size#134
Merged
Wikilicious merged 2 commits intoMay 27, 2026
Merged
Conversation
anatoly-scherbakov
force-pushed
the
fix-gmc800-history-size
branch
from
ba0d11b to
384c2d3
Compare
Owner
|
Hey @anatoly-scherbakov, |
Contributor
Author
|
Done, thank you @Wikilicious! |
Owner
|
I plan to merge this... then release a semver patch version on pypi |
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
2 participants
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.
Summary
Why
GMC-800 history reads currently inherit the base 1 MiB flash size, causing get_raw_history() to stop before current records on devices with 2 MiB history memory.
Verification
python -m pytest tests/test_gmc800.py tests/test_devices/test_gmc800.py tests/test_device_get_history.py