Skip to main content

SCHEMA_VERSION

Constant SCHEMA_VERSION 

Source
pub const SCHEMA_VERSION: u32 = 20;
Expand description

The version of the record encoding that this build of kizz reads and writes.

Version 2 replaced the first step record with the full one: the step specification, the observations with their path states, and why the step ran. Version 3 added the cache check’s reasons, with the differences it found, when each record’s observations were written, and the failure message of a missing or non-executable program. Version 4 added the reason a run’s result was not cached, which marks a record that is never a cache hit, and the exit of a command that could not start. Version 5 added explanations: the verdict of the most recent build in step positions, the parts of the task program and how output names the task in task records, and the position, build, and time of each last writer. Version 6 added the reason for the result of a command that exited with a code of its own after the build was interrupted, which, like a command that a signal stopped then, is never a cache hit. Version 7 added the owners of step records: the tasks that produced or used each record, which path resets and kizz cache clean use. Version 8 added task programs as last writers: each last writer names its task and either the step that wrote the path, with its position, or the task program, and explanations name a task program that last wrote a changed input. Version 9 added the owner, as user and group numbers, to every regular-file state, the mode and owner to every directory state, and the permission and owner changes that a cache check finds. Version 10 added the timestamps option to the step specification, the modification and change times to every directory state, and the timestamp change that a cache check finds. Version 11 keeps directory listings in the order the file system returned their entries, with a hash of that order and a hash of the same entries sorted, and adds the names of the entries that changed and the order change to what a cache check finds. Version 12 adds the reason for a run in which files changed after the command first read them or ran them, which lists each such file and whether the command wrote it, and, like the other reasons a run’s result is not cached, marks a record that is never a cache hit. Version 13 adds the xattr access bit, the extended attributes recorded with a path whose attributes the command read or listed, each name with a hash of its value, for the path and, for a symbolic link, for what it points to, and the change that lists the attributes that appeared, disappeared, or changed. Version 14 adds the numbers of the system calls that a command made and that the tracer does not know to every step record, whether or not its result was cached, and the reason for a run that made such calls, which, like the other reasons a run’s result is not cached, marks a record that is never a cache hit. Version 15 adds the connections that a command made to IPv4 and IPv6 addresses and to Unix sockets, by path or abstract name, to every step record, whether or not its result was cached; they never keep a result out of the cache. Version 16 adds the cache identity, in the meta/ family: the host name, the effective user and group, the supplementary groups, the umask, the machine architecture, and the CPU model of the process that created the database, which every later open compares with the current values. Version 17 adds the machine state that a command started with to every step record, the machine names to the step specification, the machine state values that a cache check finds changed, and the reasons that name a change of the machine names or of the machine state. Version 18 adds the reason of a command that runs because its task is marked cache=never, to step records and to the explanations of step positions. Version 19 adds the reason of a command that runs because kizz run --no-cache was given, to step records and to the explanations of step positions. Version 20 records explicit untraced execution and its explanation, with a distinct key and no reuse across builds.