Repository navigation
Conversation
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.
Some valid Bruker TDF acquisitions contain rows with
Frames.NumPeaks = 0and no decodable binary payload. Reading these frames currently attempts blob decoding and reports a corrupt frame. This is observable through Python bindings asCould not read frame, Corrupt frame.The frame reader now records zero-peak frame IDs from the SQLite table and returns empty ions for those IDs without reading the binary blob. It still rejects unknown frame IDs and propagates decoder errors for nonempty frames.
Verification:
cargo fmt --all --check;cargo test -p timsrust-tdf --lib;cargo clippy -p timsrust-tdf --lib. Strict Clippy across dependencies is blocked by two pre-existing warnings infilemanager.