depot - monorepo for the virus lounge

Age	Commit message (Collapse)	Author	Files	Lines
2013-08-07	Run the daemon worker on the same CPU as the client	Eelco Dolstra	9	-4/+92
	On a system with multiple CPUs, running Nix operations through the daemon is significantly slower than "direct" mode: $ NIX_REMOTE= nix-instantiate '<nixos>' -A system real 0m0.974s user 0m0.875s sys 0m0.088s $ NIX_REMOTE=daemon nix-instantiate '<nixos>' -A system real 0m2.118s user 0m1.463s sys 0m0.218s The main reason seems to be that the client and the worker get moved to a different CPU after every call to the worker. This patch adds a hack to lock them to the same CPU. With this, the overhead of going through the daemon is very small: $ NIX_REMOTE=daemon nix-instantiate '<nixos>' -A system real 0m1.074s user 0m0.809s sys 0m0.098s
2013-08-06	Set the default GCC optimisation level to -O3	Eelco Dolstra	1	-0/+2

2013-08-06	Remove obsolete reference to ATerms	Eelco Dolstra	1	-3/+3

2013-08-02	In the profiler output, show function names (if available)	Eelco Dolstra	2	-8/+8

2013-08-02	Let the ordering operators also work on strings	Eelco Dolstra	3	-4/+12
	E.g. ‘"foo" < "bar"’ now works.
2013-08-02	Add comparison operators ‘<’, ‘<=’, ‘>’ and ‘>=’	Eelco Dolstra	4	-1/+31

2013-08-02	Add integer ‘-’, ‘*’ and ‘/’ operators	Eelco Dolstra	4	-2/+16

2013-08-02	Add a unary integer negation operator	Eelco Dolstra	3	-4/+11
	This allows saying "-1" instead of "builtins.sub 0 1".
2013-08-02	Overload the ‘+’ operator to support integer addition	Eelco Dolstra	3	-15/+23

2013-07-31	nix-shell: Don't disable Automake dependency tracking	Eelco Dolstra	1	-1/+2
	Nixpkgs' stdenv disables dependency tracking by default. That makes sense for one-time builds, but in an interactive environment we expect repeated "make" invocations to do the right thing.
2013-07-31	Test the delayed with a bit more	Eelco Dolstra	3	-5/+8

2013-07-31	Make Env smaller	Eelco Dolstra	2	-21/+23
	Commit 20866a7031ca823055a221653b77986faa167329 added a ‘withAttrs’ field to Env, which is annoying because it makes every Env structure bigger and we allocate millions of them. E.g. NixOS evaluation took 18 MiB more. So this commit squeezes ‘withAttrs’ into values[0]. Probably should use a union...
2013-07-31	Don't use NULL	Eelco Dolstra	1	-4/+2

2013-07-31	Avoid thunks when a fromWith var can be looked up without evaluation	Shea Levy	2	-8/+8
	Signed-off-by: Shea Levy <shea@shealevy.com>
2013-07-31	Delay evaulation of `with` attrs until a variable lookup needs them	Shea Levy	4	-7/+40
	Evaluation of attribute sets is strict in the attribute names, which means immediate evaluation of `with` attribute sets rules out some potentially interesting use cases (e.g. where the attribute names of one set depend in some way on another but we want to bring those names into scope for some values in the second set). The major example of this is overridable self-referential package sets (e.g. all-packages.nix). With immediate `with` evaluation, the only options for such sets are to either make them non-recursive and explicitly use the name of the overridden set in non-overridden one every time you want to reference another package, or make the set recursive and use the `__overrides` hack. As shown in the test case that comes with this commit, though, delayed `with` evaluation allows a nicer third alternative. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-07-30	Detect stack overflows	Eelco Dolstra	3	-1/+80
	Previously, if the Nix evaluator gets a stack overflow due to a deep or infinite recursion in the Nix expression, the user gets an unhelpful message ("Segmentation fault") that doesn't indicate that the problem is in the user's code rather than Nix itself. Now it prints: error: stack overflow (possible infinite recursion) This only works on x86_64-linux and i686-linux. Fixes #35.
2013-07-30	killUser: Don't let the child kill itself on Apple	Shea Levy	1	-0/+13
	The kill(2) in Apple's libc follows POSIX semantics, which means that kill(-1, SIGKILL) will kill the calling process too. Since nix has no way to distinguish between the process successfully killing everything and the process being killed by a rogue builder in that case, it can't safely conclude that killUser was successful. Luckily, the actual kill syscall takes a parameter that determines whether POSIX semantics are followed, so we can call that syscall directly and avoid the issue on Apple. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-07-23	buildenv: remove special treatment of python files	Florian Friesdorf	1	-3/+0
	buildPythonPackage does not leave easy_install.pth and site.py anymore. A python package that leaves these files is broken. An exception to this is setuptoolsSite which packages setuptools' site.py. To include it into a buildenv, this patch is even needed, not just cosmetic.
2013-07-19	Add hacking notes plus a script for running nix-shell	Eelco Dolstra	3	-0/+54

2013-07-19	nix-shell: Set $IN_NIX_SHELL	Eelco Dolstra	1	-0/+2
	This allows scripts to distinguish between a real build and a Nix shell.
2013-07-19	nix-shell: Set some environment variables also set by build.cc	Eelco Dolstra	1	-1/+3
	Setting $NIX_STORE causes the purity checks in gcc/ld-wrapper to kick in, so that's why we unset $NIX_ENFORCE_PURITY.
2013-07-19	Rename ‘nix-build --run-env’ to ‘nix-shell’	Eelco Dolstra	7	-92/+201

2013-07-19	nix-build --run-env: Add a ‘--pure’ flag	Eelco Dolstra	2	-3/+43
	This causes the environment to be (almost) cleared, thus giving a shell that more closely resembled the actual Nix derivation.
2013-07-18	Revert "build-remote.pl: Enforce timeouts locally"	Eelco Dolstra	2	-3/+6
	This reverts commit 69b8f9980f39c14a59365a188b300a34d625a2cd. The timeout should be enforced remotely. Otherwise, if the garbage collector is running either locally or remotely, if will block the build or closure copying for some time. If the garbage collector takes too long, the build may time out, which is not what we want. Also, on heavily loaded systems, copying large paths to and from the remote machine can take a long time, also potentially resulting in a timeout.
2013-07-15	Allow bind-mounting regular files into the chroot	Shea Levy	1	-1/+9
	mount(2) with MS_BIND allows mounting a regular file on top of a regular file, so there's no reason to only bind directories. This allows finer control over just which files are and aren't included in the chroot without having to build symlink trees or the like. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-07-12	Fix syntax error in unpack-channel	Eelco Dolstra	1	-1/+1

2013-07-12	Garbage collector: Don't follow symlinks arbitrarily	Eelco Dolstra	5	-47/+53
	Only indirect roots (symlinks to symlinks to the Nix store) are now supported.
2013-07-12	Add gzip support for channel unpacking	Gergely Risko	4	-3/+8

2013-07-12	doc: typo	Domen Kožar	1	-1/+1

2013-07-11	build-remote.pl: Move "building ..." message to a better place	Eelco Dolstra	1	-1/+1

2013-07-11	nix-build --run-env: Always use Bash	Eelco Dolstra	1	-1/+1
	Fixes #113. Fixes #131.
2013-07-11	nix-build --run-env: Source $stdenv/setup in the interactive shell	Eelco Dolstra	2	-16/+26
	This ensures that not just environment variables are set, but also shell functions such as unpackPhase, configurePhase and so on.
2013-07-07	Leave `HAVE_HUP_NOTIFICATION' undefined on GNU/Hurd.	Ludovic Courtès	1	-2/+7

2013-07-03	Manual: auto-optimise-store is disabled by default	Eelco Dolstra	1	-5/+6

2013-07-01	Add support for uncompressed NARs in binary caches	Eelco Dolstra	6	-17/+31
	Issue NixOS/hydra#102.
2013-07-01	copy-from-other-stores.pl: Respect $NIX_BIN_DIR	Eelco Dolstra	1	-4/+4

2013-07-01	copy-from-other-stores.pl: Report downloaded size as 0	Eelco Dolstra	1	-1/+1

2013-06-20	Don't set $preferLocalBuild and $requiredSystemFeatures in builders	Eelco Dolstra	2	-8/+15
	With C++ std::map, doing a comparison like ‘map["foo"] == ...’ has the side-effect of adding a mapping from "foo" to the empty string if "foo" doesn't exist in the map. So we ended up setting some environment variables by accident.
2013-06-20	Don't substitute derivations that have preferLocalBuild set	Eelco Dolstra	3	-7/+15
	In particular this means that "trivial" derivations such as writeText are not substituted, reducing the number of GET requests to the binary cache by about 200 on a typical NixOS configuration.
2013-06-20	Increase SQLite's auto-checkpoint interval	Eelco Dolstra	1	-2/+2
	Common operations like instantiating a NixOS system config no longer fitted in 8192 pages, leading to more fsyncs. So increase this limit.
2013-06-20	Disable the copy-from-other-stores substituter	Eelco Dolstra	1	-0/+2
	This substituter basically cannot work reliably since we switched to SQLite, since SQLite databases may need write access to open them even just for reading (and in WAL mode they always do).
2013-06-20	Don't keep "disabled" substituters running	Eelco Dolstra	9	-7/+46
	For instance, it's pointless to keep copy-from-other-stores running if there are no other stores, or download-using-manifests if there are no manifests. This also speeds things up because we don't send queries to those substituters.
2013-06-17	Bump version	Eelco Dolstra	1	-1/+1

2013-06-17	Update release notes for Nix 1.5.3	Eelco Dolstra	1	-0/+48

2013-06-13	Allow hard links between the outputs of a derivation	Eelco Dolstra	3	-9/+20

2013-06-13	Fix a security bug in hash rewriting	Eelco Dolstra	1	-0/+6
	Before calling dumpPath(), we have to make sure the files are owned by the build user. Otherwise, the build could contain a hard link to (say) /etc/shadow, which would then be read by the daemon and rewritten as a world-readable file. This only affects systems that don't have hard link restrictions enabled.
2013-06-13	Fix assertion failure in canonicalisePathMetaData() after hash rewriting	Eelco Dolstra	1	-2/+9
	The assertion in canonicalisePathMetaData() failed because the ownership of the path already changed due to the hash rewriting. The solution is not to check the ownership of rewritten paths. Issue #122.
2013-06-13	computeFSClosure: Only process the missing/corrupt paths	Eelco Dolstra	1	-11/+17
	Issue #122.
2013-06-13	Typo	Eelco Dolstra	1	-1/+1

2013-06-13	In repair mode, update the hash of rebuilt paths	Eelco Dolstra	2	-4/+5
	Otherwise subsequent invocations of "--repair" will keep rebuilding the path. This only happens if the path content differs between builds (e.g. due to timestamps).