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.

Multiple Explore-related components still make use of GrafanaTheme.
Since Grafana 8.0 introduces GrafanaTheme2 and deprecates GrafanaTheme we should migrate to the new theme.

This should probably be done in multiple small PRs that target a small amount of components to make review easy.

Also the following data sources have components that need to be migrated:

• Elasticsearch

Keyboard navigation in the control panel of the Explore view is difficult.

Expected results

You should be able to move focus between adjacent controls in the control panel with a single Tab key press
and visually distinguish what element has focus. You should be able to interact with controls the keyboard
(Enter or space bar for button-like things).

Actual results

Several tab

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

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

Bug description

Some of our dashboard tags don't show up due to the color scheme mixed w/ our app BG.

Expected behavior

Dashboard tags are easy to read against the app background.

How to reproduce

1. Go to Dashboards in our app
2. Look at the 'big-5' or 'core-experience' tag

Environment

• PostHog Cloud
• self-hoste

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

When you change a query state filter e.g. showing 'Finished' queries or 'User Error' queries, the Show Limit is not respected immediately resulting in all queries being rendered. If a re-order interval is set then Show Limit is applied on the next query refresh. If there are a large number of queries in the history this can result in the browser crashing on the first render.

The following two c

Use Case

Currently to populate the description of a @pipeline(), you have to specify the description in decorator keyword arguments.

@pipeline(
   description="Download, process, and transform HYCOM data for a date"
)
def daily_hycom_download():
    date = input_date()
    hycom_ds_for_date(date)

This differs from @solid(), which will use the functions docstring fo

In strptime as compiled for Emscripten, when given the US locale string format ("%m/%d/%Y, %I:%M:%S %p"), it incorrectly parses "12:00:00 AM" as "12:00:00 PM". In order to fix this, we will need a custom-written string parser similar to the CustomISO8601Parser from arrow_csv.cpp. This parser uses the