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

Serverless: Deprecation warning: Variables resolver reports following resolution errors:
              - Cannot resolve variable at "provider.environment.CUBEJS_APP": Value not found at "self" source,
              - Cannot resolve variable at "functions.cubejsProcess.events.0.event.resource": Value not found at "self" source
            From a next major this will be

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

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

Allow redirecting clients to an alternative location to fetch query information. This can be configured via the query.info-url-template configuration property. (#7678)

Use Case

Commonly used aliases for --help and --version

Ideas of Implementation

-h for --help and -V for --version

Message from the maintainers:

Excited about this feature? Give it a 👍. We factor engagement into prioritization.