-
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
channel close should not throw a RuntimeException #9362
Comments
/cc @buchgr P1? |
From the client side we are seeing this error message:
However on server side the requests seems to be handled correctly. Our remote cache server uses the nginx + webdav approach. "access": {
"user_agent": {
"name": "Other",
"os_name": "Other",
"device": "Other",
"os": "Other",
"build": ""
},
"time_local": "11/Sep/2019:07:26:54 +0000",
"referrer": "-",
"request_time": "0.001",
"upstream_cache_status": "-",
"method": "GET",
"url": "/cache/cas/44750cbb1cbb9f3679e0c93e02906080beb984751b45e504cd88df6fa1518dc0",
"http_version": "1.1",
"body_sent": {
"bytes": "170628"
},
"remote_user": "-",
"response_code": "200"
} |
Exceptions that are reused between download futures must not be added to the suppression of themselves. Fixes bazelbuild#9362
We're seeing this issue with bazel 1.0 as well. |
Does anyone know what version this bug was introduced with? We were updating from 0.23.1 and we need to downgrade to before it was introduced |
It was introduced in Bazel 0.29.0. |
@buchgr please comment on severity of this. Patch-release worthy? |
chatted offline. agreed to do a patch release. |
Description of the problem / feature request:
We are seeing the following error:
The connection to our remote cache has been closed and we are getting this RuntimeException.
Feature requests: what underlying problem are you trying to solve with this feature?
Reliable remote cache
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
We can't reliably reproduce this bug at this point in time.
I will check if killing the connection to the remote cache triggers the bug.
What operating system are you running Bazel on?
centOS 7
Linux 847cea82af63 3.10.0-957.12.1.el7.x86_64 #1 SMP Mon Apr 29 14:59:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
What's the output of
bazel info release
?Have you found anything relevant by searching the web?
https://groups.google.com/forum/#!topic/bazel-discuss/_IpJjDm5a2w
The text was updated successfully, but these errors were encountered: