t128_tank: stream from the beginning if parsing the index fails#82
Merged
gregschrock merged 1 commit intorelease-128tech-1.22.100-multiarch-supportfrom Sep 17, 2025
Conversation
I95-62311 #time 4h
shriyanshk128T
approved these changes
Sep 11, 2025
shriyanshk128T
left a comment
There was a problem hiding this comment.
Should we do some manual testing just to make sure this doesn't break anything?
Collaborator
Author
|
Added testing here: https://github.com/Juniper-SSN/ssr/pull/18009 |
c94be0d
into
release-128tech-1.22.100-multiarch-support
2 checks passed
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.
I95-62311
Description
There are a couple cases when reading the index file we might return an error indicating that it failed and why.
The intention here was to provide information, but not to fail. The default index should be used when these errors occur. However, the calling code was written to check for the error and "fail" if observed. Instead, the failure should be logged and the process should continue. The code is updated to behave as described.
Testing: https://github.com/Juniper-SSN/ssr/pull/18009
The index code for reference: