iot
Here are 12,020 public repositories matching this topic...
-
Updated
Feb 11, 2022 - Python
Is there an existing issue for this?
- I have searched the existing issues
Kong version ($ kong version)
2.5.1.0
Current Behavior
When calling kong.response.exit(), the function automatically sets the Content-Length header on the response even if the Transfer-Encoding header is present. This is in violation of RFC 7230 3.3.2:
A sender MUST NOT send a Content-
-
Updated
Jun 16, 2021 - C
In https://github.com/taosdata/TDengine/blob/develop/src/client/src/tscPrepare.c, Local variable loopCont is assigned only once, to a constant value, making it effectively constant throughout its scope. If this is not the intent, examine the logic to see if there is a missing assignment that would make loopCont not remain constant.
So the 1567th line should be removed.
. Since the data is 16-bits wide and can therefore not be negative, the easy fix would be to do the following:
sip.js(1128): uncompensated = uint16(data[0], data[1]);
Please see page 15 of the manual of the BMP180 chip:
https://ae-bst.resource.bosch.com/media
-
Updated
Feb 11, 2022 - C
Description
In log messages, salt.modules.tls uses csr_path in log messages without checking for a trailing slash, resulting in misleading log entries:
'Created Private Key: "/etc/ssl/MYCA/certsMY.HOSTNAME.key." '
(It also makes it appear that there's a trailing dot on the filename)
https://github.com/saltstack/salt/blob/v3003.3/salt/modules/tls.py#L1167 among other places. It pr
-
Updated
Feb 11, 2022 - Java
-
Updated
Feb 11, 2022 - Erlang
-
Updated
Feb 10, 2022 - C++
-
Updated
Feb 10, 2022 - C
Issue description
The test case in t/core/utils.t currently has some code errors, such as
The variable host is a nil when the code is executed here (which may never happened)
Solut
Describe the bug
ATM the following query
select * from t where abyte = null;executes just fine and returns rows with abyte column equal to zero. The same happens for short columns.
Byte and short column types don't support nulls (important note: geobyte and geoshort types support nulls), so we need to do something with this behavior. We could either report an error for
A common protocol structure is to have a header containing a length field, followed by data of length bytes, followed by additional protocol fields such as a CRC. If the length field is variable, the position of subsequent URH-specified protocol fields defined by fixed position will not be in the correct location.
I do not know the best way to address this, but quick and easy way to support
-
Updated
Jan 16, 2022 - Go
-
Updated
Feb 2, 2022 - Jupyter Notebook
-
Updated
Oct 25, 2021 - C#
While struggling around with ingress (#2546) I figured out some inconsistencies. For most k8s services it is possible to override args or configs. But for ingress this doesn't work.
It should be possible to customize enable.{my-service} and {my-service}.yaml by having a local copy in:
/var/snap/microk8s/current/microk8s-resources/
But this doesn't seem to work.
-
Updated
Feb 11, 2022 - C
-
Updated
Aug 1, 2021 - C++
-
Updated
Feb 10, 2022 - Python
Is your enhancement proposal related to a problem? Please describe.
access_addr always seems to be of size 4; that should be #defined.
crc_init always seem to be of size 3; that should be #defined.
https://github.com/zephyrproject-rtos/zephyr/pull/31009/files#r736229677
https://github.com/zephyrproject-rtos/zephyr/pull/31009/files#r736229386
Describe the solution you'd like
A
-
Updated
Feb 6, 2022 - C++
-
SerialPort Version: 6.2.0
-
NodeJS Version: N/A
-
Operating System and Hardware Platform: N/A
-
Have you checked the right version of the api docs?: N/A
-
Are you having trouble installing and you checked the Installation Special Cases docs? N/A
-
Are you using Electron and have you checked the Electron Docs?: N/A
I have a device which is only intermit
-
Updated
Feb 7, 2022 - C++
Improve this page
Add a description, image, and links to the iot topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the iot topic, visit your repo's landing page and select "manage topics."
Hi,
first thanks for this awesome software. But I have some trouble and I don't know how to proceed. First I try to find out what else I could provide for this report to be a good bug report.
First, I use the latest version (v1.14.0) from openSUSE build Service. I know, I should compile it by my self to avoid any other causes for this behavior. But for now I still use this package from there