Kodai Matsumoto

I have the same problem. Changing the service port to connect to from grpc to tcp solves the problem, but I don't know the root cause. This problem started occurring...

This issue may be fixed in the envoy release v1.29.3. Related - https://github.com/triton-inference-server/server/issues/6936 - https://github.com/envoyproxy/envoy/pull/32255 - https://github.com/envoyproxy/envoy/pull/33018

I was able to temporarily work around this problem by setting `runtimeValues`. ```yaml defaultConfig: runtimeValues: envoy.reloadable_features.sanitize_te: "false" ``` or ```yaml annotations: proxy.istio.io/config: | runtimeValues: envoy.reloadable_features.sanitize_te: "false" ```

This issue has been fundamentally resolved with the release of istio/proxy v1.21.1. https://github.com/istio/proxy/commit/467438722bae01ef9daf0749e1a0f1d15c96aa70

I have encountered the same problem. ~~I think you need to put this command in the README.~~ ``` $ oco config set OCO_API_URL=http://localhost:11434/api/chat ``` Sorry, it was already listed. I...

@erikgb @wallrj @SgtCoDFish Hello, could you please review this pull request? Or, if you know who would be appropriate to ask for a review, could you let me know?

@hawksight I fixed the error that was occurring in CI. Could you please run the test CI again?