Ludovic Courtès 51800e06de Allow recovery from isValidPath RPCs with an invalid path ... Currently, clients cannot recover from an isValidPath RPC with an invalid path parameter because the daemon closes the connection when that happens. More precisely: 1. in performOp, wopIsValidPath case, ‘readStorePath’ raises an ‘Error’ exception; 2. that exception is caught by the handler in ‘processConnection’; 3. the handler determines errorAllowed == false, and thus exits after sending the message. This last part is fixed by calling ‘startWork’ early on, as in the patch below. The same reasoning could be applied to all the RPCs that take one or more store paths as inputs, but isValidPath is, by definition, likely to be passed invalid paths in the first place, so it’s important for this one to allow recovery.		2014-03-18 23:22:49 +01:00
..
local.mk	Update Makefile variable names	2014-02-01 13:54:38 +01:00
nix-daemon.cc	Allow recovery from isValidPath RPCs with an invalid path	2014-03-18 23:22:49 +01:00