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

Right now all our Vega-Lite based charts (st.altair_chart, st.line_chart, etc.) follow the user theme. For st.map and PyDeck it's not as easy to make them follow the exact theme, but we could at least make them use the dark map style when the app is show in Streamlit's dark theme with no overrides.

This line currently fixes the

In recent versions (can't say from exactly when), there seems to be an off-by-one error in dcc.DatePickerRange. I set max_date_allowed = datetime.today().date(), but in the calendar, yesterday is the maximum date allowed. I see it in my apps, and it is also present in the first example on the DatePickerRange documentation page.

E

We have a PowerNorm. We should define a PowerScale derived from a PowerTransform consistent with the log norm, etc. This will allow a proper scale for PowerNorm. I'm not exactly sure what such a scale should look like (i.e. where to put the ticks), but its probably not a linear scale.

The y-axis ticks supports the rotated option, but the doc is missing.

I haven't checked whether other options are missing.

Bugs and Questions

Checklist

• This is not a victory-native specific issue. (Issues that only appear in victory-native should be opened here)

• I have read through the FAQ and Guides before asking a qu

OpenRefine 3.4.1 on Windows (with or without integrated JRE) does not use the proxy set in openrefine.l4j.ini to connect to reconciliation service (https://lobid.org/gnd/reconcile)

To Reproduce

Steps to reproduce the behavior:

1. First, set proxy in openrefine.l4j.ini using the following parameters:
   -Dhttps.proxyHost=proxy-name.domain.ch
-Dhttps.proxyPort=8080
   `-Dhttp.proxyHo

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