- 21 10月, 2021 1 次提交
-
-
由 Bert Kleewein 提交于
Signed-off-by: NBert Kleewein <bertk@microsoft.com>
-
- 20 10月, 2021 1 次提交
-
-
由 Roger Light 提交于
-
- 14 10月, 2021 1 次提交
-
-
由 Roger Light 提交于
Closes #602. Also-by: N陳傑夫 <chienfuchen32@gmail.com>
-
- 26 8月, 2021 2 次提交
-
-
由 Roger Light 提交于
-
由 Roger Light 提交于
-
- 24 8月, 2021 2 次提交
-
-
由 Nick 提交于
...instead of just passing the value to the _published condition. Signed-off-by: NNick <nick.mayerhofer@enchant.at>
-
由 Nick 提交于
In order to enable waiting with timeout after issuing mqtt.Client's publish(..) like: ''' infot = self.mqttc.publish(topic, msg, qos=1) infot.wait_for_publish(0.5) '''
-
- 21 8月, 2021 1 次提交
-
-
由 Roger Light 提交于
-
- 19 8月, 2021 1 次提交
-
-
由 Roger Light 提交于
-
- 30 7月, 2021 2 次提交
-
-
由 Roger A. Light 提交于
-
由 Roger A. Light 提交于
-
- 26 7月, 2021 1 次提交
-
-
由 Roger Light 提交于
Closes #500. Closes #89.
-
- 23 7月, 2021 3 次提交
-
-
由 Roger Light 提交于
Closes #520. Thanks to Chris Hibberd.
-
由 Roger Light 提交于
-
由 Roger Light 提交于
Closes #566. Thanks to Cody Scott.
-
- 22 7月, 2021 9 次提交
-
-
由 Roger A. Light 提交于
-
由 Roger A. Light 提交于
-
由 Roger A. Light 提交于
-
由 Roger Light 提交于
Appending to bytes() is slow, bytearray() is fast. Closes #571. Thanks to Umberto Morelli.
-
由 Roger Light 提交于
It would sometimes call the MQTT v3.x callback when it should call the MQTT v5 callback. Closes #570. Thanks to Frank Pagliughi.
-
由 Roger Light 提交于
Closes #575. Thanks to briggySmalls.
-
由 Hildo Guillardi Júnior 提交于
-
由 Roger Light 提交于
And convert the _out_packet queue use to thread safe.
-
由 Roger Light 提交于
-
- 08 7月, 2021 4 次提交
-
-
由 Roger Light 提交于
-
由 Roger Light 提交于
-
由 Roger A. Light 提交于
-
由 Roger A. Light 提交于
-
- 07 7月, 2021 6 次提交
-
-
由 Roger A. Light 提交于
-
由 Roger A. Light 提交于
Closes #409 Closes #576 Thanks to Thomas Zahari.
-
由 Roger A. Light 提交于
-
由 Roger A. Light 提交于
The `rc` parameter in the `on_disconnect` callback now has meaningful values in the case of an error. Closes #441. Thanks to Nawab.
-
由 Christian Clauss 提交于
-
由 Roger A. Light 提交于
This means that outgoing messages will only be retried on the client reconnecting to the server. They will *not* be retried when the client is still connected.
-
- 21 6月, 2021 1 次提交
-
-
由 GilbertWong 提交于
The correct usage for `socket.create_connection` is below: >> socket.create_connection(address[, timeout[, source_address]]) >> Connect to a TCP service listening on the Internet address (a 2-tuple (host, port)), and return the socket object. This is a higher-level function than socket.connect(): if host is a non-numeric hostname, it will try to resolve it for both AF_INET and AF_INET6, and then try to connect to all possible addresses in turn until a connection succeeds. This makes it easy to write clients that are compatible to both IPv4 and IPv6. >> Passing the optional timeout parameter will set the timeout on the socket instance before attempting to connect. If no timeout is supplied, the global default timeout setting returned by getdefaulttimeout() is used. >> If supplied, source_address must be a 2-tuple (host, port) for the socket to bind to as its source address before connecting. If host or port are ‘’ or 0 respectively the OS default behavior will be used. >> Changed in version 3.2: source_address was added. Also the semantic of connect timeout and keepalive timeout are totally different.
-
- 16 5月, 2021 1 次提交
-
-
由 Max Christoph 提交于
Signed-off-by: NMax Christoph <chrystler@web.de>
-
- 08 5月, 2021 1 次提交
-
-
由 Bert Kleewein 提交于
Signed-off-by: NBert Kleewein <bertk@microsoft.com>
-
- 15 4月, 2021 1 次提交
-
-
由 Roger Light 提交于
Closes #551.
-
- 09 12月, 2020 1 次提交
-
-
由 Frederik Peter Aalund 提交于
Signed-off-by: NFrederik Aalund <fpa@sbtinstruments.com>
-
- 23 9月, 2020 1 次提交
-
-
由 Roger A. Light 提交于
Closes #481. Thanks to Tao Su.
-