Commit Graph

11794 Commits

Author SHA1 Message Date
Zaiming (Stone) Shi
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
JianBo He
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
JianBo He
6d232fda5c chore(i18n): improve the max_awaiting_rel desc 2022-10-21 10:27:20 +08:00
JianBo He
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
Zaiming (Stone) Shi
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
Zaiming (Stone) Shi
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
Zaiming (Stone) Shi
05793ef1e5 chore: upgrade to dashboard v1.1.0 2022-10-20 19:13:09 +02:00
Zaiming (Stone) Shi
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
Zaiming (Stone) Shi
b3ffe89f35 test: assert message receive pid is in the expected pids list 2022-10-20 19:10:45 +02:00
Zaiming (Stone) Shi
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
Ivan Dyachkov
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
ieQu1
d0120e1edc chore(gen_rpc): Bump version to 3.0.0 2022-10-20 16:32:06 +02:00
JianBo He
fa020d036f chore(docs): translate Max Awaiting PUBREL confs 2022-10-20 20:14:36 +08:00
Zaiming (Stone) Shi
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
lafirest
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
Ivan Dyachkov
cd40acb035 chore: fix ssl.enable variable in enterprise helm chart 2022-10-20 08:54:29 +02:00
Zaiming (Stone) Shi
53414b004b
Merge pull request #9153 from Tautcius/patch-1
chore(charts): fix typos
2022-10-20 08:36:47 +02:00
lafirest
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
firest
7b3c67fbe9 test(shared_sub): ensure snabbkaffe will be stopped 2022-10-18 13:47:57 +08:00
firest
bdaadda479 fix(banned): fix nit code 2022-10-18 13:39:48 +08:00
firest
3f1f244310 fix: fix bpapi versions 2022-10-18 13:39:48 +08:00
firest
b2eed47976 chore: bump retainer version && update CHANGES 2022-10-18 13:36:08 +08:00
firest
69701ff578 feat(banned): clean retained/delayed data when client is banned 2022-10-18 13:35:09 +08:00
Tautcius
228118b1fa chore(charts): Update certificate.yaml
Typo in if statement that prevented creation of Certificate resource.
2022-10-18 09:53:12 +08:00
zhongwencool
ad0e9aa092
Merge pull request #9152 from zhongwencool/trace-log-detail-api
get trace file's detail via /trace/:name/log_detail
2022-10-17 11:44:15 +08:00
Zhongwen Deng
c0ed8b82aa Merge branch 'trace-log-detail-api' of https://github.com/zhongwencool/emqx into trace-log-detail-api 2022-10-17 09:49:55 +08:00
zhongwencool
77a5125366
chore: update apps/emqx_management/src/emqx_mgmt_api_trace.erl
Co-authored-by: Thales Macedo Garitezi <thalesmg@gmail.com>
2022-10-17 09:45:00 +08:00
Zhongwen Deng
58b990064c chore: update bpapi.verions 2022-10-17 09:43:17 +08:00
Zhongwen Deng
4d9cae0387 feat: get trace file's detail via /trace/:name/log_detail 2022-10-17 09:43:15 +08:00
zhongwencool
bc0cc80d32
Merge pull request #8924 from zhongwencool/authn-config-check
fix: authentication should be array, not struct
2022-10-17 09:14:05 +08:00
Ivan Dyachkov
6f899699ca
Merge pull request #9157 from emqx/chore-bump-asdf-erlang-version
chore: bump asdf erlang version
2022-10-14 14:52:34 +02:00
Zaiming (Stone) Shi
1686ca26fa
Merge pull request #9155 from zmstone/1014-publish-api-should-not-echo
fix(api): publish API only returns message ID
2022-10-14 11:52:17 +02:00
Ivan Dyachkov
37a400ec25 chore: bump asdf erlang version 2022-10-14 11:19:25 +02:00
Ivan Dyachkov
f2db35db39 chore: delete unused function clause 2022-10-14 10:46:11 +02:00
zhongwencool
bfc780f95b
Merge branch 'master' into authn-config-check 2022-10-14 16:36:50 +08:00
Ivan Dyachkov
5a8cab46a9 test: update publish api test suite 2022-10-14 10:17:22 +02:00
Zaiming (Stone) Shi
53fb8fcded docs: Add changelog 2022-10-14 10:06:45 +02:00
Zaiming (Stone) Shi
c2f176c1e7 fix(api): publish API only returns message ID 2022-10-14 09:49:46 +02:00
Zhongwen Deng
a02fea0a19 chore: update bpapi.verions 2022-10-14 15:16:09 +08:00
Zhongwen Deng
4579d7fff8 feat: get trace file's detail via /trace/:name/log_detail 2022-10-14 11:38:39 +08:00
JianBo He
6f077c47e7
Merge pull request #9136 from emqx/enhance-flapping-detect-5
refactor: enhance the flapping detect accuracy
2022-10-13 09:49:43 +08:00
JianBo He
59c1b0d16e chore: update changes 2022-10-12 10:06:35 +08:00
JianBo He
56000cbf3e refactor: more rigorous checking of flapping to improve stability of the system
port: https://github.com/emqx/emqx/pull/9045
2022-10-12 10:03:47 +08:00
JianBo He
5a66c8b117
Merge pull request #9082 from HJianBo/update-api-docs
chore(i18n): enrich HTTP API desc
2022-10-12 09:36:11 +08:00
firest
b4eb0f18f9 fix(shared_subs): rename redispatch function name and simply test case 2022-10-10 18:06:55 +08:00
firest
f0769cb765 fix(shared_sub): kick session should not cause session message redispatch 2022-10-10 13:52:09 +08:00
Zaiming (Stone) Shi
63774ba5d3
Merge pull request #9104 from zmstone/1005-fix-shared-sub-dispatch
fix(shared): re-dispatch inflight (QoS1) and mqueue messages
2022-10-09 11:41:30 +02:00
lafirest
d600c870af
Merge pull request #9060 from lafirest/fix/delayed_pub
fix(delayed): Improve time precision of delayed messages
2022-10-09 10:39:31 +08:00
firest
6d852b69a2 chore: update CHANGES 2022-10-09 10:13:09 +08:00
Ivan Dyachkov
9faaffd50b
Merge pull request #9115 from emqx/build-check-if-quicer-binary-present-before-trying-to-sign-it
build: check if quicer binary present before trying to sign it
2022-10-07 12:33:28 +02:00