Kevin Lim

I think the fix to this would be to auto-generate a `tab_id` for `Tab` objects in the case that it's not explicitly defined.

There's no tab_id property ```python app.layout = dbc.Container( TABS := dbc.Tabs( children=[ TAB_1 := dbc.Tab(label="tab_1"), TAB_2 := dbc.Tab(label="tab_2") ] ], dbc.Row([TABS_CONTENT := html.Div()]) ) @callback( Output(content, "children"), Input(TABS, "active_tab"), )...

@tcbegley is that example good enough?

Thanks, so there's no chance the implementation is going to change to pre-create the id in the backend? I can deal with the workaround, but I think it'd be nice...

Is it not the case where length is already implicitly accounted for in the algorithm (since you're summing the strains + a decay factor)? Looks like to me, you could...

Wondering if there are any updates on this, a shame that object_store doesn't implement AsyncSeek et al. (not sure if this would be possible). But ideally, the common interface between...

This would be very cool 👍

Curious if there has been any progress made on this front? I similarly to https://github.com/hyperium/hyper/pull/2711 want access to the `Kind::Io`. It's a little tricky writing opinionated wrappers with hyper/reqwest due...

Anyone run into this?

Curious if this proposal would allow custom clocks? When using an rolling_interval, could you for example (lets say you have a column that are seconds from some epoch (as opposed...