* chore(ui): upgrade clockface dependency
* refactor(ui): update components affected by breaking changes
* refactor(ui): update test snapshots
* refactor(ui): remove obsolete component
* refactor(ui): remove reference to non-existant stylesheet
* refactor(ui): update selector in e2e collectors test
* refactor(ui): attempt to fix e2e test
* refactor(ui): appease linter
* refactor(ui): update implementation of client library cards
* refactor: update all breakage from new version
* refactor: revert this commit
* refactor: fix popover by using useRef instead of createRef
* fix: update all instances of EmptyStateText
* fix: update all instances of PageHeader
* fix: update straggler empty state text
* fix: update instance of PageHeaderCenter
* fix: update instance of PageContents
* fix: update style rule for dashboard cards
* chore: update test snapshots
* refactor: update instance of question mark tooltip
* refactor: use brighten prop to ensure contrast with background
* Revert "refactor: revert this commit"
This reverts commit f325916d91.
* chore: upgrade to NPM package instead of local
* refactor: fix css import
* refactor: update test snapshot
* refactor: Guard against string being null
Co-Authored-By: Alex Boatwright <alex@drdelambre.com>
* refactor: move resource getter inside overlay so it does not disrupt layout
* refactor: fix unit test by updating selector
* refactor: guard against name being absent
* chore: upgrade to latest clockface to utilize a bugfix
* chore: update snapshot test
* refactor: fix appearance of searchableDropdown
* chore: upgrade dependency (again) for bugfixes
* refactor: fix labels e2e test
* refactor: fix tokens e2e test
* refactor: appease linter
* chore(flux): update Flux function docs with experimental and 0.50 functions
* removed unnecessary newlines from fluxFunctions.ts
* fix(fluxFunctions): add space before param
The controller now supports setting an initial memory limit and setting
a maximum amount of memory that the controller may use separately from
the memory quota per query and the concurrency quota.
This allows the controller to increase the concurrency quota to a larger
number while setting the maximum amount of memory to a lower amount than
would be required for all queries to use 100% of their allowable memory.
Functionally, this means that a query will have a soft limit for an
initial memory byte quota that a query is guaranteed to have, a shared
pool that it is allowed access to in the case it uses more, and a hard
limit that no query may exceed to prevent runaway queries from taking
over the entire pool.
This change is completely backwards compatible with older configurations
as the new options will default to values that mimic the old behavior
where a query is allocated the full amount of its memory quota and the
maximum amount of memory is based on the concurrency quota and this
maximum memory quota.
In addition to the above, this also fixes a bug in the controller that
allowed it to run more than its concurrency as executing queries. This
happened when the results had finished being sent by the executor, but
the query had not yet been read and/or serialized. The executor would be
freed up and would take the next query even though the previous query
hadn't yet been finalized with `Done()`.