rill

rill copied to clipboard

get profiling back to perceived "magical"

2

Profiling has gotten much slower since May. I think there are some easy solutions to this. 1. it would be nice if we re-ordered the queue a bit. Right now,...

hamilton

AdityaHegde

AdityaHegde

Create a proposal for state modularization

1

Map out how we'll move application state out of the server and into the client. Consider a query-caching library (like RTK-query or svelte-query) and consider the resulting scope of the...

ericpgreen2

add a default label+description to the measure created by the "quick metrics" button

3

To help illustrate to users what the default populated measure means, we should add a defaul label "events per time period" and a default description "the number of events recorded...

bcolloran

This is a POC for duckdb golang driver. Has local copy of the driver library until Interval support PR is merged. (Job will fail since we are not installing and...

AdityaHegde

I love this "query in workspace" action. It needs a few tweaks to be more useful: - [ ] we should explicitly select all the columns in the model, not...

hamilton

humanized leaderboard numbers should probably take into account all the data

1

I think it's a good idea for us to figure out how to avoid cases like `1345.4k` (would expect `1.34m`) in the leaderboards and `40.0k` in the axes (would expect...

hamilton

rescaling animation lines and scales in line charts can create some disorienting effects

2

**Describe the bug** the scales and lines rescale at different speeds, which can cause jumping around or rubber-band ish effects, particularly when toggling a filter that removes/adds a lot of...

bcolloran

Axes ticks should be more appropriately spaced

1

For a set of time ranges, generate an axis at a bunch of breakpoints. Each one of those breakpoints should look good & provide the info we need. A PR...

djbarnwal