-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/dev/null in action cache, remote caches, etc ( /cas/e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
)
#13349
Comments
PS: It looks like many of the AC entries for a .d file for C++ have this. For now, if anyone is looking for a mitigation without an extra proxy or file system, when adding a |
#11063 mentioned that Bazel optimized away uploading zero-sized CAS blob (sha256 = e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855) to grpc cache but it's not true for http cache. I will work the fix to skip uploading zero-sized blob to other cache backends. |
An unintended side-effect of change cc2b3ec is that zero-sized blob won't be uploaded to gRPC cache. However, the behavior is existed for a long time and the REAPI spec is also updated accordingly. This change makes the behavior explicit and brings it to other remote cache backends. Context bazelbuild#11063. Fixes bazelbuild#13349. Closes bazelbuild#13594. PiperOrigin-RevId: 384457129
An unintended side-effect of change cc2b3ec is that zero-sized blob won't be uploaded to gRPC cache. However, the behavior is existed for a long time and the REAPI spec is also updated accordingly. This change makes the behavior explicit and brings it to other remote cache backends. Context bazelbuild#11063. Fixes bazelbuild#13349. Closes bazelbuild#13594. PiperOrigin-RevId: 384457129
An unintended side-effect of change cc2b3ec is that zero-sized blob won't be uploaded to gRPC cache. However, the behavior is existed for a long time and the REAPI spec is also updated accordingly. This change makes the behavior explicit and brings it to other remote cache backends. Context bazelbuild#11063. Fixes bazelbuild#13349. Closes bazelbuild#13594. PiperOrigin-RevId: 384457129
An unintended side-effect of change cc2b3ec is that zero-sized blob won't be uploaded to gRPC cache. However, the behavior is existed for a long time and the REAPI spec is also updated accordingly. This change makes the behavior explicit and brings it to other remote cache backends. Context bazelbuild#11063. Fixes bazelbuild#13349. Closes bazelbuild#13594. PiperOrigin-RevId: 384457129
An unintended side-effect of change cc2b3ec is that zero-sized blob won't be uploaded to gRPC cache. However, the behavior is existed for a long time and the REAPI spec is also updated accordingly. This change makes the behavior explicit and brings it to other remote cache backends. Context bazelbuild#11063. Fixes bazelbuild#13349. Closes bazelbuild#13594. PiperOrigin-RevId: 384457129
An unintended side-effect of change cc2b3ecb9283ebdb297fc3fb6407f4697c850ac2 is that zero-sized blob won't be uploaded to gRPC cache. However, the behavior is existed for a long time and the REAPI spec is also updated accordingly. This change makes the behavior explicit and brings it to other remote cache backends. Context bazelbuild/bazel#11063. Fixes bazelbuild/bazel#13349. Closes #13594. PiperOrigin-RevId: 384457129
Description of the problem / feature request:
Hello! I noticed today about 100x more requests for a certian object in a remote http cache.
/cas/e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
git clone https://github.com/bazelbuild/rules_apple.git cd rules_apple bazel build examples/ios/PrenotCalculator:PrenotCalculator --disk_cache=/tmp/disk-cache --appe_platform_type=ios
What operating system are you running Bazel on?
macOS
What's the output of
bazel info release
?Happens on 3x and 4x releases, dev builds
What's the output of
git remote get-url origin ; git rev-parse master ; git rev-parse HEAD
?Have you found anything relevant by searching the web?
#11063
#6260
Any other information, logs, or outputs that you want to share?
It seems like this object is in AC entries and potentially related to runfiles / and or middlemen for thise runfiles
The text was updated successfully, but these errors were encountered: