Merge pull request #10152 from JimMoen/refine-changes

chore: refine changes for merged PRs
This commit is contained in:
JimMoen 2023-03-16 21:11:52 +08:00 committed by GitHub
commit 1688cb7df2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
19 changed files with 27 additions and 17 deletions

View File

@ -1079,11 +1079,11 @@ Supported configurations are the following:
zh: """共享订阅消息派发策略。 zh: """共享订阅消息派发策略。
- `random`:随机挑选一个共享订阅者派发; - `random`:随机挑选一个共享订阅者派发;
- `round_robin`:使用 round-robin 策略派发; - `round_robin`:使用 round-robin 策略派发;
- `round_robin_per_group`: 在共享组内循环选择下一个成员; - `round_robin_per_group`在共享组内循环选择下一个成员;
- `local`: 选择随机的本地成员,否则选择随机的集群范围内成员; - `local`选择随机的本地成员,否则选择随机的集群范围内成员;
- `sticky`:总是使用上次选中的订阅者派发,直到它断开连接; - `sticky`:总是使用上次选中的订阅者派发,直到它断开连接;
- `hash_clientid`:使用发送者的 Client ID 进行 Hash 来选择订阅者; - `hash_clientid`:使用发送者的 Client ID 进行 Hash 来选择订阅者;
- `hash_topic`: 使用源主题进行 Hash 来选择订阅者。""" - `hash_topic`使用源主题进行 Hash 来选择订阅者。"""
} }
} }

View File

@ -0,0 +1 @@
Add deb package support for `raspbian9` and `raspbian10`.

View File

@ -0,0 +1 @@
`raspbian9``raspbian10` 增加 deb 包支持。

View File

@ -0,0 +1,2 @@
When connecting with the flag `clean_start=false`, EMQX will filter out messages that published by banned clients.
Previously, the messages sent by banned clients may still be delivered to subscribers in this scenario.

View File

@ -0,0 +1,2 @@
当使用 `clean_start=false` 标志连接时EMQX 将会从消息队列中过滤出被封禁客户端发出的消息,使它们不能被下发给订阅者。
此前被封禁客户端发出的消息仍可能在这一场景下被下发给订阅者。

View File

@ -1 +1,3 @@
`/bridges` API: return `400` instead of `403` in case of inconsistency in the application logic either because bridge is about to be deleted, but active rules still depend on it, or an operation (start|stop|restart) is called, but the bridge is not enabled. Fix `/bridges` API status code.
- Return `400` instead of `403` in case of removing a data bridge that is dependent on an active rule.
- Return `400` instead of `403` in case of calling operations (start|stop|restart) when Data-Bridging is not enabled.

View File

@ -1 +1,3 @@
`/bridges` API在应用逻辑不一致的情况下返回`400'而不是`403',因为桥即将被删除,但活动规则仍然依赖于它,或者调用了一个操作(启动|停止|重新启动),但桥没有被启用。 修复 `/bridges` API 的 HTTP 状态码。
- 当删除被活动中的规则依赖的数据桥接时,将返回 `400` 而不是 `403`
- 当数据桥接未启用时,调用操作(启动|停止|重启)将返回 `400` 而不是 `403`

View File

@ -1 +1 @@
Return human readable error message for `/briges_probe` and `[/node/:node]/bridges/:id/:operation` API calls and set HTTP status code to `400` instead of `500`. Improve error messages for `/briges_probe` and `[/node/:node]/bridges/:id/:operation` API calls to make them more readable. And set HTTP status code to `400` instead of `500`.

View File

@ -1 +1 @@
`/briges_probe``[/node/:node]/bridges/:id/:operation` API 调用返回人类可读的错误信息,并将 HTTP 状态代码设置为 `400` 而不是 `500` 改进 `/briges_probe``[/node/:node]/bridges/:id/:operation` API 调用的错误信息,使之更加易读。并将 HTTP 状态代码设置为 `400` 而不是 `500`

View File

@ -1,4 +1,4 @@
Upgrade HTTP client ehttpc to `0.4.7`. Upgrade HTTP client ehttpc to `0.4.7`.
Prior to this upgrade, HTTP clients for authentication, authorization and webhook may crash Prior to this upgrade, HTTP clients for authentication, authorization and webhook may crash
if `body` is empty but content-type HTTP header is set. if `Body` is empty but `Content-Type` HTTP header is set.
For more details see [ehttpc PR#44](https://github.com/emqx/ehttpc/pull/44). For more details see [ehttpc PR#44](https://github.com/emqx/ehttpc/pull/44).

View File

@ -1,3 +1,3 @@
HTTP 客户端库 `ehttpc` 升级到 0.4.7。 HTTP 客户端库 `ehttpc` 升级到 0.4.7。
在升级前,如果 HTTP 客户端,例如 认证授权webhook 等配置中使用了content-type HTTP 头,但是没有配置 body,则可能会发生异常。 在升级前,如果 HTTP 客户端,例如 '认证'、'授权'、'WebHook' 等配置中使用了 `Content-Type` HTTP 头,但是没有配置 `Body`,则可能会发生异常。
详情见 [ehttpc PR#44](https://github.com/emqx/ehttpc/pull/44)。 详情见 [ehttpc PR#44](https://github.com/emqx/ehttpc/pull/44)。

View File

@ -1 +1,2 @@
Fix channel crash for slow clients with enhanced authentication. Fix channel crash for slow clients with enhanced authentication.
Previously, when the client was using enhanced authentication, but the Auth message was sent slowly or the Auth message was lost, the client process would crash.

View File

@ -1 +1,2 @@
修复响应较慢的客户端在使用增强认证时可能出现崩溃的问题。 修复响应较慢的客户端在使用增强认证时可能出现崩溃的问题。
此前,当客户端使用增强认证功能,但发送 Auth 报文较慢或 Auth 报文丢失时会导致客户端进程崩溃。

View File

@ -1,4 +1,4 @@
Fix problems related to manual joining of EMQX replicant nodes to the cluster. Fix problems related to manual joining of EMQX replicant nodes to the cluster.
Previously, manually joining and then leaving the cluster rendered replicant node unable to start EMQX again and required a node restart. Previously, after manually executing joining and then leaving the cluster, the `replicant` node can only run normally after restarting the node after joining the cluster again.
[Mria PR](https://github.com/emqx/mria/pull/128) [Mria PR](https://github.com/emqx/mria/pull/128)

View File

@ -1,4 +1,4 @@
修复与手动加入 EMQX `replicant` 节点到集群有关的问题。 修复 `replicant` 节点因为手动加入 EMQX 集群导致的相关问题。
以前,手动加入然后离开集群会使 `replicant` 节点无法再次启动 EMQX需要重新启动节点 此前,手动执行 `加入集群-离开集群` 后,`replicant` 节点再次加入集群后只有重启节点才能正常运行
[Mria PR](https://github.com/emqx/mria/pull/128) [Mria PR](https://github.com/emqx/mria/pull/128)

View File

@ -1 +1 @@
Integrate `DynamoDB` into `bridges` as a new backend. Add `DynamoDB` support for Data-Brdige.

View File

@ -1 +1 @@
`桥接` 中集成 `DynamoDB` 为数据桥接增加 `DynamoDB` 支持

View File

@ -1 +0,0 @@
When connecting with the flag `clean_start=false`, the new session will filter out banned messages from the `mqueue` before deliver.

View File

@ -1 +0,0 @@
当使用 `clean_start=false` 标志连接时,新会话将在传递之前从 `mqueue` 中过滤掉被封禁的消息。