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.

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

Description

let's say I have an apache process group I want to control.

• when using supervisord.running, the name must be apache:* (which is the same notation used by supervisor)
• when using supervisord.dead, the name must be apache: (without the *)

As both states mirror each other, I expect them to use the same convention for name, the one from running since it

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

在Consumer中添加 consumer-restriction 插件，里面的 type 能否支持下route_id，这样我们就能基于 consumer 的纬度来限制能访问到的 route，现在的版本我看了下只支持 consumer_name 和 service_id，即只能在 route 纬度来限制 consumer 或者 只能在 consumer 纬度来限制能访问的 service。

需求场景：同一组service下可以有多个route，但是可能有部分route是不用鉴权的或者需要额外申请才给开通，如果能在consumer纬度支持一下 route_id，那样就能更精细化的赋权，且不用每个用户来申请权限都需要对route接口发起一个PATCH请求。

插件文档：https://apisix.apache.org/docs/apis

When you run "microk8s add node" you get output that looks like:

From the node you wish to join to this cluster, run the following:
microk8s join 10.220.113.121:25000/199cfabfeabc905c629ad98d93be964a/d86a2309e376

If the node you are adding is not reachable through the default interface you can use one of the following:
 microk8s join 10.220.113.121:25000/199cfabfeabc905

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

Is your enhancement proposal related to a problem? Please describe.
Refer to: zephyrproject-rtos/zephyr#28932

Describe the solution you'd like
Refer to: zephyrproject-rtos/zephyr#28932 (comment)

Describe alternatives you've considered
NA

Additional context
NA

Scenario

create table tab(f float);
insert into tab(f) values(4273.8);

Results in: org.postgresql.util.PSQLException: ERROR: inconvertible types: DOUBLE -> FLOAT [from=4273.8, to=f]

Expectation

Possibly enhance type compatibility check (SqlCompiler.isAssignableFrom) with extra cases for numeric types:

• Float <- Double: if the double fits in the Float, then

How are you planning on using kubeedge?

I've been looking for something like this for a long time (Currently our team uses Rancher although their product wasn't really meant for edge computing.) I'd love to hear how others in the community would like to use this so I can compile a list of use cases that kubeedge can support out of the box.

Thanks!