Recent build failure

[wilywampa]

I spend some time debugging this failed build 0.74.3 and just wanted to mention that the build failure happens with nushell 0.115.0 (from 2 days ago) and not with 0.114.1, so it's not an fzf change that caused that failure. A very simple completer in nushell will demonstrate the same behavior:

$env.config.completions.external.completer = {|spans|
    fzf
}

[junegunn]

Thanks for looking into it.

@sim590 Hi, do you happen to know if anything has changed in the latest version of Nushell?

[sim590]

This seems to be explained by nushell/nushell#18771 which will be worked around by nushell/nushell#18764 in the future as an opt-out option. This means, the users will have to enable the experimental feature to avoid the issues. Like so:

nu --experimental-options '[background-completions=false]'

It is also going to be possible to configure this with an environment variable:

NU_EXPERIMENTAL_OPTIONS=background-completions=false

I tested it and it seems to work.

This is a workaround though. I don't know yet if it would be possible to fix it properly without opting out background-completions. That would be preferable.

[junegunn]

Thank you very much for looking into it. Hopefully, the upstream project will come up with a better way to support this.

[junegunn]

Hmm, so this is not just a CI failure, but a real user-scenario breakage.

[sim590]

Hmm, so this is not just a CI failure, but a real user-scenario breakage.

Indeed.

And good news: nushell/nushell#18881 has addressed the issue and it should fix our use case without user intervention in a new Nushell release. From what I can see on the PR, it's scheduled for 0.116.0.

In the future, nushell/reedline#876 could open the way towards supporting built-in commands. I'll make sure to follow the thread and implement the keybind route when it's possible.

[junegunn]

Thanks a ton.