analytics

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.

Screenshot

Description

chart 3 dot menu is behind the chart title panel in chart maximize mode

Describe the bug
If I pass 'Next 7 days' into the dateRange in query, the response is not a range over the next 7 days but only the day IN 7 days.

To Reproduce
Steps to reproduce the behavior:

1. Build a query like this:

const query: Query = {
    measures: [
      measure
    ],
    timeDimensions: [
      {
        dimension: 'Your.Dimension,
        dateRange: 'Next 7

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.

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

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.
By default, we use emails are distinct_ids to list users on insights (in person modals and funnel list of people). Some users might have a different label for their persons are prefer to use the distinct_id they passed in rather than the email.

Describe the solution you'd like

We should allow users to switch back and fo

Related with nunomaduro/phpinsights#23 will be a great idea to allow set all commands parameters from config/insights.php when is used with php artisan insights.

Maybe something like:

'parameters' => '--format=json -d memo

In the past a conversion through Number "interface" has proven to be able to mask bugs in the code.
We should remove these conversions from io.trino.spi.type.TypeUtils#writeNativeValue.

I made a "dagster-internal" resource (instead of "dagster_internal") and didn't find out that was a problem until pipeline execution: https://dagster.phacility.com/P231

We should have everything we need to disallow that at definition time