Feature idea summary

Cgroups plugin supports only proportional and max Block IO policies. We should support BFQ scheduler as well. Disk stats for the scheduler are in blkio.bfq.io_service_bytes and blkio.bfq.io_serviced files.

Next line returns 200 as status https://github.com/Kong/kong/blob/c817fada7a514d84f6e0aab7461605c71bf3a841/kong/plugins/cors/handler.lua#L13

Internet says it should return 204:

• https://developer.mozilla.org/en-US/docs/Glossary/Preflight_request
• https://docs.microsoft.com/en-us/aspnet/core/security/cors?view=aspnetcore-3.1#preflight-requests

Internet changed its mind since 2018 https://

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
The documentation for Installing Salt for development feels like it's out of date https://docs.saltstack.com/en/latest/topics/development/hacking.html . One example is that it seems to indicate that Python2 should be used:
On Arch Linux, where Python 3 is the default installation of Python, use the virtualenv2 command instead of virtualenv.

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

MeshNormalSmooth() takes a vertex and iterates all the others, looking for vertices with a distance < epsilon.
Then it calculates their normals and sums it.

That's not a good idea, IMO:

• Two close vertices can be not physically linked, I don't think summing normals makes sense.
• It's quadratic.

A simpler and faster way to smooth a model could be:

• Iterating through each triangle

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

Installing microk8s with sudo snap install microk8s --classic appears to go fine, but microk8s status always reports as microk8s not running. microk8s kubectl get all --all-namespaces shows everything as not ready and pending.

Ubuntu 20.04.1 Desktop, network-interfaces are ens33, lo, virbr0 and virbr0-nic, so nothing particularly exciting there. The flannel - interface you'd get with an e

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

So far we don't enable the SNI extension when communicating with upstream. We should enable this feature by enable proxy_ssl_server_name.

What would you like to be added/modified:

To improve project stability, we need more tests to cover corner cases.
And the code coverage is around 50% currently, we need to add more tests to improve it.

To improve case coverage, we may need a list of cases to track the work.
For code coverage, simply check bef