Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Hi, I fixed a bug in the emqx.schema related to bridging.
Using a near-default emqx.conf:
I was getting errors bridging because the sslopt was a deeply nested list due to a bug in emqx.schema.
It's just one line, change:
I would happily submit a patch file in the future for stuff like this, or push directly to my own branch and make a pull request, but I don't have access and don't know how you all handle external contribution. Please let me know so that maybe next time I don't make an issue!
Hate to keep bothering you all, but I believe I found 2 more bugs relating to the bridge..:
#1 was a Logging bug in emqx_bridge:351
#2 in emqx_message:set_headers, it doesn't properly handle the case where the headers are undefined due to the is_map() guard. So either we can remove the is_map guard or add a 3rd function overload:
I'm surprised no one has pointed these out because bridging seems impossible w/o these fixes