Currently, after user editing a metric in Edit dataset modal in Explore, the edited metric jump to the bottom of the metric list.
it create a few issues:

1. when the metric list is long, by dropping to the bottom, user might take a while to find it or think the most recent edited metic is lost.
2. every time users edit a single metric, they see a different order of metric list showing in 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

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

Test the Column / Text filter

Proposed solution

Add a test for the behavior with

• an exact string, check the number of occurrences
• a partial string, also check the number of occurrences
• Test case sensitive
• Test a regular expression

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