Stable branch and nixpkgs unstable version conflict

[whereiendandyoubegin]

Yazelix diagnostics

:: yzx status --json
{"schema_version":1,"name":"Yazelix Nova","version":"1.1.0","package":"full","config_home":"/home/dan/.config/yazelix","state_dir":"/home/dan/.local/share/yazelix","shell":"nu","editor_command":"yzx-hx","editor":"/nix/store/27ck90gplyc5hj5vl1qn7lg5fp63pq0q-yzx-hx/bin/yzx-hx","agent_command":"auto","inside_zellij":true}

Details

The stable branch hard-asserts zellijBuildBase.version == "0.44.3", but nixpkgs unstable now ships 0.45.1. Anyone using inputs.nixpkgs.follows = "nixpkgs" in their yazelix input will hit an evaluation failure.

The workaround is to remove the follows statement, but this forces a full separate closure build against yazelix's bundled June nixpkgs, including the kernel, glibc, and everything downstream. On my machine this triggered ~40GB of rebuilds just to get my system to evaluate again.

More broadly, I've now had two issues where the stable branch produces a completely broken config for me without warning. I think the CI tests may not be covering follows-against-recent-unstable, or configs with non-trivial option sets enabled. A test that actually attempts a build with inputs.nixpkgs.follows pointing to a current unstable pin, and with a more representative set of options enabled, would catch both of these before they hit users.

I can't actually build the system now because I have other dependencies that relied on the latest version of nixpkgs unstable.

[luccahuguet]

thanks for the report

can you try again?

[whereiendandyoubegin]

This is working, thank you.

My issue is still that the stable branch is being pushed to basically as much as the main branch, and the current CI checks (on push) are not thorough enough to catch things like this. It would be good if the stable branch was scripted to only be pushed to once a week, and to only accept commits that have been through the full CI smoke test.

[luccahuguet]

funny, I thought I was working only on the edge branch for like 1 or 2 weeks, and keeping stable chill

[luccahuguet]

let me see if I can improve the situation.

I do wanna be able to push edge straight to main and stable if I just fixed something important

[whereiendandyoubegin]

Just had another bit of an annoying experience, in 1.2 it seems that Radar and Forest are enabled by default. I think this should have been feature flagged really or opt-in on the nix flake. I don't know how to use Radar, and I'm using Yazi to open my files so it is not helpful when I open them then have to immediately also type the file name into forest (which I don't know the controls for). And more annoying is the fact that when the LSP flake input fetch dialogue box is open, I can't actually press fetch/ignore, I assume because Forest is open, but I also can't select a file with Forest, I assume because the LSP dialogue is open.

It's possible there is an issue with my nix module, I'll try and change it now. I can, of course, just pin to a specific commit but I really don't want to have to do that. Maybe having tags and feature flags for new releases would be handy, a lot of repos use tags which I'm much happier pinning because you can still push security/urgent commits without pushing a new set of features that fundamentally change my workflow.

[luccahuguet]

Just had another bit of an annoying experience, in 1.2 it seems that Radar and Forest are enabled by default. I think this should have been feature flagged really or opt-in on the nix flake. I don't know how to use Radar, and I'm using Yazi to open my files so it is not helpful when I open them then have to immediately also type the file name into forest (which I don't know the controls for). And more annoying is the fact that when the LSP flake input fetch dialogue box is open, I can't actually press fetch/ignore, I assume because Forest is open, but I also can't select a file with Forest, I assume because the LSP dialogue is open.

It's possible there is an issue with my nix module, I'll try and change it now. I can, of course, just pin to a specific commit but I really don't want to have to do that. Maybe having tags and feature flags for new releases would be handy, a lot of repos use tags which I'm much happier pinning because you can still push security/urgent commits without pushing a new set of features that fundamentally change my workflow.

looking into these issues you had

[whereiendandyoubegin]

It would be really nice if Forest and Radar had opt-out options. I get wanting them to be the default workflow for new users, but it's a bit frustrating not being able to configure my install to always have yazi on the left sidebar, and to be able to turn off Forest. I could learn Forest easily but the keys are completely different to the yazi workflow that was default, and when I load into my editor I don't ever want to have a new plugin that I have to learn before I can get any work done. I can switch to manage my own helix but that seems like a bad solution.

[luccahuguet]

in your yazelix config, configure:

sidebar.command = "yzx-yazi"

or

programs.yazelix.config.settings.sidebar.command = "yzx-yazi";

[luccahuguet]

I will make forest opt-out! Good call.

[luccahuguet]

Also, there are no further plans for big helix plugin changes. Forest was a one-off addition, so you can stay relaxed about this point

[luccahuguet]

gpt5.6 said this:

For the nil prompt:

[language-server.nil.config.nil.nix.flake]
autoArchive = false

true automatically fetches instead. nil documents null as “ask every time,” true as automatic nix flake archive, and false as using only already-available inputs. Configuration
(https://github.com/oxalica/nil/blob/205c8ba65a7f956d7837a710794001b3515c65ff/docs/configuration.md#L58-L73), prompt implementation
(https://github.com/oxalica/nil/blob/205c8ba65a7f956d7837a710794001b3515c65ff/crates/nil/src/server.rs#L494-L529).

[luccahuguet]

in the edge branch helix already starts unfocused, so this is just a mattter of promoting edge to main and stable

[luccahuguet]

edge also brings major performance improvements

[luccahuguet]

thank you for bring these to my attention