lix -

Age	Commit message (Collapse)	Author
2014-02-03	Fix assertion failure in ‘nix-store --load-db’	Eelco Dolstra
	Namely: nix-store: derivations.cc:242: nix::Hash nix::hashDerivationModulo(nix::StoreAPI&, nix::Derivation): Assertion `store.isValidPath(i->first)' failed. This happened because of the derivation output correctness check being applied before the references of a derivation are valid.
2014-02-01	Give a friendly error message if the DB directory is not writable	Eelco Dolstra
	Previously we would say "error: setting synchronous mode: unable to open database file" which isn't very helpful.
2014-02-01	Fix "make dist"	Eelco Dolstra

2014-02-01	Remove Automakefiles	Eelco Dolstra

2014-02-01	Update Makefile variable names	Eelco Dolstra

2014-01-30	Rename Makefile -> local.mk	Eelco Dolstra

2014-01-21	Fix some clang warnings	Eelco Dolstra

2014-01-21	Merge branch 'master' into make	Eelco Dolstra
	Conflicts: src/libexpr/eval.cc
2014-01-09	Generate schema.sql.hh	Eelco Dolstra

2014-01-09	Update Makefiles	Eelco Dolstra

2014-01-08	Fix checking of NAR hashes	Eelco Dolstra
	headdesk headdesk headdesk So since commit 22144afa8d9f8968da351618a1347072a93bd8aa, Nix hasn't actually checked whether the content of a downloaded NAR matches the hash specified in the manifest / NAR info file. Urghhh...
2014-01-06	wording	Domen Kožar

2013-12-10	Garbage collector: Release locks on temporary root files	Eelco Dolstra
	This allows processes waiting for such locks to proceed during the trash deletion phase of the garbage collector.
2013-12-05	Print a trace message if a build fails due to the platform being unknown	Eelco Dolstra

2013-11-25	Rename Makefile.new -> Makefile	Eelco Dolstra

2013-11-23	Use libnix as a prefix for all Nix libraries	Eelco Dolstra
	In particular "libutil" was always a problem because it collides with Glibc's libutil. Even if we install into $(libdir)/nix, the linker sometimes got confused (e.g. if a program links against libstore but not libutil, then ld would report undefined symbols in libstore because it was looking at Glibc's libutil).
2013-11-23	Allow (dynamic) libraries to depend on other libraries	Eelco Dolstra

2013-11-22	Drop the dependency on Automake	Eelco Dolstra

2013-11-22	Rename $(here) to $(d) for brevity, and remove trailing slash	Eelco Dolstra

2013-11-22	Add ‘make dist’ support	Eelco Dolstra

2013-11-22	New non-recursive, plain Make-based build system	Eelco Dolstra

2013-11-22	Include <cstring> for memset	Eelco Dolstra
	This should fix building on Illumos.
2013-11-14	Remove nix-setuid-helper	Eelco Dolstra
	AFAIK, nobody uses it, it's not maintained, and it has no tests.
2013-11-12	Make function calls show up in stack traces again	Eelco Dolstra
	Note that adding --show-trace prevents functions calls from being tail-recursive, so an expression that evaluates without --show-trace may fail with a stack overflow if --show-trace is given.
2013-10-22	For auto roots, show the intermediate link	Eelco Dolstra
	I.e. "nix-store -q --roots" will now show (for example) /home/eelco/Dev/nixpkgs/result rather than /nix/var/nix/gcroots/auto/53222qsppi12s2hkap8dm2lg8xhhyk6v
2013-10-16	Retry all SQLite operations	Eelco Dolstra
	To deal with SQLITE_PROTOCOL, we also need to retry read-only operations.
2013-10-16	Fix a race in registerFailedPath()	Eelco Dolstra
	Registering the path as failed can fail if another process does the same thing after the call to hasPathFailed(). This is extremely unlikely though.
2013-10-16	Convenience macros for retrying a SQLite transaction	Eelco Dolstra

2013-10-16	Don't wrap read-only queries in a transaction	Eelco Dolstra
	There is no risk of getting an inconsistent result here: if the ID returned by queryValidPathId() is deleted from the database concurrently, subsequent queries involving that ID will simply fail (since IDs are never reused).
2013-10-16	Print a distinct warning for SQLITE_PROTOCOL	Eelco Dolstra

2013-10-16	Treat SQLITE_PROTOCOL as SQLITE_BUSY	Eelco Dolstra
	In the Hydra build farm we fairly regularly get SQLITE_PROTOCOL errors (e.g., "querying path in database: locking protocol"). The docs for this error code say that it "is returned if some other process is messing with file locks and has violated the file locking protocol that SQLite uses on its rollback journal files." However, the SQLite source code reveals that this error can also occur under high load: if( cnt>5 ){ int nDelay = 1; /* Pause time in microseconds / if( cnt>100 ){ VVA_ONLY( pWal->lockError = 1; ) return SQLITE_PROTOCOL; } if( cnt>=10 ) nDelay = (cnt-9)238; /* Max delay 21ms. Total delay 996ms */ sqlite3OsSleep(pWal->pVfs, nDelay); } i.e. if certain locks cannot be not acquired, SQLite will retry a number of times before giving up and returing SQLITE_PROTOCOL. The comments say: Circumstances that cause a RETRY should only last for the briefest instances of time. No I/O or other system calls are done while the locks are held, so the locks should not be held for very long. But if we are unlucky, another process that is holding a lock might get paged out or take a page-fault that is time-consuming to resolve, during the few nanoseconds that it is holding the lock. In that case, it might take longer than normal for the lock to free. ... The total delay time before giving up is less than 1 second. On a heavily loaded machine like lucifer (the main Hydra server), which often has dozens of processes waiting for I/O, it seems to me that a page fault could easily take more than a second to resolve. So, let's treat SQLITE_PROTOCOL as SQLITE_BUSY and retry the transaction. Issue NixOS/hydra#14.
2013-09-06	Don't apply the CPU affinity hack to nix-shell (and other Perl programs)	Eelco Dolstra
	As discovered by Todd Veldhuizen, the shell started by nix-shell has its affinity set to a single CPU. This is because nix-shell connects to the Nix daemon, which causes the affinity hack to be applied. So we turn this off for Perl programs.
2013-09-02	Only show trace messages when tracing is enabled	Eelco Dolstra

2013-09-02	Add an option to limit the log output of builders	Eelco Dolstra
	This is mostly useful for Hydra to deal with builders that get stuck in an infinite loop writing data to stdout/stderr.
2013-08-26	Fix typos, especially those that end up in the Nix manual	Ivan Kozik

2013-08-26	Fix personality switching from x86_64 to i686	Gergely Risko
	On Linux, Nix can build i686 packages even on x86_64 systems. It's not enough to recognize this situation by settings.thisSystem, we also have to consult uname(). E.g. we can be running on a i686 Debian with an amd64 kernel. In that situation settings.thisSystem is i686-linux, but we still need to change personality to i686 to make builds consistent.
2013-08-07	Run the daemon worker on the same CPU as the client	Eelco Dolstra
	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-07-18	Revert "build-remote.pl: Enforce timeouts locally"	Eelco Dolstra
	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
	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	Garbage collector: Don't follow symlinks arbitrarily	Eelco Dolstra
	Only indirect roots (symlinks to symlinks to the Nix store) are now supported.
2013-06-20	Don't set $preferLocalBuild and $requiredSystemFeatures in builders	Eelco Dolstra
	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
	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
	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
	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
	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-13	Allow hard links between the outputs of a derivation	Eelco Dolstra

2013-06-13	Fix a security bug in hash rewriting	Eelco Dolstra
	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
	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
	Issue #122.
2013-06-13	In repair mode, update the hash of rebuilt paths	Eelco Dolstra
	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).