mbgit2
mbgit2
This issue is marked as resolved but running ``` kubescape scan deployment.yaml --verbose -f sarif ``` still results in ``` { "version": "2.1.0", "$schema": "https://json.schemastore.org/sarif-2.1.0.json", "runs": [ { "tool": {...
Any update on this? I'm currently stuck on 1.26.4 due to this.
For us it doesn't seem fixed. We have a custom interceptor, but this now gets a complete empty (ReqT message) argument when using transcoding.
Issue: explicitly need to set json_name in proto file to enable trancoding. I've made a minimal [repo](https://github.com/mbgit2/armeria-example) that reproduces the issue. Note it is build using bazel, but with all...
Any update would be much appreciated, would this be taken into the next version?