emqx/NanoSDK

Issues

• MQTT: publishing with QoS 1 (related to pinned issue)

  #230 opened a month ago by pmf
  2

• Subscribing to $SYS/brokers/connected and $SYS/brokers/disconnected

  #229 opened a month ago by pmf
  1

• nng_sendmsg is forbiddened with MQTT QoS 1/2

  #228 opened a month ago by JaylinYu
  0

• nni_mqtt_msg_get_publish_topic(),topic length =0

  #226 opened 2 months ago by ruishanyin
  1

• mqtt_client demo

  #208 opened 7 months ago by OdyWayne
  1

• SEGV on unknown address 0x000000000060

  #203 opened 9 months ago by wanghaEMQ
  0

• Can't build some of the demo projects

  #201 opened 9 months ago by ooonak
  0

• Licensing with GPL submodule?

  #193 opened a year ago by timwoj
  1

• Tips for using `Ninja` to build NanoSDK/NanoMQ with msquic on `MacOS`

  #165 opened a year ago by alvin1221
  2

• Need to connect exception backoff strategy. Need to be able to modify through configuration parameters

  #159 opened a year ago by DDDHuang
  0

• nng_mqtt_client struct is weird

  #119 opened a year ago by wanghaEMQ
  0

• Segment fault in quic_client conn

  #103 opened a year ago by wanghaEMQ
  0

• Working build

  #136 opened a year ago by aguasonic
  2

• SQLite Caching ignores extra info of MQTT v5 msg

  #132 opened 2 years ago by JaylinYu
  0

• use quic example code to connect to mq over tcp fail

  #126 opened 2 years ago by gavinshao111
  3

• independent MQTT subscribe API

  #9 opened 2 years ago by JaylinYu
  0

• quic mqtt disconnect fail

  #123 opened 2 years ago by gavinshao111
  2

• Improving `nng_mqtt_sqlite_option` interface memory ownership

  #121 opened 2 years ago by eeff
  0

• No nng_mqtt_msg_free API provided

  #120 opened 2 years ago by wanghaEMQ
  0

• delete 0x00 of each string nanosdk send out.

  #99 opened 2 years ago by JaylinYu
  0

• Need to porting the fix in nanonng to nanosdk for QUIC

  #101 opened 2 years ago by JaylinYu
  0

• Retain msg( tls test) can lead to nanomq error (heap use after free)

  #98 opened 2 years ago by xinyi-xs
  0

• Don't send SUB/UNSUB message with classical nng API

  #95 opened 2 years ago by JaylinYu
  0

• SUB/UNSUB will break the AIO callback chain in certain case.

  #50 opened 2 years ago by JaylinYu
  0

• packet ID of qos msg is not getting set when resending

  #44 opened 2 years ago by JaylinYu
  0

• Do not send msg in connect/disconnect cb of mqtt dialer

  #42 opened 2 years ago by JaylinYu
  0

• clean session function is off default

  #45 opened 2 years ago by wanghaEMQ
  0

• The keepalive is ZERO if not set

  #46 opened 2 years ago by wanghaEMQ
  1

• NanoSDK donot check if publish topic is illegal?

  #24 opened 2 years ago by xinyi-xs
  0

• SEGV on unknown address when pub illegal topic #

  #33 opened 2 years ago by xinyi-xs
  0

• QoS 0 msg might have slightly chance of data racing

  #39 opened 2 years ago by JaylinYu
  0

• nni_lmq might has some memleak problem

  #8 opened 2 years ago by JaylinYu
  0

• is nni_msg too heavy?

  #4 opened 2 years ago by JaylinYu
  0

• unexpected disconnect when applying massive load

  #32 opened 2 years ago by xinyi-xs
  0

• the packet ID of SUBSCRIBE should not start from 0

  #37 opened 2 years ago by JaylinYu
  0

• Building demo not succeed

  #36 opened 2 years ago by wanghaEMQ
  0

• nng_close cause seg fault

  #34 opened 2 years ago by JaylinYu
  0

• mqtt_ctx_send does not respect result of AIO

  #29 opened 2 years ago by JaylinYu
  0

• Resource dead lock in qos_send_cb

  #27 opened 2 years ago by JaylinYu
  0

• panic: pthread_mutex_lock: Resource deadlock avoided

  #26 opened 2 years ago by alvin1221
  1

• SDK should check invalid publishing topic

  #25 opened 2 years ago by JaylinYu
  0

• Segmentation fault (TLS connect)

  #22 opened 2 years ago by alvin1221
  0

• Client crashed when calling nng_closeall()

  #17 opened 2 years ago by JaylinYu
  0

• QoS 1 msg : memleak when sending PUBACK

  #16 opened 2 years ago by JaylinYu
  0

• nng_recvmsg return NULL msg when receving massive QoS 2

  #15 opened 2 years ago by JaylinYu
  0

• User send msg before pipe start cause msg lost.

  #10 opened 2 years ago by JaylinYu
  0

• memleak due to PINGRESP

  #6 opened 2 years ago by JaylinYu
  0

• Memleak while receving CONNACK

  #2 opened 2 years ago by JaylinYu
  1