Write a named gap manifest to the logfile and point the summary at it - #345
Merged
jp-spotter merged 2 commits intoAug 7, 2026
Merged
Conversation
This was referenced Aug 7, 2026
Merged
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.
The INCOMPLETE EXTRACT summary samples 3 examples per group, so the complete list of affected objects previously existed nowhere — and "where is the log file?" is the first question on nearly every help request. The logfile now receives a complete named manifest (guid + name per object, grouped like the console block, DEBUG so the console is unchanged), and the summary ends with the exact path to this run's logfile. Console output is byte-identical to the validated runs.