Since the API Changes to not accept unsupported files changed the tem… #132
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.
Description
API changes caused temporary baseline scan files to be rejected by the validator when they don't have the expected
.socket.facts.jsonfilename format. This prevented baseline scans from being created when no previous scan exists, causing scan failures for new repositories.Root Cause
The
empty_head_scan_file()method was creating temporary files usingtempfile.mkstemp()with a generic suffix (.empty) and prefix (socket_baseline_), which generated filenames that didn't match the expected.socket.facts.jsonformat required by the API validator. The API now validates that manifest files follow expected naming patterns, causing these temporary baseline files to be rejected.Fix
Changed the temporary file creation logic to create files with the exact filename
.socket.facts.jsonin the system temporary directory instead of usingtempfile.mkstemp(). This ensures the temporary baseline scan files pass API validation while maintaining the same functionality. Also added debug flag support to the reachability engine.Public Changelog