dc3c0094f0
Merge pull request #9236 from ieQu1/master
...
chore(ekka): Bump version to 0.13.6
2022-10-26 14:50:24 +02:00
702c968f46
chore(ekka): Apply suggestions from code review
...
Co-authored-by: Zaiming (Stone) Shi <zmstone@gmail.com>
2022-10-26 13:02:35 +02:00
6c8936467e
chore(ekka): Bump version to 0.13.6
2022-10-26 12:08:14 +02:00
7d23074073
Merge pull request #9233 from zmstone/1026-add-pr-template
...
chore: add pull request template
2022-10-26 10:50:18 +02:00
13543c45cc
chore: add pull request template
2022-10-26 10:29:47 +02:00
0eca531e64
feat: add `retry-after` headers to unavailable response
2022-10-25 15:01:05 -03:00
79f2d3e9c3
docs: update v5.0.10-en.md
2022-10-25 17:26:05 +02:00
156b19b525
docs: update v5.0.10-zh.md
2022-10-25 17:24:36 +02:00
8fa9a06337
Merge pull request #9222 from zhongwencool/add-prometheus-collector-switch
...
feat: add prometheus collectors config
2022-10-25 22:10:28 +08:00
049f988642
chore: update apps/emqx_conf/src/emqx_conf_schema.erl
...
Co-authored-by: Thales Macedo Garitezi <thalesmg@gmail.com>
2022-10-25 22:07:48 +08:00
4c5e64d5a3
feat: hibernate after send data to prometheus push_gateway
2022-10-25 12:27:25 +08:00
8578024637
chore: bump emqx_prometheus to 5.0.3
2022-10-25 11:21:16 +08:00
6710736243
feat: add prometheus collectors config
2022-10-25 09:41:58 +08:00
997a262c96
fix(mgmt_api): return 503 when emqx is not running in `/status` (5.0)
2022-10-24 14:53:41 -03:00
2d606c1159
Merge pull request #9215 from zmstone/1024-chore-merge-release-v50-back-to-master
...
1024 chore merge release v50 back to master
2022-10-24 19:47:17 +02:00
93195f7b5b
chore: fix introduced_in for new proto APIs
2022-10-24 11:53:51 +02:00
637bc886bb
chore: bump release version to 5.0.10
2022-10-24 11:49:20 +02:00
67da0a1479
chore: bump chart version to 5.0.10
2022-10-24 11:48:49 +02:00
e3240b52a8
chore: bump app versions
2022-10-24 11:48:17 +02:00
508c0e84d0
Merge branch 'release-v50' into master
2022-10-24 11:46:31 +02:00
11daaa08e2
chore: bump version numbers to 5.0.9
2022-10-24 09:42:25 +02:00
572e2d7c2c
Merge pull request #9209 from zmstone/1020-docs-split-change-logs
...
chore: split change logs
2022-10-24 09:41:18 +02:00
31c0d73cd5
chore: split change logs
2022-10-24 09:40:08 +02:00
fa5d756ae6
Merge pull request #9186 from HJianBo/more-understanderable-trans
...
chore(docs): translate Max Awaiting PUBREL confs
2022-10-21 17:29:28 +02:00
ca052bd0f4
docs: Update apps/emqx/i18n/emqx_schema_i18n.conf
2022-10-21 17:28:49 +02:00
918c011e33
Merge pull request #9198 from lafirest/test/rmv_unused_test_case
...
test(shared_sub): remove redundant test case
2022-10-21 12:36:52 +02:00
6455085111
Merge pull request #9187 from ieQu1/master
...
chore(gen_rpc): Bump version to 3.0.0
2022-10-21 11:14:38 +02:00
9d650a69b8
fix(gen_rpc): Fix Chinese translation
2022-10-21 10:25:22 +02:00
0f03449b43
chore: improve max_awating_rel_timeout conf docs
...
Co-authored-by: Zaiming (Stone) Shi <zmstone@gmail.com>
2022-10-21 16:08:09 +08:00
49dd25cb14
chore: make spellcheck happy
2022-10-21 14:38:46 +08:00
1d564ab8d5
test(shared_sub): remove redundant test case
2022-10-21 14:37:46 +08:00
0ca4f30a34
Merge pull request #9193 from zmstone/1020-chore-upgrade-gun-1.3.9
...
1020 chore upgrade gun 1.3.9
2022-10-21 08:13:21 +02:00
8344d70e07
Merge pull request #9194 from zmstone/1020-upgrade-dashboard-to-v1.1.0
...
chore: upgrade to dashboard v1.1.0
2022-10-21 11:49:58 +08:00
6d232fda5c
chore(i18n): improve the max_awaiting_rel desc
2022-10-21 10:27:20 +08:00
72a228c521
chore: update apps/emqx/i18n/emqx_schema_i18n.conf
...
Co-authored-by: Zaiming (Stone) Shi <zmstone@gmail.com>
2022-10-21 09:53:31 +08:00
01e0c9e64e
Merge pull request #9170 from zmstone/fix-publish-api-return-error-code
...
feat(api/publish): return detailed publish results
2022-10-20 20:04:00 +02:00
d1332b72e7
feat(api/publish): return detailed publish results
...
Prior to this change, the publish API returns 200 in most of
the cases.
This change provides more insights to the publish result.
For single message publish endpoint (`publish/`):
HTTP error codes are:
200: Everything is OK
202: No subscriber for the topic
400: When mesage is invalid message.
e.g. bad topic name or QoS out of range.
503: Failed to dispatch the message. e.g. during EMQX restart.
The response body is a JSON object with two fields
`message_id`, and `publish_result`.
The `message_id` is a globally unique ID for tracing.
`publish_result` is `"OK"` when the message is delivered
to at least one subscriber.
Otherwise `"no_subscriber"`.
`publish_result` may also be some other informative
message to hint the failure result, the content of which
may change in the future.
For `publish/bulk` endpoint:
200: When all message in the bulk are published OK
202: If at least one message in the bulk had `"no_subscriber"` result
400: When mesage is invalid message. e.g. bad topic name or
QoS out of range.
503: When there is at least one message failed at dispatch.
The reply body is a list of JSON objects having the same layout
as for hte `publish` endpoint.
2022-10-20 20:03:27 +02:00
05793ef1e5
chore: upgrade to dashboard v1.1.0
2022-10-20 19:13:09 +02:00
67dd733e8d
chore: bump to gun 1.3.9
...
1.3.7 had a bug which caused ssl_passive message unhandled
2022-10-20 19:10:45 +02:00
b3ffe89f35
test: assert message receive pid is in the expected pids list
2022-10-20 19:10:45 +02:00
27de9998a8
Merge pull request #9191 from zmstone/1020-fix-shared-dispatch
...
fix(shared): do not redispatch shared messages for certain shutdown
2022-10-20 18:59:45 +02:00
c01eae5a8b
Merge pull request #9181 from emqx/chore-fix-helm-chart-variable-name
...
chore: fix ssl.enable variable in helm chart
2022-10-20 18:18:37 +02:00
d0120e1edc
chore(gen_rpc): Bump version to 3.0.0
2022-10-20 16:32:06 +02:00
fa020d036f
chore(docs): translate Max Awaiting PUBREL confs
2022-10-20 20:14:36 +08:00
c7a90d73b2
fix(shared): do not redispatch shared messages for certain shutdown
...
For takeover, there should be no message re-dispatch because
the messages will be retried by the new session.
For kick, messages should not be re-dispatched for security reason.
i.e. if admin has identified that there are malicious messages
stored in persisted sessions, killing the session should not
cause messages to be re-dispatched
2022-10-20 13:51:48 +02:00
c0c2657a80
Merge pull request #9139 from lafirest/fix/clean_blocked_user_data
...
feat(banned): clean retained/delayed data when client is banned
2022-10-20 18:00:48 +08:00
cd40acb035
chore: fix ssl.enable variable in enterprise helm chart
2022-10-20 08:54:29 +02:00
53414b004b
Merge pull request #9153 from Tautcius/patch-1
...
chore(charts): fix typos
2022-10-20 08:36:47 +02:00
6cbb5aa172
Merge pull request #9128 from thalesmg/kjell/jira-EMQX-7312/kafka_rule_engine_counters_ok
...
feat: add support for counters and gauges to the Kafka Bridge
2022-10-19 10:25:21 -03:00
0546cd3d1a
Merge pull request #9123 from lafirest/fix/kick_seesion_redispatch
...
fix(shared_sub): kick session should not cause session message redispatch
2022-10-19 09:47:10 +08:00
ieQu1