Repository navigation
Add application-only website parsing and prefilled failure issues - #154
Merged
Merged
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
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.
Application-only payloads such as
78 03 13 15 31 00and bare DIF/VIF records such as03 13 15 31 00now parse on the website after wired and wireless frame detection fails. The fallback supports all website output formats, labels application-only results, and rejects malformed or incomplete records. Existing full-frame APIs keep their strict behavior.Parse failures and partial frame results show an Open GitHub issue link prefilled with the captured payload, error codes/messages, parse attempts, parser version, output format, browser, and reproduction URL. AES keys are omitted. The toolbar report action uses the captured failure even if the input is edited afterward; successful retries clear stale reports.
Validation:
Pages continues to rebuild the WASM assets during deployment.