iot
Here are 11,638 public repositories matching this topic...
-
Updated
Dec 17, 2021 - 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
Dec 17, 2021 - C
Describe the solution you'd like
It would be nice to have a way to control whether a VM starts on boot or not. Maybe a new autostart option to salt.states.virt.running and/or salt.states.virt.defined? Or maybe a new function?
Describe alternatives you've considered
I'll probably use salt.modules.virt.set_autostart for now.
-
Updated
Dec 16, 2021 - Java
-
Updated
Dec 17, 2021 - Erlang
-
Updated
Dec 10, 2021 - C++
-
Updated
Dec 16, 2021 - C
Issue description
Sometimes, we just need install etcd, ref here. But install_dependencies.sh not support this feature, it will install all dependencies of APISIX. Should we support install etcd separately in install_dependencies.sh ?
example:
bash install_dependencies.sh etcd
Environment
- apisix version
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
Describe the bug
When 2 tables joined on INT and LONG columns error shown that there is join column mismatch
To reproduce
select x, y
from long_sequence(100) ls
join (
select cast(x as int) y from long_sequence(100)
) as ls2
on ls.x = ls2.y
Expected Behavior
INT can be be upcast to LONG and equality should be checked as LONG equality so that above query returns 10
-
Updated
Nov 20, 2021 - Go
-
Updated
Oct 25, 2021 - C#
-
Updated
Dec 9, 2021 - Jupyter Notebook
-
Updated
Dec 15, 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
Aug 1, 2021 - C++
-
Updated
Dec 15, 2021 - Python
-
Updated
Dec 16, 2021 - C++
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
Summary of Problem
Not able to open port with stopbits as 1.5
I am currently building a desktop client using electron, where the COM port receives data correctly for values: baudRate: 2400, dataBits: 7, stopBits: 1.5, parity: 'none'
I found from the node-serialport documentation, stopBits Must be one of these: 1 or 2. But, should 1.5 be supported as well? especially for old & slow
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