-
Notifications
You must be signed in to change notification settings - Fork 5.1k
ssl: remove openssl threading code if using boringssl #382
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
Conversation
boringssl has internal support for threading.
@lyft/network-team @PiotrSikora |
Both: However, if you want to remove dead code, then |
I just noticed it in the coverage build so just deleting dead code. I will fix it up to include the other functions you mention. |
@PiotrSikora updated |
- Remvoe transcoding filter, which is already available at https://lyft.github.io/envoy/docs/configuration/http_filters/grpc_json_transcoder_filter.html
We don't care about it, and it's currently broken. Signed-off-by: Piotr Sikora <piotrsikora@google.com>
We don't care about it, and it's currently broken. Signed-off-by: Piotr Sikora <piotrsikora@google.com>
…161) We don't care about it, and it's currently broken. Signed-off-by: Piotr Sikora <piotrsikora@google.com>
zh-translation:docs/root/configuration/other_features/other_features.rst
envoyproxy/envoy-mobile#381 surfaced an issue where extensions aren't allowed on Swift protocols that are visible to Objective-C. This meant that the Swift `Client` protocol (conformed to by the `Envoy` Swift class) could not provide a default implementation of the non-streaming `send` function, and the function had to be moved into the concrete `Envoy` class so that it could be visible from both Swift and Objective-C. This ended up breaking our Swift tests in `ClientTests.swift` (as mentioned in that PR's description). In order to fix these tests, we need to convert `EnvoyHTTPStream` into a protocol and use an `EnvoyHTTPStreamImpl` concrete type - similarly to how we do with `EnvoyEngine`/`EnvoyEngineImpl`. This PR updates the types accordingly, and fixes the tests. Also renames the tests to `EnvoyTests` rather than `ClientTests` since this is testing the concrete type. Signed-off-by: Michael Rebello <me@michaelrebello.com> Signed-off-by: JP Simard <jp@jpsim.com>
envoyproxy/envoy-mobile#381 surfaced an issue where extensions aren't allowed on Swift protocols that are visible to Objective-C. This meant that the Swift `Client` protocol (conformed to by the `Envoy` Swift class) could not provide a default implementation of the non-streaming `send` function, and the function had to be moved into the concrete `Envoy` class so that it could be visible from both Swift and Objective-C. This ended up breaking our Swift tests in `ClientTests.swift` (as mentioned in that PR's description). In order to fix these tests, we need to convert `EnvoyHTTPStream` into a protocol and use an `EnvoyHTTPStreamImpl` concrete type - similarly to how we do with `EnvoyEngine`/`EnvoyEngineImpl`. This PR updates the types accordingly, and fixes the tests. Also renames the tests to `EnvoyTests` rather than `ClientTests` since this is testing the concrete type. Signed-off-by: Michael Rebello <me@michaelrebello.com> Signed-off-by: JP Simard <jp@jpsim.com>
boringssl has internal support for threading.