Repository navigation
Studio-first physical test: visible Capture workspace, in-app SV/PTP evidence, bundled firmware #258
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
Closed
masarray
wants to merge
10
commits into
integration/p0-receiver-ptp-sv-and-studio-gui-20261020
from
fix/studio-first-class-capture-ux-20261020
Closed
Studio-first physical test: visible Capture workspace, in-app SV/PTP evidence, bundled firmware #258
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
0b28f22
feat(studio): expose first-class capture command without scripts
masarray d20ac12
feat(studio): one persistent dedicated Capture tab, no duplicate worker
masarray ea2f980
feat(studio): primary Capture action beside live signal controls
masarray 490eeaf
refactor(studio): remove hidden duplicate capture from Device setup
masarray a721867
feat(studio-capture): expose compact decoded evidence summary and sup…
masarray 7883bdd
feat(studio-capture): report wire facts in GUI and make capture setup…
masarray 1c9b0f0
feat(studio-capture): show SV/PTP counters and first-run capture supp…
masarray ee92ad2
test(studio-capture): verify in-app summary mirrors real production d…
masarray a431b51
test(studio-capture): assert visible one-owner workspace and native e…
masarray c959486
test(studio-capture): match dynamic Capture button label expression
masarray File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When an operator selects the wrong TAP/SPAN adapter or captures only PTP traffic, parsing can succeed and
ptpFramescan contain useful evidence whilematched == 0; however,usableis false and this condition suppresses the entire summary. The QML panel consequently displays none of the decoded SV/PTP counters and only reports “No valid SV packets,” hiding the PTP count that would help diagnose the capture setup. Populate the summary for completed parses while retaining theINVALID_CAPTUREstatus.Useful? React with 👍 / 👎.