If the reader produces more than one table with the same group key, we
discard the later ones because the stream should never give us more than
one table with the same group key.
This is an error and it indicates the server sent us a bad set of data.
This change makes it so that the client is tolerant of that data and
will discard it if it exists.
* Move current check to TimeMachine alerting
* Unify RemoveButton actions in to ConvertFromCheckView
* Unify AddCheckDialog actions
* Switch saveCurrentCheck to saveCheckFromTimeMachine
* Remove current check from checks reducer
* Change getCurrentCheck to getCheckForTimeMachine
* Get Check along with view in EditcheckEO
* Tidy imports
* Import Actions With on...
* fix module name
* Remove check fixtures
* adding new templates; removing calls to create templates
* fixing quickstart dashboard creation
* Type dashboard template
* bump templates repo version
* add templateID to template meta in swagger
* Add templateID to document meta type in UI
* add templateID to telegrafPlugin and telegrafplugin info types
* Instantiate templates from static templates
* Get tests to pass
* Fix type conflicts
* Bump templates version
* update changelog
Disables running ESLint through the fork-ts-checker-webpack-plugin in
development, due to its tendency to overuse CPU.
I think this OK since linter errors, unlike typechecking errors, are
usually confined to the file you are working within. So they're a good
fit to run via an editor, rather than the build tool.
* refactor(ui): replace instaces of AutoInput with Clockface
* refactor(ui): delete local AutoInput component
* refactor(ui): ensure null gets passed back when bin count is set to auto
* refactor(ui): convert BinCountInput into a stateless component
* refactor(ui): convert BinCountInput to function component
* Fix editVEO check saving
* Get checks at dashboard load
* Fix check queries type
* save View before saving check in VEOs
* Get checks from checks list for checkPlot
* Add check view properties to backend
* Match Alerting Button to CheckAlertingButton
* Remove thresholds from default check
* Remove explicity declaration of check view type in query views
* Pass check down to CheckPlot
* Fix clashing action calls
* Fix calling check type change action from dispatch
* Only check for checkView if view is defined
* Remove type when spreading new check on to default check
* Fix check edit route in check cards
* Get checks for dashboard earlier
* Clean up getCheckForView selector
* refactor(ui): replace instace of local Form with clockface
* refactor(ui): replace Form in token overlay
* refactor(ui): replace Form in label overlay
* refactor(ui): replace Form in danger overlay
* refactor(ui): delete local form layout components
* refactor(ui): replace instances of local confirmation button with clockface
* refactor(ui): delete local confirmation button
* refactor(ui): fix affected e2e tokens test
* refactor(ui): polish appearance of alerting index view
* refactor(ui): ensure alert check editor header has proper padding
* refactor(ui): emphasize alerting button more
* refactor(ui): style check builder control bar
* refactor(ui): allow buidler card to have a customizable width
* refactor(ui): expose autohide prop from dapperscrollbars within buildercardbody
* refactor(ui): allow dashed button to have configurable color and size
* refactor(ui): add placeholder buttons in to thresholds card
* refactor(ui): add custom styles for alert builder cards
* refactor(ui): increase height of status message template
* refactor(ui): add empty state to matching rules card
* fix(ui): reconnect checks list to redux
* refactor(ui): use more appropriate copy in endpoints empty state
* Use CheckPlot to visualize check view
* Revert to add threshold types
* Disable view type dropdown in checkView
* Add proper equality
* Add errors in default cases
This will only attempt to parse an error as JSON if it has the content
type `application/json` so that it stops trying to parse the result as
JSON when it isn't JSON.
While the real error message is included, the addition of the "could not
parse json" makes it very confusing to read and distracts from the real
issue.
Changes our error reporting strategy for Honeybadger from "report
everything logged by `console.error`" to "report everything caught by an
error boundary".
As before, Honeybadger still reports everything caught by
`window.onerror` as well.
* chore: add new types for NotiicationRules
* build(client): remove client and build each build
* chore: update gitignore to exclude generated client
* fix: allow client dir to be empty
* docs: add README to client dir
* fix(build): add autogen client to eslintignore
* build: gen client for ci js tests
kelwang
Kelvin Wang
Jonathan A. Sternberg
Lyon Hill
Deniz Kusefoglu
Christopher Henn
Russ Savage
kelseiv
Edd Robinson
Nathaniel Cook
Stuart Carnie
alexpaxton
Alirie Gray
Andrew Watkins
maxunt