Merge pull request #10175 from zmstone/0320-cleanup-old-changelog-files
0320 cleanup old changelog files
This commit is contained in:
Zaiming (Stone) Shi
GitHub
commit
affb781c80
|
|
@ -1 +0,0 @@
|
|||
Add low level tuning settings for QUIC listeners.
|
||||
|
|
@ -1 +0,0 @@
|
|||
为 QUIC 监听器添加更多底层调优选项。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Start releasing Rocky Linux 9 (compatible with Enterprise Linux 9) and MacOS 12 packages
|
||||
|
|
@ -1 +0,0 @@
|
|||
开始发布Rocky Linux 9（与Enterprise Linux 9兼容）和MacOS 12软件包。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Errors returned by rule engine API are formatted in a more human readable way rather than dumping the raw error including the stacktrace.
|
||||
|
|
@ -1 +0,0 @@
|
|||
规则引擎 API 返回用户可读的错误信息而不是原始的栈追踪信息。
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
Add `extraVolumeMounts` to EMQX Helm Chart, it will have the ability to mount the user-own files into the EMQX instance, for example, ACL rule files as mentioned in [#9052](https://github.com/emqx/emqx/issues/9052)
|
||||
|
||||
Done of [#10116](https://github.com/emqx/emqx/issues/10116)
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
将 `extraVolumeMounts` 添加到 EMQX Helm Chart 中，它将能够挂载用户自己的文件到 EMQX 实例中，例如在 [#9052](https://github.com/emqx/emqx/issues/9052) 中提到的 ACL 规则文件。
|
||||
|
||||
完成了 [#10116](https://github.com/emqx/emqx/issues/10116)
|
||||
|
|
@ -1 +0,0 @@
|
|||
Add pod disruption budget to helm chart
|
||||
|
|
@ -1 +0,0 @@
|
|||
在 Helm chart 中添加干扰预算 (disruption budget)。
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
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.
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
当使用 `clean_start=false` 标志连接时，EMQX 将会从消息队列中过滤出被封禁客户端发出的消息，使它们不能被下发给订阅者。
|
||||
此前被封禁客户端发出的消息仍可能在这一场景下被下发给订阅者。
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
QUIC transport Multistreams support and QUIC TLS cacert support.
|
||||
|
||||
|
|
@ -1 +0,0 @@
|
|||
QUIC 传输多流支持和 QUIC TLS cacert 支持。
|
||||
|
|
@ -1 +0,0 @@
|
|||
For helm charts, add MQTT ingress bridge; and removed stale `mgmt` references.
|
||||
|
|
@ -1 +0,0 @@
|
|||
在 helm chart 中新增了 MQTT 桥接 ingress 的配置参数；并删除了旧版本遗留的 `mgmt` 配置。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Validate `bytes` param to `GET /trace/:name/log` to not exceed signed 32bit integer.
|
||||
|
|
@ -1 +0,0 @@
|
|||
验证 `GET /trace/:name/log` 的 `bytes` 参数，使其不超过有符号的32位整数。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Fix return type structure for error case in API schema for `/gateways/:name/clients`.
|
||||
|
|
@ -1 +0,0 @@
|
|||
修复 API `/gateways/:name/clients` 返回值的类型结构错误。
|
||||
|
|
@ -1 +0,0 @@
|
|||
In dashboard API for `/monitor(_current)/nodes/:node` return `404` instead of `400` if node does not exist.
|
||||
|
|
@ -1 +0,0 @@
|
|||
如果 API 查询的节点不存在，将会返回 404 而不再是 400。
|
||||
|
|
@ -1,7 +0,0 @@
|
|||
To prevent errors caused by an incorrect EMQX node cookie provided from an environment variable,
|
||||
we have implemented a fail-fast mechanism.
|
||||
Previously, when an incorrect cookie was provided, the command would still attempt to ping the node,
|
||||
leading to the error message 'Node xxx not responding to pings'.
|
||||
With the new implementation, if a mismatched cookie is detected,
|
||||
a message will be logged to indicate that the cookie is incorrect,
|
||||
and the command will terminate with an error code of 1 without trying to ping the node.
|
||||
|
|
@ -1,4 +0,0 @@
|
|||
在 cookie 给错时，快速失败。
|
||||
在此修复前，即使 cookie 配置错误，emqx 命令仍然会尝试去 ping EMQX 节点，
|
||||
并得到一个 "Node xxx not responding to pings" 的错误。
|
||||
修复后，如果发现 cookie 不一致，立即打印不一致的错误信息并退出。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Fix bridge metrics when running in async mode with batching enabled (`batch_size` > 1).
|
||||
|
|
@ -1 +0,0 @@
|
|||
修复使用异步和批量配置的桥接计数不准确的问题。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Fix error message when the target node of `emqx_ctl cluster join` command is not running.
|
||||
|
|
@ -1 +0,0 @@
|
|||
修正当`emqx_ctl cluster join`命令的目标节点未运行时的错误信息。
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Allow setting node name from `EMQX_NODE__NAME` when running in docker.
|
||||
Prior to this fix, only `EMQX_NODE_NAME` is allowed.
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
在 docker 中启动时，允许使用 `EMQX_NODE__NAME` 环境变量来配置节点名。
|
||||
在此修复前，只能使 `EMQX_NODE_NAME`。
|
||||
|
|
@ -1 +0,0 @@
|
|||
When resources on some nodes in the cluster are still in the 'initializing/connecting' state, the `bridges/` API will crash due to missing Metrics information for those resources. This fix will ignore resources that do not have Metrics information.
|
||||
|
|
@ -1 +0,0 @@
|
|||
当集群中某些节点上的资源仍处于 '初始化/连接中' 状态时，`bridges/` API 将由于缺少这些资源的 Metrics 信息而崩溃。此修复后将忽略没有 Metrics 信息的资源。
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Fix Swagger API doc rendering crash.
|
||||
In version 5.0.18, a bug was introduced that resulted in duplicated field names in the configuration schema. This, in turn, caused the Swagger schema generated to become invalid.
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
修复 Swagger API 文档渲染崩溃。
|
||||
在版本 5.0.18 中，引入了一个错误，导致配置 schema 中出现了重复的配置名称，进而导致生成了无效的 Swagger spec。
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
For influxdb bridge, added integer value placeholder annotation hint to `write_syntax` documentation.
|
||||
Also supported setting a constant value for the `timestamp` field.
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
为 influxdb 桥接的配置项 `write_syntax` 描述文档增加了类型标识符的提醒。
|
||||
另外在配置中支持 `timestamp` 使用一个常量。
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
Improve behavior of the `replicant` nodes when the `core` cluster becomes partitioned (for example when a core node leaves the cluster).
|
||||
Previously, the replicant nodes were unable to rebalance connections to the core nodes, until the core cluster became whole again.
|
||||
This was indicated by the error messages: `[error] line: 182, mfa: mria_lb:list_core_nodes/1, msg: mria_lb_core_discovery divergent cluster`.
|
||||
|
||||
[Mria PR](https://github.com/emqx/mria/pull/123/files)
|
||||
|
|
@ -1,6 +0,0 @@
|
|||
改进 `core` 集群被分割时 `replicant`节点的行为。
|
||||
修复前，如果 `core` 集群分裂成两个小集群（例如一个节点离开集群）时，`replicant` 节点无法重新平衡与核心节点的连接，直到核心集群再次变得完整。
|
||||
这种个问题会导致 replicant 节点出现如下日志：
|
||||
`[error] line: 182, mfa: mria_lb:list_core_nodes/1, msg: mria_lb_core_discovery divergent cluster`。
|
||||
|
||||
[Mria PR](https://github.com/emqx/mria/pull/123/files)
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
Fixed two bugs introduced in v5.0.18.
|
||||
* The environment varialbe `SSL_DIST_OPTFILE` was not set correctly for non-boot commands.
|
||||
* When cookie is overridden from environment variable, EMQX node is unable to start.
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
修复 v5.0.18 引入的 2 个bug。
|
||||
* 环境变量 `SSL_DIST_OPTFILE` 的值设置错误导致节点无法为 Erlang distribution 启用 SSL。
|
||||
* 当节点的 cookie 从环境变量重载 （而不是设置在配置文件中时），节点无法启动的问题。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Fix node information formatter for stopped nodes in the cluster. The bug was introduced by v5.0.18.
|
||||
|
|
@ -1 +0,0 @@
|
|||
修复集群中已停止节点的信息序列化问题，该错误由 v5.0.18 引入。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Ensure Bridge API returns `404` status code consistently for resources that don't exist.
|
||||
|
|
@ -1 +0,0 @@
|
|||
确保 Bridge API 对不存在的资源一致返回 `404` 状态代码。
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
Improve daemon mode startup failure logs.
|
||||
|
||||
Before this change, it was difficult for users to understand the reason for EMQX 'start' command failed to boot the node.
|
||||
The only information they received was that the node did not start within the expected time frame,
|
||||
and they were instructed to boot the node with 'console' command in the hope of obtaining some logs.
|
||||
However, the node might actually be running, which could cause 'console' mode to fail for a different reason.
|
||||
|
||||
With this new change, when daemon mode fails to boot, a diagnosis is issued. Here are the possible scenarios:
|
||||
|
||||
* If the node cannot be found from `ps -ef`, the user is instructed to find information in log files `erlang.log.*`.
|
||||
* If the node is found to be running but not responding to pings, the user is advised to check if the host name is resolvable and reachable.
|
||||
* If the node is responding to pings, but the EMQX app is not running, it is likely a bug. In this case, the user is advised to report a Github issue.
|
||||
|
|
@ -1,11 +0,0 @@
|
|||
优化 EMQX daemon 模式启动启动失败的日志。
|
||||
|
||||
在进行此更改之前，当 EMQX 用 `start` 命令启动失败时，用户很难理解出错的原因。
|
||||
所知道的仅仅是节点未能在预期时间内启动，然后被指示以 `console` 式引导节点以获取一些日志。
|
||||
然而，节点实际上可能正在运行，这可能会导致 `console` 模式因不同的原因而失败。
|
||||
|
||||
此次修复后，启动脚本会发出诊断：
|
||||
|
||||
* 如果无法从 `ps -ef` 中找到节点，则指示用户在 `erlang.log.*` 中查找信息。
|
||||
* 如果发现节点正在运行但不响应 ping，则建议用户检查节点主机名是否有效并可达。
|
||||
* 如果节点响应 ping 但 EMQX 应用程序未运行，则很可能是一个错误。在这种情况下，建议用户报告一个Github issue。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Fix the problem that the obfuscated password is used when using the `/bridges_probe` API to test the connection in Data-Bridge.
|
||||
|
|
@ -1 +0,0 @@
|
|||
修复数据桥接中使用 `/bridges_probe` API 进行测试连接时密码被混淆的问题。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Fix `mqtt.max_awaiting_rel` change does not work.
|
||||
|
|
@ -1 +0,0 @@
|
|||
修复 `mqtt.max_awaiting_rel` 更新不生效问题。
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
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.
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
修复 `/bridges` API 的 HTTP 状态码。
|
||||
- 当删除被活动中的规则依赖的数据桥接时，将返回 `400` 而不是 `403` 。
|
||||
- 当数据桥接未启用时，调用操作（启动|停止|重启）将返回 `400` 而不是 `403`。
|
||||
|
|
@ -1,7 +0,0 @@
|
|||
Deprecate unused QUIC TLS options.
|
||||
Only following TLS options are kept for the QUIC listeners:
|
||||
|
||||
- cacertfile
|
||||
- certfile
|
||||
- keyfile
|
||||
- verify
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
废弃未使用的 QUIC TLS 选项。
|
||||
QUIC 监听器只保留以下 TLS 选项:
|
||||
|
||||
- cacertfile
|
||||
- certfile
|
||||
- keyfile
|
||||
- verify
|
||||
|
||||
|
|
@ -1 +0,0 @@
|
|||
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`.
|
||||
|
|
@ -1 +0,0 @@
|
|||
改进 `/briges_probe` 和 `[/node/:node]/bridges/:id/:operation` API 调用的错误信息，使之更加易读。并将 HTTP 状态代码设置为 `400` 而不是 `500`。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Check if type in `PUT /authorization/sources/:type` matches `type` given in body of request.
|
||||
|
|
@ -1 +0,0 @@
|
|||
检查 `PUT /authorization/sources/:type` 中的类型是否与请求正文中的 `type` 相符。
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Fix webhook bridge error handling: connection timeout should be a retriable error.
|
||||
Prior to this fix, connection timeout was classified as unrecoverable error and led to request being dropped.
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
修复 HTTP 桥接的一个异常处理：连接超时错误发生后，发生错误的请求可以被重试。
|
||||
在此修复前，连接超时后，被当作不可重试类型的错误处理，导致请求被丢弃。
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Fix an issue that invalid QUIC listener setting could casue segfault.
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
修复了无效的 QUIC 监听器设置可能导致 segfault 的问题。
|
||||
|
||||
|
|
@ -1 +0,0 @@
|
|||
Fix description of `shared_subscription_strategy`.
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
修正对 `shared_subscription_strategy` 的描述。
|
||||
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
Fix problem when joining core nodes running different EMQX versions into a cluster.
|
||||
|
||||
[Mria PR](https://github.com/emqx/mria/pull/127)
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
修正将运行不同 EMQX 版本的核心节点加入集群的问题。
|
||||
|
||||
[Mria PR](https://github.com/emqx/mria/pull/127)
|
||||
|
|
@ -1 +0,0 @@
|
|||
Consistently return `404` for all requests on non existent source in `/authorization/sources/:source[/*]`.
|
||||
|
|
@ -1 +0,0 @@
|
|||
如果向 `/authorization/sources/:source[/*]` 请求的 `source` 不存在，将一致地返回 `404`。
|
||||
|
|
@ -1,4 +0,0 @@
|
|||
Upgrade HTTP client ehttpc to `0.4.7`.
|
||||
Prior to this upgrade, HTTP clients for authentication, authorization and webhook may crash
|
||||
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).
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
HTTP 客户端库 `ehttpc` 升级到 0.4.7。
|
||||
在升级前，如果 HTTP 客户端，例如 '认证'、'授权'、'WebHook' 等配置中使用了 `Content-Type` HTTP 头，但是没有配置 `Body`，则可能会发生异常。
|
||||
详情见 [ehttpc PR#44](https://github.com/emqx/ehttpc/pull/44)。
|
||||
|
|
@ -1 +0,0 @@
|
|||
A crash with an error in the log file that happened when the MongoDB authorization module queried the database has been fixed.
|
||||
|
|
@ -1 +0,0 @@
|
|||
当MongoDB授权模块查询数据库时，在日志文件中发生的崩溃与错误已经被修复。
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
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.
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
修复响应较慢的客户端在使用增强认证时可能出现崩溃的问题。
|
||||
此前，当客户端使用增强认证功能，但发送 Auth 报文较慢或 Auth 报文丢失时会导致客户端进程崩溃。
|
||||
|
|
@ -1,9 +0,0 @@
|
|||
For operations on `bridges API` if `bridge-id` is unknown we now return `404`
|
||||
instead of `400`. Also a bug was fixed that caused a crash if that was a node
|
||||
operation. Additionally we now also check if the given bridge is enabled when
|
||||
doing the cluster operation `start` . Affected endpoints:
|
||||
* [cluster] `/bridges/:id/:operation`,
|
||||
* [node] `/nodes/:node/bridges/:id/:operation`, where `operation` is one of
|
||||
`[start|stop|restart]`.
|
||||
Moreover, for a node operation, EMQX checks if node name is in our cluster and
|
||||
return `404` instead of `501`.
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
现在对桥接的 API 进行调用时，如果 `bridge-id` 不存在，将会返回 `404`，而不再是`400`。
|
||||
然后，还修复了这种情况下，在节点级别上进行 API 调用时，可能导致崩溃的问题。
|
||||
另外，在启动某个桥接时，会先检查指定桥接是否已启用。
|
||||
受影响的接口有：
|
||||
* [cluster] `/bridges/:id/:operation`,
|
||||
* [node] `/nodes/:node/bridges/:id/:operation`,
|
||||
其中 `operation` 是 `[start|stop|restart]` 之一。
|
||||
此外，对于节点操作，EMQX 将检查节点是否存在于集群中，如果不在，则会返回`404`，而不再是`501`。
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Fix an error occurring when a joining node doesn't have plugins that are installed on other nodes in the cluster.
|
||||
After this change, the joining node will copy all the necessary plugins from other nodes.
|
||||
|
|
@ -1,4 +0,0 @@
|
|||
Fix problems related to manual joining of EMQX replicant nodes to the cluster.
|
||||
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)
|
||||
|
|
@ -1,4 +0,0 @@
|
|||
修复 `replicant` 节点因为手动加入 EMQX 集群导致的相关问题。
|
||||
此前，手动执行 `加入集群-离开集群` 后，`replicant` 节点再次加入集群后只有重启节点才能正常运行。
|
||||
|
||||
[Mria PR](https://github.com/emqx/mria/pull/128)
|
||||
|
|
@ -1 +0,0 @@
|
|||
Fix crash when `statsd.server` is set to an empty string.
|
||||
|
|
@ -1 +0,0 @@
|
|||
修复 `statsd.server` 配置为空字符串时启动崩溃的问题。
|
||||
|
|
@ -1 +0,0 @@
|
|||
The default heartbeat period for MongoDB has been increased to reduce the risk of too excessive logging to the MongoDB log file.
|
||||
|
|
@ -1 +0,0 @@
|
|||
增加了MongoDB的默认心跳周期，以减少对MongoDB日志文件的过多记录的风险。
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
Fix garbled config display in dashboard when the value is originally from environment variables.
|
||||
For example, `env EMQX_STATSD__SERVER='127.0.0.1:8124' . /bin/emqx start` results in unreadable string (not '127.0.0.1:8124') displayed in Dashboard's Statsd settings page.
|
||||
Related PR: [HOCON#234](https://github.com/emqx/hocon/pull/234).
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
修复通过环境变量配置启动的 EMQX 节点无法通过HTTP API获取到正确的配置信息。
|
||||
比如：`EMQX_STATSD__SERVER='127.0.0.1:8124' ./bin/emqx start` 后通过 Dashboard看到的 Statsd 配置信息是乱码。
|
||||
相关 PR: [HOCON:234](https://github.com/emqx/hocon/pull/234).
|
||||
|
|
@ -1 +0,0 @@
|
|||
Fix `systemctl stop emqx` command not stopping jq, os_mon application properly, generating some error logs.
|
||||
|
|
@ -1 +0,0 @@
|
|||
修复`systemctl stop emqx` 命令没有正常停止 jq, os_mon 组件，产生一些错误日志。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Add -setcookie emulator flag when invoking emqx ctl to prevent problems with emqx cli when home directory is read only. Fixes [#10142](https://github.com/emqx/emqx/issues/10142)
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
Allow 'emqx ctl cluster' command to be issued before Mnesia starts.
|
||||
Prior to this change, EMQX `replicant` could not use `manual` discovery strategy.
|
||||
Now it's possible to join cluster using 'manual' strategy.
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
允许 'emqx ctl cluster join' 命令在 Mnesia 启动前就可以调用。
|
||||
在此修复前， EMQX 的 `replicant` 类型节点无法使用 `manual` 集群发现策略。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Fix bad http response format when client ID is not found in `clients` APIs
|
||||
|
|
@ -1 +0,0 @@
|
|||
修复 `clients` API 在 Client ID 不存在时返回的错误的 HTTP 应答格式。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Avoid parsing config files for node name and cookie when executing non-boot commands in bin/emqx.
|
||||
|
|
@ -1 +0,0 @@
|
|||
在 bin/emqx 脚本中，避免在运行非启动命令时解析 emqx.conf 来获取节点名称和 cookie。
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Report memory usage to statsd and prometheus using the same data source as dashboard.
|
||||
Prior to this fix, the memory usage data source was collected from an outdated source which did not work well in containers.
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Statsd 和 prometheus 使用跟 Dashboard 相同的内存用量数据源。
|
||||
在此修复前，内存的总量和用量统计使用了过时的（在容器环境中不准确）的数据源。
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Fixed configuration issue when choosing to use SSL for a Postgres connection (`authn`, `authz` and bridge).
|
||||
The connection could fail to complete with a previously working configuration after an upgrade from 5.0.13 to newer EMQX versions.
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
修正了在Postgres连接中选择使用SSL时的配置问题（`authn`, `authz` 和 bridge）。
|
||||
从5.0.13升级到较新的EMQX版本后，连接可能无法完成之前的配置。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Fix Swagger API schema generation. `deprecated` metadata field is now always boolean, as [Swagger specification](https://swagger.io/specification/) suggests.
|
||||
|
|
@ -1 +0,0 @@
|
|||
修复 Swagger API 生成时，`deprecated` 元数据字段未按照[标准](https://swagger.io/specification/)建议的那样始终为布尔值的问题。
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue