scriptis/lix
0
0
Fork 0
forked from lix-project/lix
Code Pull requests Activity
lix/tests/functional/remote-store.sh

35 lines
1 KiB
Bash
Raw Permalink Normal View History

* A test for the nix-worker.
2007-08-13 14:56:40 +00:00
source common.sh
clearStore
Test nix-store --switch-profile and more daemon actions
2014-02-26 17:28:55 +00:00
Separate auth and logic for the daemon Before, processConnection wanted to know a user name and user id, and `nix-daemon --stdio`, when it isn't proxying to an underlying daemon, would just assume "root" and 0. But `nix-daemon --stdio` (no proxying) shouldn't make guesses about who holds the other end of its standard streams. Now processConnection takes an "auth hook", so `nix-daemon` can provide the appropriate policy and daemon.cc doesn't need to know or care what it is.
2020-08-12 15:14:56 +00:00
# Ensure "fake ssh" remote store works just as legacy fake ssh would.
nix --store ssh-ng://localhost?remote-store=$TEST_ROOT/other-store doctor
Add `Store::isTrustedClient()` This function returns true or false depending on whether the Nix client is trusted or not. Mostly relevant when speaking to a remote store with a daemon. We include this information in `nix ping store` and `nix doctor` Co-Authored-By: John Ericson <John.Ericson@Obsidian.Systems>
2022-12-26 20:21:08 +00:00
# Ensure that store ping trusted works with ssh-ng://
nix --store ssh-ng://localhost?remote-store=$TEST_ROOT/other-store store ping --json | jq -e '.trusted'
* Refactoring.
2011-07-20 11:50:13 +00:00
startDaemon
Test nix-store --switch-profile and more daemon actions
2014-02-26 17:28:55 +00:00
Add `Store::isTrustedClient()` This function returns true or false depending on whether the Nix client is trusted or not. Mostly relevant when speaking to a remote store with a daemon. We include this information in `nix ping store` and `nix doctor` Co-Authored-By: John Ericson <John.Ericson@Obsidian.Systems>
2022-12-26 20:21:08 +00:00
if isDaemonNewer "2.15pre0"; then
# Ensure that ping works trusted with new daemon
nix store ping --json | jq -e '.trusted'
"but doctor, I AM the untrusted store": nix doctor had wrong trustedness This probably snuck in in a refactor using truthiness or so. The trustedness flag was having the optional fullness checked, rather than the actual contained trust level. Also adds some tests. ``` m1@6876551b-255d-4cb0-af02-8a4f17b27e2e ~ % nix store ping warning: 'nix store ping' is a deprecated alias for 'nix store info' Store URL: daemon Version: 2.20.4 Trusted: 0 m1@6876551b-255d-4cb0-af02-8a4f17b27e2e ~ % nix doctor warning: 'doctor' is a deprecated alias for 'config check' [PASS] PATH contains only one nix version. [PASS] All profiles are gcroots. [PASS] Client protocol matches store protocol. [INFO] You are trusted by store uri: daemon ``` Fixes: https://git.lix.systems/lix-project/lix/issues/232 Change-Id: I21576e2a0a755036edf8814133345987617ba3d0
2024-04-08 05:34:24 +00:00
# Suppress grumpiness about multiple nixes on PATH
(nix doctor || true) 2>&1 | grep 'You are trusted by'
Add `Store::isTrustedClient()` This function returns true or false depending on whether the Nix client is trusted or not. Mostly relevant when speaking to a remote store with a daemon. We include this information in `nix ping store` and `nix doctor` Co-Authored-By: John Ericson <John.Ericson@Obsidian.Systems>
2022-12-26 20:21:08 +00:00
else
# And the the field is absent with the old daemon
nix store ping --json | jq -e 'has("trusted") | not'
fi
Fix deadlock in IFD through the daemon Fixes #4235.
2020-11-17 12:50:36 +00:00
# Test import-from-derivation through the daemon.
remote-store test: Break out IFD expression into a separate file (cherry picked from commit 9cb287657bec5a969d8bb1678d598d9fa820e60b)
2023-12-23 22:15:09 +00:00
[[ $(nix eval --impure --raw --file ./ifd.nix) = hi ]]
Fix deadlock in IFD through the daemon Fixes #4235.
2020-11-17 12:50:36 +00:00
Actually test nix-env with a remote store The `remote-store` test loads the `user-env` one to test nix-env when using the daemon, but actually does it incorrectly because every test starts (in `common.sh`) by resetting the value of `NIX_REMOTE`, meaning that the `user-env` test will never use the daemon. Fix this by setting `NIX_REMOTE_` before sourcing `user-env.sh` in the `remote-store` test, so that `NIX_REMOTE` is correctly set inside the test
2020-06-08 08:01:14 +00:00
storeCleared=1 NIX_REMOTE_=$NIX_REMOTE $SHELL ./user-envs.sh
Test nix-store --switch-profile and more daemon actions
2014-02-26 17:28:55 +00:00
Add a test ensuring compatibility with an old daemon This requires adding `nix` to its own closure which is a bit unfortunate, but as it is optional (the test will be disabled if `OUTER_NIX` is unset) it shouldn't be too much of an issue. (Ideally this should go in another derivation so that we can build Nix and run the test independently, but as the tests are running in the same derivation as the build it's a bit complicated to do so).
2020-11-10 09:43:33 +00:00
nix-store --gc --max-freed 1K
Test nix-store --switch-profile and more daemon actions
2014-02-26 17:28:55 +00:00
nix-store --dump-db > $TEST_ROOT/d1
NIX_REMOTE= nix-store --dump-db > $TEST_ROOT/d2
Doh
2014-02-26 21:41:29 +00:00
cmp $TEST_ROOT/d1 $TEST_ROOT/d2
Test nix-store --switch-profile and more daemon actions
2014-02-26 17:28:55 +00:00
* Refactoring.
2011-07-20 11:50:13 +00:00
killDaemon
Copy permalink