package yadcc.daemon

Get desktop application:
View/edit binary Protocol Buffers messages

Defines some meta data about a compilation cache. For the compilation result (i.e., object file), it's stored immediately after this message.

• int32 exit_code = 3

  Note that even if we cache failure result, the only exit code we should be using is 0 (success) and 1 (failure). Any other exit code likely comes from non-compilation errors.

• bytes standard_output = 1

  I'm not sure how can it happen, yet I did see some `stderr` contains non-utf8 byte sequence. So we use `bytes` instead of `string` here.

• bytes standard_error = 2

• optional google.protobuf.Any extra_info = 6

  Depending on source code language, this field may contain some extra meta information (e.g., C++ compilation cache use this field for source-path patch locations.).

• bytes files_digest = 4

  BLAKE3 of object file. This helps us to detect data corruption on network (or bug in our cache server implementation.). I'm not sure if we should use a cryptographical hash algorithm here. Given that the digest is used only to detect non-malicious data corruption, a cryptograhical hash algorithm may be a overkill?