Currently the tabs on SQL Lab queries show green circle when a query is running as well as when a query has successfully finished.

The green circles for "query running" and "query completed" could be made more distinct - different color, or having the "query running" circle be hollow, and the "query completed" one filled in. This would enable users, who might go to SQL Lab and trigger few quer

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

This bug is actually caused by #2989, but I'm filing it separately as fixing #2989 may end up being a few days worth of effort while a small workaround to fix this apparently incorrect behavior (that's just a bandaid until the real issue is fixed) would likely only take a couple hours.

What happens here is that a file calls config.get_option on import, causing config files to be parsed, then wh

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

When a user first logs into Wikidata, or logs out through the Manage Wikidata account option of the Wikidata extension and then logs in, the UX leaves the user wondering what happened since the login dialog disappears, leaving the user to assume they logged in successfully.

Proposed solution

Ideally, the current "logged in" dialog (bind="explainLogin") could actually be shown immedia

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