ecf74bac20
Merge pull request #12263 from id/0105-sync-r54
...
sync release-54 to master
2024-01-06 15:15:51 +08:00
d221f34ce8
chore: bump version && update changes
2024-01-06 13:34:07 +08:00
e20b024b6e
fix(iotdb): fix iotdb testcases
2024-01-06 13:01:43 +08:00
803529968e
test(s3): fix httpc ssl opts
2024-01-05 19:35:13 +01:00
06117c3a33
Merge remote-tracking branch 'upstream/release-54' into 0105-sync-r54
2024-01-05 14:20:38 +01:00
66c8faa87e
Merge pull request #12262 from id/0105-release-5.4.1
...
release 5.4.1
2024-01-05 13:16:00 +01:00
d04ac08d1d
chore: release 5.4.1
2024-01-05 11:48:28 +01:00
d16458ccd0
feat(iotdb): improve the IoTDB bridge to v2 style
2024-01-05 16:54:31 +08:00
e4c06a6be5
Merge pull request #12244 from jostar-y/fix/log
...
fix:judgment condition failure
2024-01-05 16:44:08 +08:00
42ec566771
Merge pull request #12259 from Kinplemelon/kinple/for-upgrade-dashboard
...
chore: upgrade dashboard to e1.4.1 for ee
2024-01-05 14:24:33 +08:00
37feeed560
fix: judgment condition always failure
2024-01-05 14:23:15 +08:00
da3937b80e
Merge pull request #12247 from emqx/split_influxdb_connector_actions
...
refactor: split influxdb bridges to actions and connectors
2024-01-05 14:07:35 +08:00
2f08471303
fix: cannot found desc for influxdb_parameters
2024-01-05 11:59:13 +08:00
4edd4b4db8
chore: upgrade dashboard to e1.4.1 for ee
2024-01-05 11:51:47 +08:00
9714092525
fix: fix: update more influxdb testcases
2024-01-05 11:20:27 +08:00
ca3109dfa6
Merge pull request #12256 from keynslug/fix/mysql-wo-pwd
...
fix(mysql): expect password may be missing from config
2024-01-04 16:40:21 +01:00
ace6081792
chore: add changelog entry
2024-01-04 15:16:27 +01:00
304fe84434
fix(mysql): expect password may be missing from config
2024-01-04 15:16:27 +01:00
338e14ad54
Merge pull request #12250 from zhongwencool/deobfuscate-config
...
fix: incorrectly attempt to update the field value when the previous …
2024-01-04 13:59:01 +08:00
8ebd233a46
chore: update influxdb-erl to 1.1.12
2024-01-04 10:20:52 +08:00
90404b62a4
fix: incorrectly attempt to update the field value when the previous field don't have value
2024-01-04 10:12:34 +08:00
b4c4103eab
Merge pull request #12246 from id/0102-docker-do-not-expose-11883
...
chore: do not expose 11883 by default in docker as we do not listen on it
2024-01-04 09:14:03 +08:00
19e2ec9748
fix: update influxdb testcases
2024-01-03 18:39:29 +08:00
f2f099ff18
Merge pull request #12249 from zhongwencool/log-prompt-garbled
...
fix: the API prompt garbled characters for updating the configuration
2024-01-03 16:00:46 +08:00
00e8a36dbe
fix: the API prompt garbled characters for updating the configuration
2024-01-03 15:34:45 +08:00
57c0a7c5ef
Merge pull request #12235 from zhongwencool/ft-config-update-api
...
fix: ft config update api return raw config
2024-01-03 14:07:22 +08:00
b33f46f82a
Merge pull request #12248 from id/0102-prep-5.4.1-alpha.1
...
5.4.1-alpha.1
2024-01-02 15:21:30 +01:00
d4c83cf463
chore: tag 5.4.1-alpha.1
2024-01-02 14:37:45 +01:00
904bd0270f
chore: bump app versions
2024-01-02 18:04:06 +08:00
7c7a0b2172
refactor: split influxdb bridges to actions and connectors
2024-01-02 18:01:22 +08:00
4c761b0ff9
docs: add changelog entry
2024-01-02 10:50:15 +01:00
1649f67996
chore: do not expose 11883 by default in docker as we do not listen on it
2024-01-02 10:07:05 +01:00
071d15d13e
Merge pull request #12228 from clementnuss/cjmn/ipv6-port-fix
...
feat(helm): only keep last digits for ipv6 ports
2024-01-02 08:41:43 +01:00
c22687e322
feat(helm): only keep last digits for ipv6 ports
...
permits specifying ports such as :::18083, a somewhat strange but needed
syntax when trying to make emqx listen on IPv6 addresses
The solution here is to split by colon `:` and to only keep the last
entry, which will corespond to the actual number for the port.
Signed-off-by: Clément Nussbaumer <clement@n8r.ch>
2024-01-01 16:14:48 +01:00
a87df28dfc
Merge pull request #12243 from keynslug/fix/EMQX-11483/route-async-repl
...
fix(router): rely on local sync state updates to propagate routes
2023-12-29 16:31:00 +01:00
42da329b34
chore: add changelog entry
2023-12-29 14:05:50 +01:00
5c91984ad7
chore: leave comment describing need for tighter synchronization
2023-12-29 14:04:48 +01:00
02110bc79d
Merge pull request #12245 from savonarola/1229-improve-emqx_ds-interface
...
feat(ds): restore original add_generation/update_db_config callback semantics
2023-12-29 14:40:42 +02:00
9e0f3ce53b
feat(ds): restore original add_generation/update_db_config callback semantics
2023-12-29 13:12:15 +03:00
a3fc4fa5c3
Merge pull request #12242 from JimMoen/1228-chore-typo-and-style
...
chore: typo and style
2023-12-29 16:39:03 +08:00
8f8ad2895b
chore: bump git-blame-ignore-revs
2023-12-29 09:08:21 +08:00
5e100f52b8
style: erlfmt all `rebar.config` files and `bin/nodetool`
2023-12-29 09:08:03 +08:00
0f10d9a8bb
build: erlfmt `rebar.config` files and `bin/nodetool`
2023-12-29 09:08:03 +08:00
a3f33cc8bc
chore: fix typos in code and suite
2023-12-29 09:07:51 +08:00
a35ed4dacb
docs: enhance markdown indent and fix typos
2023-12-29 09:07:26 +08:00
572f465346
fix(typo): sync to enterprise
...
- follow up emqx/emqx#10398
2023-12-29 09:07:26 +08:00
ed10827343
docs: README spell
2023-12-29 09:07:25 +08:00
b9627c420f
fix(router): rely on local sync state updates to propagate routes
...
Instead of (potentially lagging) global table state itself. Local
state should be the only source of truth anyway. Moreover,
synchronize parts of local state update logic through the broker
pool to ensure consistency.
The problem was that `emqx_router:has_route/2` check may observe a
stale route, which deletion is not yet replicated from the core node
to the local replicant node.
For example:
1. The only one subscriber per a given topic A unsubscribes from
a replicant node.
2. The route to A is deleted by the emqx_broker.
3. Mria makes RPC to a core node, it succeeds and returns.
4. The client resubscribes or another client subscribes to the same
topic A.
5. emqx_broker tries to add a route again:
`emqx_router:do_add_route(Topic)`.
6. `emqx_router` checks if the route is present.
7. The stale route is present because deletion not replicated yet,
so no route is being added.
8. Route deletion is replicated locally but it's too late:
we already have a local subscriber without a route.
Co-Authored-By: Serge Tupchii <serge.tupchii@protonmail.com>
2023-12-28 19:16:31 +01:00
331bfaa535
fix(broker): avoid reclaiming per-topic counter twice
2023-12-28 17:43:50 +01:00
a8cd609ff4
chore(broker): simplify subscribe code path
2023-12-28 17:43:42 +01:00
zhongwencool