depot - monorepo for the virus lounge

Age	Commit message (Collapse)	Author	Files	Lines
2013-11-22	Add ‘make dist’ support	Eelco Dolstra	1	-1/+1

2013-11-22	Add missing #include	Eelco Dolstra	1	-1/+1

2013-11-22	Generate the parser and the lexer	Eelco Dolstra	1	-1/+5

2013-11-22	New non-recursive, plain Make-based build system	Eelco Dolstra	10	-0/+86

2013-11-22	Include <cstring> for memset	Eelco Dolstra	1	-0/+1
	This should fix building on Illumos.
2013-11-19	Check meta values and warn about bad ones	Eelco Dolstra	4	-26/+54

2013-11-19	Generalise meta attributes	Eelco Dolstra	5	-204/+204

2013-11-19	Shorter error message	Eelco Dolstra	1	-2/+1

2013-11-19	Drop support for user environment manifests in ATerm format	Eelco Dolstra	1	-112/+1

2013-11-19	nix-env -q: Add a --json flag	Eelco Dolstra	1	-8/+45

2013-11-19	Refactor JSON output	Eelco Dolstra	2	-13/+56

2013-11-19	Add a toJSON primop	Eelco Dolstra	6	-24/+150

2013-11-18	Add a primop unsafeGetAttrPos to return the position of an attribute	Eelco Dolstra	4	-6/+37

2013-11-18	Add a symbol __curPos that expands to the current source location	Eelco Dolstra	5	-2/+37
	I.e. an attribute set { file = <string>; line = <int>; column = <int>; }.
2013-11-18	Support quoted attribute names in -A	Eelco Dolstra	1	-10/+34
	This is requires if you have attribute names with dots in them. So you can now say: $ nix-instantiate '<nixos>' -A 'config.systemd.units."postgresql.service".text' --eval-only Fixes #151.
2013-11-14	Remove nix-setuid-helper	Eelco Dolstra	9	-446/+32
	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	4	-26/+35
	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-11-12	Make function calls tail-recursive	Eelco Dolstra	4	-40/+65

2013-11-12	Make ifs and asserts tail-recursive	Eelco Dolstra	2	-4/+11
	The local Value object prevented g++ from making a tail call. Not clear why. In any case, not using a temporary makes g++ do the tail call.
2013-11-12	Get rid of an intermediary on the stack	Eelco Dolstra	2	-13/+17

2013-10-28	Fix building without a garbage collector	Eelco Dolstra	1	-5/+5
	http://hydra.nixos.org/build/6695350
2013-10-28	Fix a segfault in genericClosure	Eelco Dolstra	1	-16/+25
	It kept temporary data in STL containers that were not scanned by Boehm GC, so Nix programs using genericClosure could randomly crash if the garbage collector kicked in at a bad time. Also make it a bit more efficient by copying points to values rather than values.
2013-10-28	Slightly optimize listToAttrs	Eelco Dolstra	3	-9/+10

2013-10-24	Rename "attribute sets" to "sets"	Eelco Dolstra	9	-59/+52
	We don't have any other kind of sets so calling them attribute sets is unnecessarily verbose.
2013-10-24	Remove unnecessary call to forceStringNoCtx	Eelco Dolstra	1	-1/+1

2013-10-24	Add a typeOf primop	Eelco Dolstra	1	-3/+28
	We already have some primops for determining the type of a value, such as isString, but they're incomplete: for instance, there is no isPath. Rather than adding more isBla functions, the generic typeOf function returns a string representing the type of the argument (e.g. "int").
2013-10-24	Don't require NIX_SHOW_STATS for NIX_COUNT_CALLS	Eelco Dolstra	1	-0/+1

2013-10-23	Memoize evalFile() lookups under both the original and resolved name	Eelco Dolstra	1	-4/+9
	Previously we only used the resolved name, causing repeated resolution (e.g. /dir to /dir/default.nix).
2013-10-22	For auto roots, show the intermediate link	Eelco Dolstra	1	-1/+1
	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-17	Fold two stack trace messages in derivations	Eelco Dolstra	1	-4/+2
	Combined with the previous changes, stack traces involving derivations are now much less verbose, since something like while evaluating the builtin function `getAttr': while evaluating the builtin function `derivationStrict': while instantiating the derivation named `gtk+-2.24.20' at `/home/eelco/Dev/nixpkgs/pkgs/development/libraries/gtk+/2.x.nix:11:3': while evaluating the derivation attribute `propagatedNativeBuildInputs' at `/home/eelco/Dev/nixpkgs/pkgs/stdenv/generic/default.nix:78:17': while evaluating the attribute `outPath' at `/nix/store/212ngf4ph63mp6p1np2bapkfikpakfv7-nix-1.6/share/nix/corepkgs/derivation.nix:18:9': ... now reads while evaluating the attribute `propagatedNativeBuildInputs' of the derivation `gtk+-2.24.20' at `/home/eelco/Dev/nixpkgs/pkgs/development/libraries/gtk+/2.x.nix:11:3': ...
2013-10-17	Don't show <nix/derivation.nix> in stack traces	Eelco Dolstra	3	-2/+5
	Messages like while evaluating the attribute `outPath' at `/nix/store/212ngf4ph63mp6p1np2bapkfikpakfv7-nix-1.6/share/nix/corepkgs/derivation.nix:18:9': are redundant, because Nix already shows that it's evaluating a derivation: while instantiating the derivation named `firefox-24.0' at `/home/eelco/Dev/nixpkgs/pkgs/applications/networking/browsers/firefox/default.nix:131:5': while evaluating the derivation attribute `nativeBuildInputs' at `/home/eelco/Dev/nixpkgs/pkgs/stdenv/generic/default.nix:76:17':
2013-10-17	Ensure proper type checking/coercion of "${expr}"	Eelco Dolstra	1	-2/+3
	Now we only rewrite "${expr}" to expr if expr is a string literal.
2013-10-17	Revert the behaviour of antiquoted paths to pre-Nix 1.6	Eelco Dolstra	1	-4/+4
	Commit 159e621d1a9c4391b53f3d822109c36931934698 accidentally changed the behaviour of antiquoted paths, e.g. "${/foo}/bar" used to evaluate to "/nix/store/<hash>-foo/bar" (where /foo gets copied to the store), but in Nix 1.6 it evaluates to "/foo/bar". This is inconsistent, since " ${/foo}/bar" evaluates to " /nix/store/<hash>-foo/bar". So revert to the old behaviour.
2013-10-16	Retry all SQLite operations	Eelco Dolstra	2	-128/+169
	To deal with SQLITE_PROTOCOL, we also need to retry read-only operations.
2013-10-16	Fix a race in registerFailedPath()	Eelco Dolstra	1	-2/+1
	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	1	-46/+42

2013-10-16	Don't wrap read-only queries in a transaction	Eelco Dolstra	1	-6/+0
	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	1	-4/+8

2013-10-16	Treat SQLITE_PROTOCOL as SQLITE_BUSY	Eelco Dolstra	1	-1/+1
	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-10-08	printStats(): Print the size of the symbol table in bytes	Eelco Dolstra	3	-0/+15

2013-10-08	Deduplicate filenames in Pos	Eelco Dolstra	3	-6/+7
	This saves ~4 MiB of RAM for NixOS system instantiation, and ~18 MiB for "nix-env -qa".
2013-10-08	Treat undefined variable errors consistently	Eelco Dolstra	3	-2/+8
	Previously, a undefined variable inside a "with" caused an EvalError (which can be caught), while outside, it caused a ParseError (which cannot be caught). Now both cause an UndefinedVarError (which cannot be caught).
2013-10-08	Show the exact position of undefined variables	Eelco Dolstra	4	-21/+18
	In particular, undefined variable errors in a "with" previously didn't show any position information, so this should help a lot in those cases.
2013-10-08	Remove some unused functions	Eelco Dolstra	1	-15/+0

2013-10-08	Merge VarRef into ExprVar	Eelco Dolstra	4	-21/+8

2013-10-07	Don't show calls to primops in stack traces	Eelco Dolstra	1	-6/+1
	Since they don't have location information, they just give you crap like: while evaluating the builtin function `getAttr': while evaluating the builtin function `derivationStrict': ...
2013-10-02	Fix segfault in nix-repl / hydra-eval-jobs	Eelco Dolstra	1	-3/+3
	If a "with" attribute set fails to evaluate, we have to make sure its Env record remains unchanged. Otherwise, repeated evaluation gives a segfault: nix-repl> :a with 0; { a = x; b = x; } Added 2 variables. nix-repl> a error: value is an integer while an attribute set was expected nix-repl> b Segmentation fault
2013-10-02	Report OOM errors better	Eelco Dolstra	2	-1/+8

2013-10-02	Fix typo	Eelco Dolstra	1	-1/+1

2013-09-17	RestoreSink: Slightly reduce the number of concurrent FDs	Eelco Dolstra	1	-0/+1