zhouzb

I don't know how you get this output, if I set Username to empty in SQL Test, the output I get is an empty string:

Hi @samuelyhsu We have noticed that this project does not appear to be actively maintained anymore. So I would like to invite you to try the open source MQTT client...

Hi, @josorv We have noticed that this project does not appear to be actively maintained anymore. So I would like to invite you to try the open source MQTT client...

@louisburton For some historical reasons, the `emqx-statsd` plugin (renamed `emqx-prometheus`) does not support statsd, and the previous name may misunderstand users, so we have corrected it now and will support...

@kjellwinblad Hi, I revisited the code of this PR once again, and found that there may be some problems in the implementation. Neither float nor bits types distinguish between signed...

``` SELECT subbits(hexstr2bin('9F4E58'), 1, 16, 'float', 'unsigned', 'big') as t1, subbits(hexstr2bin('9F4E58'), 1, 16, 'float', 'signed', 'big') as t2, subbits(hexstr2bin('9F4E58'), 1, 16, 'float', 'unsigned', 'little') as t3, bin2hexstr(subbits(hexstr2bin('9F4E58'), 1, 16, 'bits',...

I agree with this. > but unfortunately I think this is too late now since subbits/6 has been released and documented so it might already be in use in production...

@peace4j Sorry for not replying to you in time. What operating system and emqx version are you using?

@CoderIvan 是的，接收端不能根据 DUP 来判断已经接收过这个消息。

> @tigercl 感谢回复，所以和是否重复使用相同的`package_id`无关吧？，就算用不同的`package_id`也是无法判断吧？ 是的，虽然重传的时候必须使用与原始消息相同的 Packet ID，然后我们无法保证发送端在其他时候不会使用这个 Packet ID。 比如我们一次性发送多个 QoS 为 1 的消息，实际上这些消息中的 Packet ID 可以是一样的，因为接收端总是在响应完上一条消息后才来处理下一条消息，所以它总会认为消息中的 Packet ID 目前是可用的。