Thales Macedo Garitezi 3954b7bde2 fix(bridges): function clause when a non-ingress bridge coexists with an egress bridge ... This was not caught by our tests because we always test bridge types in isolation. So, if the config only contains ingress-only bridges, the `on_message_publish` hook is never installed. In a real system, if there are bridges of mixed types in the config, the hook might be installed, and `emqx_bridge:get_matched_bridge_id` would crash when iterating over the ingress bridges.		2023-03-16 13:43:01 -03:00
..
proto	perf(bridge-api): ask bridge listings in parallel	2023-03-15 19:17:29 +03:00
schema	fix(bridge): do not log in converter	2023-03-06 15:31:28 -03:00
emqx_bridge_api.erl	Merge pull request #10123 from fix/EMQX-9136/lookup-busy-resources	2023-03-16 00:07:12 +03:00
emqx_bridge_app.erl	fix(bridge): ensure all bridge resources are stopped before app stop	2023-01-27 12:39:05 +01:00
emqx_bridge_resource.erl	chore(kafka_producer): make schema changes more backwards compatible	2023-03-16 13:43:01 -03:00
emqx_bridge_sup.erl	feat: implement kafka consumer	2023-03-16 13:43:01 -03:00
emqx_bridge.app.src	feat: implement kafka consumer	2023-03-16 13:43:01 -03:00
emqx_bridge.erl	fix(bridges): function clause when a non-ingress bridge coexists with an egress bridge	2023-03-16 13:43:01 -03:00