Merge envoy-wasm for v1.13.0.#2631
Conversation
Signed-off-by: John Plevyak <jplevyak@gmail.com>
|
There's a crash in WasmHandle destructor. |
|
There are a number of changes in the underlying envoy repository that I am not familiar with. |
|
It looks like a Wasm specific crash: |
|
You also need to re-generate Wasm files here I think. |
Signed-off-by: John Plevyak <jplevyak@gmail.com>
Signed-off-by: John Plevyak <jplevyak@gmail.com>
Signed-off-by: John Plevyak <jplevyak@gmail.com>
| # 1. Determine SHA256 `wget https://github.com/envoyproxy/envoy-wasm/archive/$COMMIT.tar.gz && sha256sum $COMMIT.tar.gz` | ||
| # 2. Update .bazelversion, envoy.bazelrc and .bazelrc if needed. | ||
| # | ||
| # envoy-wasm commit date: 12/19/19 |
There was a problem hiding this comment.
Per the text above, you still need to update .bazelversion to 2.0.0.
|
I kicked off the build on my latop for the macOS, to make sure we don't release from a broken thing. |
Signed-off-by: John Plevyak <jplevyak@gmail.com>
|
@PiotrSikora @jplevyak I'd like to get envoyproxy/envoy-wasm#345 in. I can send a follow-up SHA bump or you can include it here. |
|
Btw I assume the crash was due to ABI change. Should I file an issue to harden host once more, since it's likely to happen someone is going to run mis-matched Wasm file anyways? |
|
Kuat, do we need that for the release? It isn't currently used AFAICT |
|
We should probably just get this one in. |
|
I think so. Why not? It's fairly self-contained from the rest. I can make a plugin PR to use it quickly, since I was waiting for it to make through. It would be nice to test out de-coupling plugin release from envoy release actually. |
|
Yes, sorry, still waiting for one of the macOS builds to finish (either on CircleCI or my laptop, whichever is first). |
Signed-off-by: John Plevyak jplevyak@gmail.com