Update envoy SHA to 6/18#3387
Conversation
|
Skipping CI for Draft Pull Request. |
|
@PiotrSikora @lambdai Any idea about why centos has |
|
Add a "build --cxxopt -Wno-range-loop-analysis" around https://github.com/istio/proxy/blob/master/.bazelrc#L51-L54 ? |
I want to make it clear the -Wno-range-loop-analysis is following "--cxxopt" and NOT in |
|
I wonder if the issue is outdated compiler and a false positive warning? It's not happening on Ubuntu nor upstream. |
lambdai
left a comment
There was a problem hiding this comment.
Thanks! A few questions though
e4058c1 to
76e939d
Compare
76e939d to
e958e8a
Compare
@lambdai does not seem to work.. |
Looks like conflict args are provided and the order matters. |
Try to see if compiler update could unblock envoy sha update istio/proxy#3387
Try to see if compiler update could unblock envoy sha update istio/proxy#3387
| location->value()->string_view(), "/instances/", name); | ||
| return absl::StrCat( | ||
| "//compute.googleapis.com/projects/", | ||
| ::Wasm::Common::toAbslStringView(project->value()->string_view()), |
There was a problem hiding this comment.
nit: doesn't absl StrCat handle std::string_view natively?
There was a problem hiding this comment.
It doesn't - it supports absl::string_view, which by default is equivalent to std::string_view in C++17, but Envoy switched to non-standard null-terminated variants in envoyproxy/envoy#16029, so std::string_view is no longer supported.
There was a problem hiding this comment.
@PiotrSikora Could you clarify wrt null?
is it null-terminated or nullptr constructed?
There was a problem hiding this comment.
Good catch - nullptr-constructed.
kyessenov
left a comment
There was a problem hiding this comment.
I think Wasm needs to switch to absl string_view to make this cleaner.
Try to see if compiler update could unblock envoy sha update istio/proxy#3387
Try to see if compiler update could unblock envoy sha update istio/proxy#3387
No description provided.