The docker container we're using has 2 vCPUs. -p=8 was working fine for
a while, but diagnosing #1832 looks like the tsi1.test process was
likely getting OOM-killed. Reducing from -p=8 to -p=4 ought to reduce
memory pressure enough to avoid OOM kills, hopefully.
Also remove a stale TODO.
- Ensures that a SingleStat inside a TimeMachine can be resized
- Ensures that a SingleStat has the approriate border raidus when used
in a cell or TimeMachine
Moves the check to determine if a series has data for the current time
range into the groupBySort function, which is consistent with the
groupNoneSort function.
* Introduce Labels components
* Export label type from clockface
* Make component spacer behave as expected
* Include padding so IndexList rows scale more gracefully
* Allow optional truncation of labels in list with tooltip
* Add option for displaying a delete button on a label
* WIP introduce label selector component
* Flesh out suggestive functionality including keyboard support
Co-Authored-By: Delmer <ofthedelmer@users.noreply.github.com>
* Enable scrolling in labels widget
Also doing a handful of things to improve usability
Co-Authored-By: Delmer <ofthedelmer@users.noreply.github.com>
* Make linter happier
Changes the gauge and single stat visualizations to use their decimal
place option more literally. For example, if the decimal place option is
set to 2 digits, then every number in the visualization will be
formatted with 2 digits after the decimal place. Previously, this option
was ignored altogether, and seemed to be programmed to mean “display at
most 2 digits after the decimal place”.
- Allow deleting the input entirely
- Only reset value if mode has changed, even if a mode button is clicked
- Emit changes to the input value consistently
* fix(testing): compare expected error messages against actual
* remove nonsense
* remove nonsense
* add expected error message for bucket not found
* oops
The test used `AND` instead of `and` which is not valid syntax. It also
did not include packages and imports in the generated JSON from parsing
the flux query.
Report the total number of gets, puts, and deletes at the end of the
test. I've found this kind of output to be a useful sanity check in
similar tests that exercise concurrency involving tasks.
Use a local random source in each goroutine. I unscientifically
eyeballed that to increase total operations by 5-10%.
Also call t.Parallel in a few more tests that involve disk access. This
shaves 1-2 seconds off the full tsi1 test suite on my machine.