Repository navigation
resolve-nightly: discover SDK toolchain version by version probing - #45
Merged
Merged
Conversation
The SDK toolchain filename contains a version suffix (e.g. 2.1) that can change over time. The previous approach used a hardcoded version (2.0) which was already stale, and a directory-listing fallback that failed because the artifact server (S3-backed) returns NoSuchKey for directory path requests rather than an index. Replace with a version probe: iterate candidate versions from 3.9 down to 1.0, issuing a HEAD request for each, and use the first URL that returns HTTP 200. This works without any directory-listing support from the server and automatically picks up version bumps (e.g. 2.x -> 3.x) without requiring code changes. Signed-off-by: Hasibur Rahman Mohammed <hasiburr@qti.qualcomm.com>
Hasibur Rahman Mohammed (hasiburr-qti)
requested review from
NaveenCherukuri (CherukuriNaveenQC) and
GirishKadirisani
as code owners
September 22, 2026 05:26
GirishKadirisani
approved these changes
Sep 22, 2026
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.
Description
The SDK toolchain filename contains a version suffix (e.g. 2.1) that can change over time. The previous approach used a hardcoded version (2.0) which was already stale, and a directory-listing fallback that failed because the artifact server (S3-backed) returns NoSuchKey for directory path requests rather than an index.
Replace with a version probe: iterate candidate versions from 3.9 down to 1.0, issuing a HEAD request for each, and use the first URL that returns HTTP 200. This works without any directory-listing support from the server and automatically picks up version bumps (e.g. 2.x -> 3.x) without requiring code changes.