microservices

expected result:
example.com?param=abc -> will become example.com
example.com/?param=abc -> will stay example.com/

actual result:
example.com?param=abc -> become example.com
example.com/?param=abc -> stays example.com/?param=abc

In what area(s)?

/area runtime

What version of Dapr?

dapr --version
CLI version: 1.7.0
Runtime version: 1.7.0

Expected Behavior

API methods to be logged without any errors

Actual Behavior

When I start my dapr actor host application like this:

dapr run --app-id myapp --app-port 5000 --dapr-http-port 3500 --log-level debug --enable-api-logging -- dotnet run

Feature Suggestion

Possible Implementation

Background

目前使用qiankun2.x的版本，业务提出需求在发布新的版本时候，期望可以不刷新页面（主应用暂时不考虑）进行该系统的热重载。类似于pc端的热更新，期望qiankun可以导出unload方法，完全销毁app的生命周期，业务系统再次将其重载。

Proposal

1. 翻看源码发现不能热更新的原因是因为import-html-entry中缓存了 embedHTMLCache
2. qiankun在importEntry时，如果已经获取过html资源，每次获取的都是内存中的html，以至于script & style也是缓存的
3. 我的解决方案是，在import-html-entry中导出根据app去清除缓存的钩子函数
4. 在qiankun中包裹其方法，根据single-spa的appStatus进行卸载应用

Maybe new warnings after upgrading ErrorProne in #3355.

/home/runner/work/jib/jib/jib-core/src/main/java/com/google/cloud/tools/jib/image/json/JsonToImageTranslator.java:250: warning: [UnrecognisedJavadocTag] This Javadoc tag wasn't recognised by the parser. Is it malformed somehow, perhaps with mismatched braces?
58

59
   * Converts a map of volumes strings to a set of {@link Absolut

Description

I'm using grpc-transcode plugin to manage gRPC<=> HTTP, It would be great to convert grpc-status-details-bin in header to HTTP response body in case an error from the upstream.

Decoded grpc-status-details-bin :
![Screens

Sometimes it might be handy to easily get a header's value as int, where validation errors would automatically result in an HTTP 400, along the lines of req.get_header_as_datetime & [req.get_param_as_int](https://falcon.readthedocs.io/en/stable/api/request_and_response_wsgi.ht

On contexts with many APIs and APIs calling other APIs in chains, having too many spans in the zipkin/jaeger dashboards may lead to a too complex usage of such dashboards and of not necessary big data volumes.

For Tyk's admin team, the steps representing the time spent in each Tyk middleware are much valuable.

But the upstream APIs teams just want to know the global time spent in Tyk interna