Daniel Strobusch
Daniel Strobusch
btw. pythons `memoryview` uses tuples for strides and shapes as well: ``` memoryview(np.ones(2)).shape (2,) memoryview(np.ones(2)).strides (8,) ``` see also #320
> Not following; it looks like you are converting the bfloat16 weights to float32, and saving them as float32. At what point do you convert them back to bfloat16? @vgoklani...
@tyxia thank you for this hint. I wouldn't expect envoy to merge herders, as this would be inconsistent with the behavior of `allowed_upstream_headers_to_append`. With this option, I get both headers...
I have reviewed the documentation, but I find it somewhat ambiguous. From my point of view, it should refer to the merge behavior of the client's original request headers and...
Ok, let me try to summarize. The current behavior of `allowed_upstream_headers` is: ```mermaid graph TB subgraph client [client request headers] c1[foo-bar: client1] c2[foo-bar: client2] end subgraph authz [authz response headers]...
@tyxia as far as I can see there is no way to configure `headers_to_remove` on external authz. This seems to be used internally, only. The way we workaround this, is...
@tyxia interesting, seems to be an undocumented feature (?). I was able to remove the headers by setting `x-envoy-auth-headers-to-remove: foo-bar`. However, it removes all the headers, which does not surprise...
I can report the same issue after upgrading to Grafana 11. The request that is failing is ``` https://***/grafana/api/prometheus/grafana/api/v1/rules?dashboard_uid=container-restarts ``` The response is `{"message":"Not found"}`. Grafana logs on debug level...
Some local testing shows the following API behavior: ``` [unified_alerting] enabled = true ``` gives ``` curl -X GET --location "http://localhost:3000/grafana/api/prometheus/grafana/api/v1/rules" -H "Accept: application/json" -H "Content-Type: application/json" -H "Authorization: basic...