I think we're doing different things, that's why it's giving us completely different errors.
I just added files to imports in configuration.nix
I'm guessing you've got some manual error checking implemented with assertions?
error:
… while calling the 'seq' builtin
at «github:nixos/nixpkgs/4bd9165a9165d7b5e33ae57f3eecbcb28fb231c9?narHash=sha256-l/iNYDZ4bGOAFQY2q8y5OAfBBtrDAaPuRQqWaFHVRXM%3D»/lib/modules.nix:402:18:
401| options = checked options;
402| config = checked (removeAttrs config [ "_module" ]);
| ^
403| _module = checked (config._module);
… while evaluating a branch condition
at «github:nixos/nixpkgs/4bd9165a9165d7b5e33ae57f3eecbcb28fb231c9?narHash=sha256-l/iNYDZ4bGOAFQY2q8y5OAfBBtrDAaPuRQqWaFHVRXM%3D»/lib/modules.nix:305:9:
304| checkUnmatched =
305| if config._module.check && config._module.freeformType == null && merged.unmatchedDefns != [ ] then
| ^
306| let
(stack trace truncated; use '--show-trace' to show the full, detailed trace)
error: Path 'nix/bobo/test.nix' does not exist in Git repository "/home/bobo/dotfiles".
Command 'nix --extra-experimental-features 'nix-command flakes' build --print-out-paths '/home/bobo/dotfiles/nix#nixosConfigurations."bobo".config.system.build.nixos-rebuild' --no-link' returned non-zero exit status 1.
I can often only try to guess what's wrong by reading the stacktrace top-to-bottom, so I've somewhat gotten used to doing that.
I'm yet to see any nix error be more readable top to bottom. And I think it's intentionally designed that way so you don't need to scroll up.
What is the exact command you're running? In the screenshot above you've only got
nixos-rebuild --flake ...
Which shouldn't run at all since you don't have a command like switch
Also, what version of nix are you running? I'm on: nix (Nix) 2.34.6