Lines Matching +full:working +full:- +full:directory
8 font-weight: inherit;
9 font-style: inherit;
10 font-size: 100%;
11 font-family: inherit;
12 vertical-align: baseline;
16 font-size: 13px;
21 font-size: 26px;
22 margin-bottom: 1em;
26 font-size: 24px;
27 margin-bottom: 1em;
31 font-size: 20px;
32 margin-bottom: 1em;
33 margin-top: 1em;
37 line-height: 1.5;
38 font-family: Monaco, 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', 'Lucida Console', monospace;
42 margin-top: 0.5em;
46 font-family: Arial, sans serif;
50 border-bottom: solid #CCC 1px;
54 margin-top: 0.5em;
58 margin-left: 2 em;
62 margin-top: 1em;
69 font-weight: bold;
70 font-size: 14px;
97 …er MAY require use of this field to select between them in an implementation-defined fashion, othe…
98 …hash: string, The hash. In the case of SHA-256, it will always be a lowercase hex string exactly 6…
105 1 - v1 error format
106 2 - v2 error format
111 …onResult.execution_metadata.Worker`) have a non-default value, to ensure that the serialized value…
113 … Details that are specific to the kind of worker used. For example, on POSIX-like systems this cou…
130 …directory requested in the `output_directories` or `output_paths` field of the Action, if the corr…
131 …{ # An `OutputDirectory` is the output in an `ActionResult` corresponding to a directory's fu…
132 …directory relative to the working directory. The path separator is a forward slash `/`. Since this…
133 …-front (or storing the size along with the digest in every message where digests are embedded). Th…
134 …"hash": "A String", # The hash. In the case of SHA-256, it will always be a lo…
139 …working directory, if the server supports SymlinkAbsolutePathStrategy.ALLOWED. For each output dir…
140 … but it is used as an output in an `ActionResult`. `OutputSymlink` is binary-compatible with `Syml…
143 "properties": [ # A list of string-based NodeProperties.
151 …quot;A String", # The full path of the symlink relative to the working directory, including t…
152 …r is a forward slash `/`. The target path can be relative to the parent directory of the symlink o…
155 …output files, or input files, or even absolute paths outside of the working directory, if the serv…
156 … but it is used as an output in an `ActionResult`. `OutputSymlink` is binary-compatible with `Syml…
159 "properties": [ # A list of string-based NodeProperties.
167 …quot;A String", # The full path of the symlink relative to the working directory, including t…
168 …r is a forward slash `/`. The target path can be relative to the parent directory of the symlink o…
171 …after v2.1). If an output listed in `output_files` was found, but was a directory rather than a re…
174 …mplicated implementation as opposed to having the client specify the size up-front (or storing the…
175 …"hash": "A String", # The hash. In the case of SHA-256, it will always be a lo…
181 "properties": [ # A list of string-based NodeProperties.
189 …: "A String", # The full path of the file relative to the working directory, including t…
192 … to other outputs, or inputs, or even absolute paths outside of the working directory, if the serv…
193 … but it is used as an output in an `ActionResult`. `OutputSymlink` is binary-compatible with `Syml…
196 "properties": [ # A list of string-based NodeProperties.
204 …quot;A String", # The full path of the symlink relative to the working directory, including t…
205 …r is a forward slash `/`. The target path can be relative to the parent directory of the symlink o…
208 …mplicated implementation as opposed to having the client specify the size up-front (or storing the…
209 …"hash": "A String", # The hash. In the case of SHA-256, it will always be a lo…
213 …mplicated implementation as opposed to having the client specify the size up-front (or storing the…
214 …"hash": "A String", # The hash. In the case of SHA-256, it will always be a lo…
226 …er MAY require use of this field to select between them in an implementation-defined fashion, othe…
227 …hash: string, The hash. In the case of SHA-256, it will always be a lowercase hex string exactly 6…
232 …onResult.execution_metadata.Worker`) have a non-default value, to ensure that the serialized value…
234 … Details that are specific to the kind of worker used. For example, on POSIX-like systems this cou…
251 …directory requested in the `output_directories` or `output_paths` field of the Action, if the corr…
252 …{ # An `OutputDirectory` is the output in an `ActionResult` corresponding to a directory's fu…
253 …directory relative to the working directory. The path separator is a forward slash `/`. Since this…
254 …-front (or storing the size along with the digest in every message where digests are embedded). Th…
255 …"hash": "A String", # The hash. In the case of SHA-256, it will always be a lo…
260 …working directory, if the server supports SymlinkAbsolutePathStrategy.ALLOWED. For each output dir…
261 … but it is used as an output in an `ActionResult`. `OutputSymlink` is binary-compatible with `Syml…
264 "properties": [ # A list of string-based NodeProperties.
272 …quot;A String", # The full path of the symlink relative to the working directory, including t…
273 …r is a forward slash `/`. The target path can be relative to the parent directory of the symlink o…
276 …output files, or input files, or even absolute paths outside of the working directory, if the serv…
277 … but it is used as an output in an `ActionResult`. `OutputSymlink` is binary-compatible with `Syml…
280 "properties": [ # A list of string-based NodeProperties.
288 …quot;A String", # The full path of the symlink relative to the working directory, including t…
289 …r is a forward slash `/`. The target path can be relative to the parent directory of the symlink o…
292 …after v2.1). If an output listed in `output_files` was found, but was a directory rather than a re…
295 …mplicated implementation as opposed to having the client specify the size up-front (or storing the…
296 …"hash": "A String", # The hash. In the case of SHA-256, it will always be a lo…
302 "properties": [ # A list of string-based NodeProperties.
310 …: "A String", # The full path of the file relative to the working directory, including t…
313 … to other outputs, or inputs, or even absolute paths outside of the working directory, if the serv…
314 … but it is used as an output in an `ActionResult`. `OutputSymlink` is binary-compatible with `Syml…
317 "properties": [ # A list of string-based NodeProperties.
325 …quot;A String", # The full path of the symlink relative to the working directory, including t…
326 …r is a forward slash `/`. The target path can be relative to the parent directory of the symlink o…
329 …mplicated implementation as opposed to having the client specify the size up-front (or storing the…
330 …"hash": "A String", # The hash. In the case of SHA-256, it will always be a lo…
334 …mplicated implementation as opposed to having the client specify the size up-front (or storing the…
335 …"hash": "A String", # The hash. In the case of SHA-256, it will always be a lo…
341 …n time or other advantage, but the interpretation of a given value is server-dependent. A priority…
344 1 - v1 error format
345 2 - v2 error format
350 …onResult.execution_metadata.Worker`) have a non-default value, to ensure that the serialized value…
352 … Details that are specific to the kind of worker used. For example, on POSIX-like systems this cou…
369 …directory requested in the `output_directories` or `output_paths` field of the Action, if the corr…
370 …{ # An `OutputDirectory` is the output in an `ActionResult` corresponding to a directory's fu…
371 …directory relative to the working directory. The path separator is a forward slash `/`. Since this…
372 …-front (or storing the size along with the digest in every message where digests are embedded). Th…
373 …"hash": "A String", # The hash. In the case of SHA-256, it will always be a lo…
378 …working directory, if the server supports SymlinkAbsolutePathStrategy.ALLOWED. For each output dir…
379 … but it is used as an output in an `ActionResult`. `OutputSymlink` is binary-compatible with `Syml…
382 "properties": [ # A list of string-based NodeProperties.
390 …quot;A String", # The full path of the symlink relative to the working directory, including t…
391 …r is a forward slash `/`. The target path can be relative to the parent directory of the symlink o…
394 …output files, or input files, or even absolute paths outside of the working directory, if the serv…
395 … but it is used as an output in an `ActionResult`. `OutputSymlink` is binary-compatible with `Syml…
398 "properties": [ # A list of string-based NodeProperties.
406 …quot;A String", # The full path of the symlink relative to the working directory, including t…
407 …r is a forward slash `/`. The target path can be relative to the parent directory of the symlink o…
410 …after v2.1). If an output listed in `output_files` was found, but was a directory rather than a re…
413 …mplicated implementation as opposed to having the client specify the size up-front (or storing the…
414 …"hash": "A String", # The hash. In the case of SHA-256, it will always be a lo…
420 "properties": [ # A list of string-based NodeProperties.
428 …: "A String", # The full path of the file relative to the working directory, including t…
431 … to other outputs, or inputs, or even absolute paths outside of the working directory, if the serv…
432 … but it is used as an output in an `ActionResult`. `OutputSymlink` is binary-compatible with `Syml…
435 "properties": [ # A list of string-based NodeProperties.
443 …quot;A String", # The full path of the symlink relative to the working directory, including t…
444 …r is a forward slash `/`. The target path can be relative to the parent directory of the symlink o…
447 …mplicated implementation as opposed to having the client specify the size up-front (or storing the…
448 …"hash": "A String", # The hash. In the case of SHA-256, it will always be a lo…
452 …mplicated implementation as opposed to having the client specify the size up-front (or storing the…
453 …"hash": "A String", # The hash. In the case of SHA-256, it will always be a lo…