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

NOTE: we'll need to verify that this is indeed what we want the behavior to be before doing any work on this.

Consider the following sequence of actions a user might take

1. Populate a config.toml file by running streamlit config show > ~/.streamlit/config.toml
2. In the file, change the server.port config option to something other than 8501 (the default), let's say it's changed to 8502

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

To Reproduce

Configure a reconciliation service that returns URIs as IDs.

Hovering over reconciliation suggestions, automatically matched values and manually mapped values will fail to retrieve the preview information as ID contained in the callback is truncated.

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