-
Notifications
You must be signed in to change notification settings - Fork 92
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
Fixing crash in dump-events #2717
Conversation
cleanup, and fixing a warning from the robot
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.
} | ||
|
||
case "EventTrace/PartitionInfoExtension": |
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.
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.
If it's obvious what I did to trigger legacy form mode instead of V2, I'd love to be corrected. This is the command I'm using. [1]
[1] Sarif.PatternMatcher.cli.exe analyze ..\..\..\..\..\..\AzureDevOps\ --recurse true --max-file-size-in-kb 999999999 --output .\ado.sarif --level "Error;Warning;Note" --plugin ".\SEC101.SecurePlaintextSecretsInternal.json" --log ForceOverwrite --insert ContextRegionSnippets --etw .\ADO-Run.etl
Suggest adding a release note on this in ReleaseNotes.md, similar to following. Please replace BUG: Resolve trace parsing |
Updating release notes for invalid operation exception fix.
Fixing single quotes in release notes.
I'm not 100% sure why this event started getting into my etl logs and triggering crashes, but I suspect the right answer is to treat it as another way of recognizing session start.