Age | Commit message (Collapse) | Author |
|
|
|
|
|
...to prevent additional conversions to ArtifactDigest from plain strings.
|
|
Also switch to using the fields from RemoteContext instances
instead of those from ApiBundle.
|
|
|
|
|
|
...to properly fallback to local api if needed.
|
|
...instead of using singleton calls.
|
|
|
|
If the serve endpoint reports an internal error, local builds
should not continue and the error message should be provided.
Similarly, if the serve endpoint promises the target cache value to
be in remote CAS, but the client cannot find or process it as
needed, then a local build again should not continue and the reason
be provided as an error message.
|
|
...by increasing granularity in client-side reporting. This allows
to correctly continue with builds of local targets if the serve
endpoint does not have the requested target, as well as improve
the reporting for users on failure.
|
|
Some of the more specific issues addressed:
- missing log_level target/include
- header-only libs wrongly marking deps as private
- missing/misplaced gsl includes
|
|
The just serve client-side and API methods, as well as just-mr
utilities should use the noexcept specifier.
|
|
|
|
|
|
With the introduction of 'just serve', export targets can now be
built also independently from one another based on their
corresponding minimal repository configuration, as stored in the
target cache key.
In this context, this commit changes the RepositoryConfig usage
from one global (static) instance to pointers passed as necessary
throughout the code.
|
|
Co-authored-by: Alberto Sartori <alberto.sartori@huawei.com>
|