-
Notifications
You must be signed in to change notification settings - Fork 50
list-available gives results that are not available to install #306
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
Comments
@patricktcoakley swiftly relying entirely on the swift.org API for this. If there's a discrepancy in the API then I think that this issue belongs on the swift-org-website repository. |
Ok, feel free to close and I'll make an issue there. |
I will say though that the Swift API seems to give us:
which to me indicates that Swiftly is not taking into account the architecture/platforms when displaying the available toolchains and would argue that it is more on the Swifty side than the Swift website since it may very well be that those releases do have downloads, just not for the platform I was running at the time. |
@patricktcoakley when you ran the above list-available command, I'm assuming that you were on macOS at the time? This JSON does seem to indicate that there is a macOS toolchain from 2016 available, it's just that the download URL couldn't be figured out for it, for possibly historical reasons. As a default, all swift releases have a macOS toolchain, so there's no need for swiftly to inspect the platforms list when running on macOS. |
Now I see what you mean now, thanks. Yeah I used the Swift OpenAPI docs to get the releases JSON, but I didn't notice the Xcode property that determines it, but I can go ahead and log an issue on the site repo, just wanted to make sure I didn't miss something. |
Uh oh!
There was an error while loading. Please reload this page.
I haven't checked every version, but if I do
swiftly list-available 2
I getbut when I run
swiftly install 2.2.1
I getIt would also be nice if the error posted the full URL of the release it's failing on.
The text was updated successfully, but these errors were encountered: