When I select the ruler, ruler-logs or alertmanager datasources, I get an empty query editor. We should just not show them.

User now can change X AXIS FORMAT in time series charts and see date format on rich tooltip. However, the first date of the month is always missing its full time format in tooltip. (e.g. 1/1/2021 is displayed as Jan 2021) see video

https://user-images.githubusercontent.com/67837651/107318140-ef522c80-6a50-11eb-9447-3ee3be094592.mov

<img width="294" alt="Screen Shot 2021-02-08 at 9 05 58 PM"

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

Summary

When a function has print('sth', file=sys.stderr) in the body I get:

InternalHashError: [Errno 2] No such file or directory: '<stderr>'

While caching the body of eval_models_on_all_data(), Streamlit encountered an object of type _io.TextIOWrapper, which it does not know how to hash.

Steps to reproduce

Code snippet:

@st.cache
def f():
   prin

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

The expressions editor window includes a Help tab that has some plain-text information about each variable and function.

I am editing this text right now to match the user manual. I'd like the fields to render with links (they currently just have full URLS that users can copy-pa

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