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;
103 between them in an implementation-defined fashion, otherwise it can be
105 hash: string, The hash. In the case of SHA-256, it will always be a lowercase hex string
117 1 - v1 error format
118 2 - v2 error format
139 # outside of the working directory, if the server supports
155 # `OutputSymlink` is binary-compatible with `SymlinkNode`.
156 …"path": "A String", # The full path of the symlink relative to the working directory, including the
160 # The target path can be relative to the parent directory of the symlink or
171 # SHOULD use SHA-256.
183 # up-front (or storing the size along with the digest in every message where
202 … "hash": "A String", # The hash. In the case of SHA-256, it will always be a lowercase hex string
219 # SHOULD use SHA-256.
231 # up-front (or storing the size along with the digest in every message where
250 … "hash": "A String", # The hash. In the case of SHA-256, it will always be a lowercase hex string
259 # If an output of the same name was found, but was a directory rather
268 … "path": "A String", # The full path of the file relative to the working directory, including the
279 # SHOULD use SHA-256.
291 # up-front (or storing the size along with the digest in every message where
310 … "hash": "A String", # The hash. In the case of SHA-256, it will always be a lowercase hex string
317 # directories, or even absolute paths outside of the working directory,
320 # For each output directory requested in the `output_directories` field of
321 # the Action, if the directory existed after the action completed, a
323 # `output_directories` field, if the directory was not a symbolic link.
326 # instead of a directory, the server will return a FAILED_PRECONDITION.
334 # `OutputSymlink` is binary-compatible with `SymlinkNode`.
335 …"path": "A String", # The full path of the symlink relative to the working directory, including the
339 # The target path can be relative to the parent directory of the symlink or
346 … "outputDirectories": [ # The output directories of the action. For each output directory requested
348 # directory existed after the action completed, a single entry will be
351 # directory tree, and the path equal exactly to the corresponding Action
354 # As an example, suppose the Action had an output directory `a/b/dir` and the
356 # and a directory named `foo` with an executable file named `baz`. Then,
391 # // (Directory proto with hash "4cf2eda940..." and size 43)
405 # If an output of the same name was found, but was not a directory, the
408 # directory's full contents rather than a single file.
409 … "path": "A String", # The full path of the directory relative to the working directory. The path
412 # and it denotes the entire working directory.
415 # directory's contents.
417 # SHOULD use SHA-256.
429 # up-front (or storing the size along with the digest in every message where
448 … "hash": "A String", # The hash. In the case of SHA-256, it will always be a lowercase hex string
480 between them in an implementation-defined fashion, otherwise it can be
482 hash: string, The hash. In the case of SHA-256, it will always be a lowercase hex string
504 # outside of the working directory, if the server supports
520 # `OutputSymlink` is binary-compatible with `SymlinkNode`.
521 …"path": "A String", # The full path of the symlink relative to the working directory, including the
525 # The target path can be relative to the parent directory of the symlink or
536 # SHOULD use SHA-256.
548 # up-front (or storing the size along with the digest in every message where
567 … "hash": "A String", # The hash. In the case of SHA-256, it will always be a lowercase hex string
584 # SHOULD use SHA-256.
596 # up-front (or storing the size along with the digest in every message where
615 … "hash": "A String", # The hash. In the case of SHA-256, it will always be a lowercase hex string
624 # If an output of the same name was found, but was a directory rather
633 … "path": "A String", # The full path of the file relative to the working directory, including the
644 # SHOULD use SHA-256.
656 # up-front (or storing the size along with the digest in every message where
675 … "hash": "A String", # The hash. In the case of SHA-256, it will always be a lowercase hex string
682 # directories, or even absolute paths outside of the working directory,
685 # For each output directory requested in the `output_directories` field of
686 # the Action, if the directory existed after the action completed, a
688 # `output_directories` field, if the directory was not a symbolic link.
691 # instead of a directory, the server will return a FAILED_PRECONDITION.
699 # `OutputSymlink` is binary-compatible with `SymlinkNode`.
700 …"path": "A String", # The full path of the symlink relative to the working directory, including the
704 # The target path can be relative to the parent directory of the symlink or
711 … "outputDirectories": [ # The output directories of the action. For each output directory requested
713 # directory existed after the action completed, a single entry will be
716 # directory tree, and the path equal exactly to the corresponding Action
719 # As an example, suppose the Action had an output directory `a/b/dir` and the
721 # and a directory named `foo` with an executable file named `baz`. Then,
756 # // (Directory proto with hash "4cf2eda940..." and size 43)
770 # If an output of the same name was found, but was not a directory, the
773 # directory's full contents rather than a single file.
774 … "path": "A String", # The full path of the directory relative to the working directory. The path
777 # and it denotes the entire working directory.
780 # directory's contents.
782 # SHOULD use SHA-256.
794 # up-front (or storing the size along with the digest in every message where
813 … "hash": "A String", # The hash. In the case of SHA-256, it will always be a lowercase hex string
823 but the interpretation of a given value is server-dependent. A priority of
831 1 - v1 error format
832 2 - v2 error format
853 # outside of the working directory, if the server supports
869 # `OutputSymlink` is binary-compatible with `SymlinkNode`.
870 …"path": "A String", # The full path of the symlink relative to the working directory, including the
874 # The target path can be relative to the parent directory of the symlink or
885 # SHOULD use SHA-256.
897 # up-front (or storing the size along with the digest in every message where
916 … "hash": "A String", # The hash. In the case of SHA-256, it will always be a lowercase hex string
933 # SHOULD use SHA-256.
945 # up-front (or storing the size along with the digest in every message where
964 … "hash": "A String", # The hash. In the case of SHA-256, it will always be a lowercase hex string
973 # If an output of the same name was found, but was a directory rather
982 … "path": "A String", # The full path of the file relative to the working directory, including the
993 # SHOULD use SHA-256.
1005 # up-front (or storing the size along with the digest in every message where
1024 … "hash": "A String", # The hash. In the case of SHA-256, it will always be a lowercase hex string
1031 # directories, or even absolute paths outside of the working directory,
1034 # For each output directory requested in the `output_directories` field of
1035 # the Action, if the directory existed after the action completed, a
1037 # `output_directories` field, if the directory was not a symbolic link.
1040 # instead of a directory, the server will return a FAILED_PRECONDITION.
1048 # `OutputSymlink` is binary-compatible with `SymlinkNode`.
1049 …"path": "A String", # The full path of the symlink relative to the working directory, including the
1053 # The target path can be relative to the parent directory of the symlink or
1060 … "outputDirectories": [ # The output directories of the action. For each output directory requested
1062 # directory existed after the action completed, a single entry will be
1065 # directory tree, and the path equal exactly to the corresponding Action
1068 # As an example, suppose the Action had an output directory `a/b/dir` and the
1070 # and a directory named `foo` with an executable file named `baz`. Then,
1105 # // (Directory proto with hash "4cf2eda940..." and size 43)
1119 # If an output of the same name was found, but was not a directory, the
1122 # directory's full contents rather than a single file.
1123 … "path": "A String", # The full path of the directory relative to the working directory. The path
1126 # and it denotes the entire working directory.
1129 # directory's contents.
1131 # SHOULD use SHA-256.
1143 # up-front (or storing the size along with the digest in every message where
1162 … "hash": "A String", # The hash. In the case of SHA-256, it will always be a lowercase hex string