* 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()`.
1. Removing dashboard changes from earlier commit
2. Changing inital state variable name to just be endpoint
3. moving dispatch in check actions
4. Adding notification to endpoints
These are the final tests and rule fix for this issue.
The checks is special in how it was fixed.
But endpoints and rules have the exact same fix on them
All the tests are running smoothly
EsLint was run so this branch should no longer fail from that as well.
1. We fixed the endpoints so it no longer routes to 404 page, instead now routes to the alerting index. When endpoint id does not exist.
2.Added Cypress test to confirm the routing works on checks. Routing the user to the index page when the checks id does not exist.
this fix allows the DI of the vault service configuration. There are place
where we'd like to adminster this with flags, but are locked into
the default env var setup we had previously. One other note is that
calling api.DefaultConfig() calls the ReadEnvironment() method already,
so that was dropped.
hopefully this commit doesnt do anything, but it opens up the ability to
change the static folder of the project through the environment variable
STATIC_FOLDER so that we can cache static files and not cache the index
file (allowing more passive deployment strategies), and allows the user
to change the base path of the project with the BASE_PATH variable,
opening up the ability to run an instance behind an nginx proxy,
though that change is pending an update to the @influxdata/oats package
before we can turn it on
Andrew Watkins
George
Jonathan A. Sternberg
Zoe Steinkamp
Bucky Schwarz
Johnny Steenbergen
Alirie Gray
Russ Savage
Bucky Schwarz
Johnny Steenbergen
David McKay
Alex Boatwright
Ariel Salem
Scott Anderson
Deniz Kusefoglu
kelwang
docmerlin (j. Emrys Landivar)
Lyon Hill
alexpaxton