This is kind of a follow up to #32677 and the PR #34762.

In #34762 we improved the test data source implementation by checking the body of the response from Tempo. The Tempo team is not comfortable making the body of a 404 response part of our stable API, so instead we are currently adding a separate endpoint specifically for testing: /api/echo (grafana/tempo#714).

Screenshot

Description

chart 3 dot menu is behind the chart title panel in chart maximize mode

Summary

date_input widget should throw an exception if value not in (min_value, max_value) range.
An exception should be thrown also in case of range input, when left and right values of a provided interval are less (or great) than min_value or max_value.

Steps to reproduce

Code snippet:

For single value

import datetime as dt
import streamlit as st

x = st.date

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

Bug report

Bug summary

Adding a legend to a SubFigure doesn't work

Code for reproduction

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

I would like to import a .zst or .zstd file but currently that file type is not recognized to be imported by OpenRefine.

Proposed solution

Perhaps using Apache Commons Compress (we already have usage in ImportingUtilities.java)
https://commons.apache.org/proper/commons-compress/examples.html#Zstandard

Allow importing the .zstor .zstd file from my local computer, as well as fr

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