| Age | Commit message (Collapse) | Author |
|---|
|
|
|
...in creating Git tree from filesystem directory.
(cherry-picked from 6b31a88acbe6a6556e36f838b914a82879949811)
|
|
(cherry-picked from cf33c43c8b12d39d0a6b3751db3f58a9895cd41d)
|
|
... and do mark artifacts internally as synchronized. First all all,
we will abort anyway, to the entry won't even be read and, secondly
it is not necessarily true that the artifact is synchronized.
(cherry-picked from d1dc5cce32ba20c0dae13aecf63e88fe8ead899f)
|
|
When backing up target-cache entries we use parallelism at two
dimensions, the independent cache entries and for each entry we
retrieve the artifacts in parallel. If for each dimension we use
the full amount of parallelism allowed, that gives a number of
threads up to the square of the amount of parallelism specified by
the user. Therefore, use in each dimension only the square root
of the allowed parallelism keeping the total parallelism (up to
rounding) within the specified range.
(cherry-picked from f4e9de93b50fe8135d378830577cda687cae28ee)
|
|
...in all return paths, including in reporting caught exceptions.
In this way give the opportunity for any calling AsyncMap to
receive an expected fatal logger call on failure and thus be able
to shut down gracefully. This is in line with the AsyncMap design,
where the loggers are assumed to be safe to call by a consumer.
(cherry-picked from ae33d0f287e83769dbef9287e64006e1c0c463e9)
|
|
|
|
|
|
(cherry-picked from fe4006fce755432b1ae3a273873f3649512c7f94)
|
|
(cherry-picked from fe11e1cc49ed46b1837336df33fb0805668905a6)
|
|
For a generic rule, it is an error if map union of various
inputs (overlayed in correct order) does not form a proper stage. To
implement this check properly, we first have to construct the map of
all inputs and only then perform the staging check and not do the check
with only the runfiles, as 5e104a526cf76fe75312d2fd288a3c88f506fb0a
accidentally did. Fix this.
(cherry-picked from f249a220913f4421c58c9c6251e4f3dce67e251c)
|
|
|
|
|
|
The built-in rule "tree" does not support the field "data". Hence
remove it from the list of white-listed fields so that an appropriate
warning is issued if it occurs for that rule.
(cherry-picked from 1324f45fa7b1938b39854f7b38d981c238da2fbc)
|
|
The serve service can be asked to get a tree root from the designated
remote-execution endpoint. Speed this process up by going through local
CAS; in this way,
- identical blobs are fetched only once, and
- the fetching happens in parallel.
(cherry-picked from 360ddbb0285554c936d5eaa95460d5aad3e13b1e)
|
|
(cherry-picked from 241ccadfc5b9bcebbbd5f41c96eda6b0d208a390)
|
|
(cherry-picked from 5e24dd0fc5e255d094a3d78e8e1b64a202c1e7a4)
|
|
... by using the write-rename dance. This allows processes
waiting for pid or similar files to rely on the information
being available as soon as the file is available.
(cherry-picked from 1efdbe20d506990028caccbfbc7fd241b5a01a99)
|
|
|
|
|
|
... instead of reporting an error, although not being fatal.
|
|
|
|
Do not emit errors when it does not lead to build failures. Callers
handle the log level at which failures of this method should be
logged.
|
|
|
|
|
|
|
|
...in order to avoid copying while uploading.
|
|
|
|
...and remove an unused method.
|
|
|
|
...to remove code duplication.
|
|
|
|
|
|
|
|
|
|
...since ArtifactBlob rehashes data on construction and guarantees that the digest matches the content.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
To properly use `just serve`, both the client and the serve instance
must talk to the very same execution endpoint. Typically, both the
client and serve can reach out to the execution endpoint via the same
IP address. However, it might be possible that the client and a serve
instance know the same execution endpoint by means of differnet IP
addresses. For example, the client knows the execution endpoint
address through an _external_ IP address, while the serve instance,
deployed within the same network infrastructure, only knows the
_internal_ IP address.
This patch adds the subkey `"client address"` -- of the key
`"execution endpoint"` -- in the serve configuration file, to specify
the alternative pair `address:port` used by the client.
|
|
|
|
|
|
|
