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

The issue #52359 was fixed and merged into develop, but no further steps have been taken to bring the changes to the master branch; the bug is still present in the latest version.

https://docs.saltstack.com/en/latest/topics/development/git/index.html states develop as the main development branch, but [https://docs.s

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

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

Deploying microk8s on an environment that does not allow access to public domain servers I discovered that the DNS add on is deploying coredns configured with google dns servers hard coded as the default forwarders. It would seem a better option would be to use the hosts DNS configuration rather than a public server that may or may not be allowed on the system.

Referencing https://kubernetes.io

Is your enhancement proposal related to a problem? Please describe.
This is related to #28900 and will be used to improve management of pages in the virtual address space, which currently can be allocated but not freed. We want to manage the address space using a searchable bitfield instead.

Describe the solution you'd like
For a bitfield defined with something resembling:

sta

• we only test HS256 algorithm, not cover HS512 and RS256
• not test unsupported algorithm, for example HS384. we need throw the unsupported alg msg from https://github.com/SkyLothar/lua-resty-jwt/blob/master/lib/resty/jwt.lua#L505

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