The basic auth headers use a function that will soon be in flux that
renders usernames and passwords into `Basic <b64 u and p>`
This work assumes that AuthMethod has been set as well as the
appropriate secrets
When parsing a Flux CSV file with hundreds of thousands of lines for the
"Raw Data View", we would see a
Maximum call stack size exceeded
error. This was because every line in the CSV was being passed as an
argument in a single `Array.prototype.push` call, and there are
[limits][0] to how many arguments can be passed to a function.
This commit avoids passing the arguments all at once.
[0]: https://stackoverflow.com/questions/22747068/is-there-a-max-number-of-arguments-javascript-functions-can-acceptCloses#14566
We chose pretty arbitrary data from monitor to add to the pagerduty
schema.
We'll need to see how this renders and make adjustments.
Co-authored-by: Alirie Gray <alirie.gray@gmail.com>
The easiest path forward for fixing
https://github.com/influxdata/influxdb/issues/14966 is to have the UI
use put instead of patch for updating checks. Long term, we will want to
be able to use patch, but as of now patch is not functional.
For whatever reason, we now have xy views stored with an empty array in
the `colors` field. Attempting to open the visualization options for
such a view results in a crash.
This commit updates the `ColorSchemeDropdown` to access the `colors`
field more defensively.
Closes#14950
This avoids a module error in Go 1.13 from a poorly tagged transitive
test dependency that looks like:
gopkg.in/stretchr/testify.v1/assert: go.mod has non-....v1 module path
"github.com/stretchr/testify" at revision v1.4.0
The `v1.databases()` call did not correctly filter buckets based on
auth. Fortunately, it did not cause any improper permissions such as
allowing a person to see buckets that they had no read access to.
The error instead was that if a user did not have read access to one of
the buckets that was returned, the entire command would fail rather than
filter out the bucket that didn't have permissions.
This changes it so that if the user doesn't gets an unauthorized error
when accessing a bucket, it will filter it from the list instead of
failing. It also changes it so the error message is marked as
`ENotFound` instead of as an internal error.
e2e tests are failing because the fancyscroll bar component hides
the admin step during certain points in onboarding.
We were able to reproduce when the form in the admin step had been
marked as valid.
The use of the scrollbar in the setting seemed unneeded as it could
be rendered in a quite small window.
Therefore, we removed the scrollbar altogether for now.
Co-authored-by: Christopher Henn <chris@chrishenn.net>
Nathaniel Cook
Andrew Watkins
Chris Goller
Michael Desa
Alirie Gray
Christopher Henn
kelwang
Kelvin Wang
Russ Savage
Jade McGough
alexpaxton
Mark Rushakoff
Jonathan A. Sternberg
Stuart Carnie
Ben Johnson