* chore(ui): Remove unused references to timeRange
* chore(ui): Add comment to timerange to duration function
* chore(ui): Fix getTimeRangeVars.test
* Refactor getTimeRangeVars.ts
* chore(ui): Remove references to zoomed time range
* chore(ui): Remove unused set dashboard time range v1 action
* chore(ui): Add preliminary timeRange types
* chore(ui): Add init pass at reasonable timeRange constants
* chore(ui): Finish Remove unused set dashboard time range v1 action
* fix(ui): Conver redux ranges state to object from array
* chore(ui): Read from and write to ranges local storage
* chore(ui): Reorder imported things
* chore(ui): Add typing to timeRanges from query params and localstorage
* chore(ui): Fix Dashboard and DE Time Range Dropdown
* chore(ui): Fix check timeRange
* chore(ui): Convert duration time Ranges to custom for time range dropdown
* chore(ui): Convert delete with predicate timeranges to TimeRange types
* chore(ui): Convert predicates timeRange to custom
* chore(ui): fix ValidateAndType bug
* fix(ui): Fix show bucketname in delete data form
* fix(ui): Allow timeRange to handle all duration time Ranges
* chore(ui): Separate DeleteDataOverlay update logic
* fix(ui): Fix deletedata overlay dismiss routing
* chore(ui) cleanup
* chore(ui): Allow timeRange dropdown to work with no prior timeRange selection
* chore(ui): Remove unused import
* fix(ui): Fix time Ranges tests
* fix(ui): Fix tests
* fix(ui): Fix tests
* fix(ui): Extract label creation function and use where needed
* fix(ui): Fix predicate testing
* fix(ui): Fix prettier issue
* chore(ui): Refactor duration.ts
* chore(ui): Remove labels from timeRange
* chore(ui): Return label for selectable-duration label
* chore(ui): Resolve merge error
* chore(ui): Make tests more robust
* feat(ui): protect query params access with get
* chore(ui): Add comment to warn against regex behavior
* Apply prettier to predicates.test
note: tests are seriously borked here. Cannot reuse any existing testing
as the setup is very particular and the http layer doesn't suppport everyting.
that being said, there are goign to be implicit testing in the
`launcher/pkger_test.go` file. This feels broken, and probably needs to be
readdressed before we GA a 2.0 influxdb....
* fix(e2e): flakey query builder test
* test(e2e): run test 50 times
* test(e2e): run update label test 50 times
* fix(e2e): visit page after creation
* chore(e2e): run test once
* fix(e2e): run update label test once
this is a step towards providing a shared http client that manages pooling connections,
timeouts, and reducing GC for by not creating/GCing a client each req. Bring on the red!
tests failign from a data race caused in the tests setup. an incrementing
const needs something to serialzie it (atmoic in this case) to remove that
data race. This touches that up.
governs the concurrency with a simple semaphore. Defaults to 5
concurrent reqs, anything greater, could put a lot of pressure
on the system as a whole (especially OSS/bolt store).
This change ensures the following behavior:
* task LatestScheduled is always set when a task is updated and
transitions from a status of inactive to active
* task LatestScheduled is non-zero when created, to set the initial
schedule time as some point after it was created
In addition, the kv.Service introduces clock.Clock that is used for
task create and task updates only. This change permits testing
in a deterministic fashion.
* chore(ui): point to local build
* refactor(ui): repair breakage from update
* chore: Revert "chore(ui): point to local build"
This reverts commit 968a8232cc.
* chore: upgrade dependency to 1.1.0
* chore: appease prettier
* fix: correct typo
* fix(ui): give size to AlertColumns and update e2e tests
Now, traces will have all headers except authorization and user-agent.
Additionally, I've removed the referer and remoteaddr as they did not
contribute much.
Eventually, this may change to just a small set of headers to record.
This removes the bucket name validation from the KV BucketService,
and moves it to the http implementation of the service.
The effect is that API user requests still get validated but direct KV access does not