swiftly list-available sometimes shows wrong version in use

[schafdog]

After installing (swiftly install 6.1.0 and swiftly use 6.1.0), swiftly still showed 6.0.3 as installed, in use.

Could reproduced afterward. Swiftly never change which was in use, but was correct on the command line. So it's mostly an cosmetic issue

root@nuc:~# swiftly use 6.0.3
The file `file:///etc/.swift-version` has been set to `Swift 6.0.3` (was 6.1.0)
root@nuc:/etc/fail2ban# swiftly list-available
Available release toolchains
----------------------------
Swift 6.1.0 (installed)
Swift 6.0.3 (installed, in use)
Swift 6.0.2
Swift 6.0.1
Swift 6.0.0
Swift 5.10.1
root@nuc:~# swiftly use 6.1.0
The file `file:///etc/.swift-version` has been set to `Swift 6.1.0` (was 6.0.3)
root@nuc:/etc/fail2ban# 
root@nuc:/etc/fail2ban# 
root@nuc:/etc/fail2ban# 
root@nuc:/etc/fail2ban# swiftly list-available
Available release toolchains
----------------------------
Swift 6.1.0 (installed)
Swift 6.0.3 (installed, in use)
Swift 6.0.2
Swift 6.0.1
Swift 6.0.0
Swift 5.10.1
root@nuc:~# swift --version
Swift version 6.1 (swift-6.1-RELEASE)
Target: x86_64-unknown-linux-gnu

[schafdog]

Maybe it was because I wasn't in the home directory. I cheated on the output. It changed behavior from
The file file:///etc/.swift-version has been set to Swift 6.1.0 (was 6.1.0)
to
The global default toolchain has been set to Swift 6.1.0 (was 6.0.3)

Still I believe it showed something wrong

[cmcgee1024]

@schafdog thanks for raising this.

swiftly's "in-use" marker can definitely change depending on the current working directory since the selection is affected by the presence of a .swift-version file. The global default is the one that swiftly will use if there is no such file in the parent tree.

Another view of what's happening is the swiftly list command that focuses on what is installed, and provides a bit more detail on how it selected the "in-use" toolchain.

Are you able to provide more detailed reproducible steps?

[schafdog]

I was standing somewhere in /etc/...

I could reproduce it:

root@nuc:/etc# swiftly list
Installed release toolchains
----------------------------
Swift 6.1.0
Swift 6.0.3 (in use) (default)

Installed snapshot toolchains
-----------------------------
root@nuc:/etc# swiftly use 6.1.0
A new file `file:///etc/.swift-version` will be created to set the new in-use toolchain for this project. Alternatively, you can set your default globally with the `--global-default` flag. Proceed with creating this file?
Proceed? (Y/n): Y

The file `file:///etc/.swift-version` has been set to `Swift 6.1.0` (was 6.0.3)
root@nuc:/etc# swiftly list
Installed release toolchains
----------------------------
Swift 6.1.0 (in use)
Swift 6.0.3 (default)

Installed snapshot toolchains
-----------------------------
root@nuc:/etc# swiftly list-available
Available release toolchains
----------------------------
Swift 6.1.0 (installed)
Swift 6.0.3 (installed, in use)
Swift 6.0.2
Swift 6.0.1
Swift 6.0.0
Swift 5.10.1

So swiftly list shows what swift --version reports , but list-available shows something else (global setting?)

I am on debian trixie. I don't think it matters, but...

[cmcgee1024]

Ok, I see what goes wrong here. The list-available is not coded (yet) to understand the difference between global default, and the more general idea of "in use" toolchain that considers other factors. Older swiftly only had the global default.

Thanks, the fix would go into the list-available subcommand to bring it up to speed with the changes in the other subcommands.