6 commits

Author	SHA1	Message	Date
John Ericson	10f864c5ae	Ensure all functional scripts are (a) executable (b) have shebang ... This is good for shebang, and also good for future build system simplifications	2024-05-28 12:46:24 -04:00
Eelco Dolstra	53ab5d87c2	Use expectStderr	2023-12-06 14:05:32 +01:00
Eelco Dolstra	83c067c0fa	PosixSourceAccessor: Don't follow any symlinks ... All path components must not be symlinks now (so the user needs to call `resolveSymlinks()` when needed).	2023-12-05 23:02:59 +01:00
Eelco Dolstra	345f79d016	Check that we can't follow symlinks outside of the allowed paths	2023-12-05 16:33:02 +01:00
Eelco Dolstra	ea95327e72	Move restricted/pure-eval access control out of the evaluator and into the accessor	2023-11-30 16:16:17 +01:00
John Ericson	68c81c7375	Put functional tests in tests/functional ... I think it is bad for these reasons when `tests/` contains a mix of functional and integration tests - Concepts is harder to understand, the documentation makes a good unit vs functional vs integration distinction, but when the integration tests are just two subdirs within `tests/` this is not clear. - Source filtering in the `flake.nix` is more complex. We need to filter out some of the dirs from `tests/`, rather than simply pick the dirs we want and take all of them. This is a good sign the structure of what we are trying to do is not matching the structure of the files. With this change we have a clean: ```shell-session $ git show 'HEAD:tests' tree HEAD:tests functional/ installer/ nixos/ ```	2023-10-06 09:05:56 -04:00

Renamed from tests/restricted.sh (Browse further)