-
-
Notifications
You must be signed in to change notification settings - Fork 14.9k
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
treewide/nixos: remove with lib;
part 12
#369419
treewide/nixos: remove with lib;
part 12
#369419
Conversation
with lib;
part 12
63c3423
to
6549f0d
Compare
6549f0d
to
b122789
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything looks good. I'm planning on merging after running a few nixosTests.
Again, breaking things.
|
Damn it! Ugh. I'm not merging any more of these because I can't verify correctness if I can't trust the tool to mutate the right areas. I checked on the commit that introduced the error (4b798ee). It's within a "with pkgs" context and I suspect that's what caused the issue, but I can't tell. |
I'm going to ask the same question I've asked before:
|
Now that I'm thinking again about this: can somebody explain to me why we're doing it like this in the first place? Like, new usages of the same pattern will come up so I think the time people "invested" on that would be way better served if tooling was developed that does this reliably and can be used by contributors easily on their new changes (and by maintainers on their code). Fixing behind everyone's back is something that we'll never be done with given that new usages will arise every now and then (and yes, I consider it a horrible contribution experience if we'd actually block PRs by asking people to... idk... remove |
There were more of them, e.g. certmgr. A suspect list: |
I'm clicking the revert button. I regret merging. |
Reverted in #369795 |
Oh, that hydra diff contains multiple of these "remove |
Actually, all of the stuff detected by trunk-combined job removals was from other PRs or fixed in the meantime 🤦🏽 as we can see from the eval after merging the revert. |
Sigh. I am trying to learn the "mass-evaluate-all-NixOS-tests" strategy that Mic92 alluded to in the previous PR. It took me a few tries to understand the output and how to discern something was already broken vs. newly broken, but I think I got it dialed in. I've fixed everything that I found in this PR: There may be more latent issues for modules without a NixOS test, or in the same modules without a NixOS test covering them. |
Laziness can bite us here? |
I suppose I'll make the |
Description of changes
part of #208242
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.