iot

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

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-

In https://github.com/taosdata/TDengine/blob/develop/src/util/src/tnettest.c, You might overrun the 128-character fixed-size string epSet.fqdn[0] by copying serverFqdn without checking the length.

We have defined a function called tstrncpy that can solve this problem. It is recomme

The uncompensated temperature of the BMP180 is incorrectly converted to a 16-bit signed value, instead of a 32-bit signed value (long). 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

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.

Issue description

Currently, the installation docs of Apache APISIX doesn't mention the offline installation scenarios, which is common in the enterprise.

Solution

add a offline installation demo in how-to-build.md

## download APISIX offline RPM packages via YUM to `./apisix` folder
mkdir -p apis

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

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.

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