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

Can anyone please help me out. I'm getting error while generating KONG client credentials on HTTP port 8000.

{ "error_description": "You must use HTTPS", "error": "access_denied" }

I have added trusted_ips = 0.0.0.0/0,::/0 in kong.conf also, but it didn't work.

There are some spelling mistake in our source code, could some help to fix this and submit a pr.
position:
1:https://github.com/taosdata/TDengine/blob/develop/tests/test/c/createNormalTable.c line 236 , word "performace"
2.https://github.com/taosdata/TDengine/blob/develop/tests/test/c/createTablePerformance.c line 224, word "performace"

Remember to assign me to review your PR. Thanks.

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.

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

Issue description

Currently, Apache APISIX will generate an id while initializing if the user doesn't specify one, and it relies on the lua-resty-jit-uuid library but without an explicit seed.

https://github.com/apache/apisix/blob/4dafab5afa3293b3d72007517246e01da385f8ef/apisix/core/id.lua#L76-L78

While the jit-uuid library creates

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.

count(1) for queries does not work on UI

Is your enhancement proposal related to a problem? Please describe.

Documentation for the feature is very high level without any details on how it can be used and examples. https://docs.zephyrproject.org/latest/guides/debug_tools/gdbstub.html

Describe the solution you'd like
A more detailed documentation of the feature with some step by step instructions on how it can be used.

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