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.

This is kind of a follow up to #32677 and the PR #34762.

In #34762 we improved the test data source implementation by checking the body of the response from Tempo. The Tempo team is not comfortable making the body of a 404 response part of our stable API, so instead we are currently adding a separate endpoint specifically for testing: /api/echo (grafana/tempo#714).

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

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?

When an event's definition is scoped to a DOM element and the HTML structure of the page changes, the event is obviously unusable. But it isn't entirely clear until after you try graphing the event that something is wrong with the definition.

Describe the solution you'd like

A simple fix would be to display an alert indicating the even

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

io.trino.tempto.assertions.QueryAssert#assertThat(QueryCallback) is deprecated.

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