Summary

All Streamlit widgets and elements fade when the app is rerunning. But this is not happening for st.expander.

Steps to reproduce

Code snippet:

import streamlit as st
import time

time.sleep(10)  # Makes it easier to see the bug

st.write("This fades correctly")
st.button("This too")

with st.expander("This doesn't fade"):
  st.write("but this fades")

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 summary

The only way (that I am aware of) to control the linewidth of hatches is through an rc parameter. But temporarily modifying the parameter with plt.rc_context has not effect.

Code for reproduction

import matplotlib.pyplot as plt

plt.figure().subplots().bar([0, 1], [1, 2], hatch=["/", "."], fc="r")

with plt.rc_context({"hatch.linewidth": 5}):
    plt.

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

The Problem

While I was debugging another issue, I noticed that the example included two bars with the same x and y values, and when you mouse over one of these bars both tooltips show up. It seems like Victory uses the x/y value to determine whether the tooltip is active when there is not another identifier.

Reproduction

https://codesandbox.io/s/frosty-du

There is no easy way to navigate up the parse tree provided by jsoup selector syntax. We currently can navigate down very easily with Jsoup's selector syntax value.parseHtml().select("div > p") and also `value.parseHtml().select("div:has(@) ~ div") but
this is not directly allow DOM traversal itself. However, Jsoup conveniently provides DOM traversal for finding a https://jsoup.org/apidocs/o

Hi!

My suggestion/request is simple. When filtering the data, sometimes one needs to use the edge values of the data distribution in the filter histogram.

For example, one wants to choose the data of an hourly distribution (from 0:00 to 24:00) for the time between 22:00 and 6:00 in the nighttime and discard the data from 6:00 till 22:00 during the daytime.

So, when filtering the data with

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

When entering a repository path, users should be able to hit TAB for autocomplete, like in bash.