|
Ran
|
Jobs
1
|
Files
437
|
Run time
2min
|
Badge
README BADGES
|
push
travis-ci-com
<a href="https://github.com/pantsbuild/pants/commit/<a class=hub.com/pantsbuild/pants/commit/209e9aa39d89ddf6b5b8fa27bcd46e2c21ec5927">209e9aa39<a href="https://github.com/pantsbuild/pants/commit/209e9aa39d89ddf6b5b8fa27bcd46e2c21ec5927">">Validate the names of directory children, and normalize output directory/file names (#10850) ### Problem As explained in https://github.com/pantsbuild/pants/issues/10802#issuecomment-697922102, Pants does not currently normalize `Process::{output_files,output_directories}` as relative paths, which caused us to send an [invalid path](https://github.com/bazelbuild/remote-apis/blob/</a><a class="double-link" href="https://github.com/pantsbuild/pants/commit/<a class="double-link" href="https://github.com/pantsbuild/pants/commit/f54876595da9f2c2d66c98c318d00b60fd64900b">f54876595</a>">f54876595</a><a href="https://github.com/pantsbuild/pants/commit/209e9aa39d89ddf6b5b8fa27bcd46e2c21ec5927">/build/bazel/remote/execution/v2/remote_execution.proto#L507-L508) to the server. Additionally, the server managed to return a "nearly valid" output where a child path for a directory had an empty name, which we should validate for in order to fail faster. ### Solution In two commits: 1) validate that `Directory` protos returned by remoting do not contain empty child names, 2) switch the `Process::{output_files,output_directories}` fields to holding `RelativePath`s, which are normalized to strip trailing slashes, and validated as not escaping their root. ### Result Fixes #10802. Opened https://github.com/bazelbuild/remote-apis/issues/175 to track upstreaming the additional "must be non-empty" constraint. [ci skip-build-wheels]
0 of 29486 relevant lines covered (0.0%)
0.0 hits per line