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.

When using right Y-axis, the first (rightmost) legend label is hard to click. Only a small fraction on the left side of the label is actually clickable. Almost impossible to hit on touch devices.

I assume this is due to the negative margin of the parent item (<div class="view" ...>)

![recording](https://user-images.githubusercontent.com/12658837/93191834-46273480-f745-11ea-8eb8-3c9921a5b

Screenshot

Using Superset 1.0.1

Here for dates fields :

Here for some prices

Description

When analysing data in a table, one expects them to be ni

Now insert and query share the resource ( Max Process Count control) 。 When the query with high TPS，the insert will get error (“error: too many process”). I think separator the resource for Insert and Query will makes sense. Ensure enough resource for insert。It looks like Use Yarn， Insert and Query use the different resource quota。

Or the simple way , Can we set Ratio for Insert and

Describe the bug

I want to connect to Redis Memory store in GCP and got the following error:

Error: Redis connection to <port> failed - unable to verify the first certificate at TLSSocket.onConnectSecure
(_tls_wrap.js:1502:34) at TLSSocket.emit (events.js:314:20) at TLSSocket._finishInit (_tls_wrap.js:937:8) at
TLSWrap.ssl.onhandshakedone (_tls_wrap.js:711:12) 

*To Reproduce

Before opening, please confirm:

• I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
• I have searched for duplicate or closed issues.
• I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-cli/blob/master/CONTR

When entering a repository path, users should be able to hit TAB for autocomplete, like in bash.

it's becoming more time-consuming and error-prone to manually re-test all the demos following internal refactorings and API adjustments.

now that the API is fleshed out a bit, it's possible to test a large amount of code (non-granularly) without having to simulate all interactions via Puppeteer or similar.

a lot of code can already be regression-tested by simply running all the demos and val

Is your feature request related to a problem? Please describe.

There are parts of the website that can use improvements in increasing the accessibility of the website.

**Describe the solution you

Bug description

When using the identify API in posthog-js, we are passing some data which could cause malformed URL's i.e. "Men's Fashion".

If I do not URL encode this, it shows in Posthog as Men's Fashion, if I do URL encode this, it shows in Posthog as Men%27s%20Fashion.

Expected behavior

If the property is URL encoded, I expect this to be decoded on receipt by Post

Would be great to have a config option to disable the "version" check of the composer.json of ComposerMustBeValid.

• [Architecture] Composer.json is not valid:

composer.json: The version field is present, it is recommended to leave it out if the package is publi

Feature Request

Description of Problem:

When transforming tables/creating views, a join or list operator to apply to the underlying grouped sets would be helpful for debugging.

Potential Solutions:

Support join operator on client side table aggregate views.