* # This is a combination of 2 commits.
# The first commit's message is:
added writeData command
# The 2nd commit message will be skipped:
# delinting
* added writeData command
* better junit reporting
removed chainable .only.
* starting onboarding test
* complete onboarding to quick start
* additional onboarding tests
* adding field requirements test
WIP - updating to new org ctx - stablizing
WIP - linting - stablizing
fixing merge conflicts
* refactor onboarding test to leverage data-testid
fixing jstests with new data-testid attribs
refactor add last data-testid replacements onb test
improving assert
* passing in additional data-testid values
troubleshoot tokens test
WIP tokens test - clean up after troubleshoot
WIP - tokens tests
updating testID in tokens test
* re-enable all current tokens tests
* starting labels test
* labels tests
* minor fix
minor fix
* cy.writeData chunked
* resynching onboarding.test.ts
As of golang/go#31960, go1.13 (or tip) will always add the go directive
to go.mod. Add it now as go 1.12 so that we don't have churn later as
people start using 1.13, before we're ready to officially switch to
building influxdb with 1.13.
I don't see anywhere obvious that an engine would be closed twice, but
if it was, the RLock would have been held permanently, such that a Lock
could not be taken later.
Running go test ./storage/... did not trigger a double-close.
The controller implementation is primarily used by influxdb so it
shouldn't be part of the flux repository. This copies the code from flux
to influxdb so it can be removed from the next flux release.
* Add scatter to visualization types dropdown
* Add initial scatter options
* Add scatter visualization to view switcher
* Add scatter to VEO
* Add scatter type to graph types
* Expand scatter options
* Update changelog
* Change scatter color type to strings
* Assume fluxgroupkey is set
* Regularize scatter options
* Place scatter behind feature flag
Now that the run status updates are transactional actions
We no longer have to add a timer to keep things on track.
This is causing a problem where some runs are showing up without a start or stop time if the system is busy.
I would rather have the scheduler hang on the update then leave a run action without required fields.
The copy was unnecessary since it was just going to be copied
immediately afterwards into an Arrow buffer. In the future, we will want
to have storage directly send the arrow buffer, but right now we are
putting it in an array and copying it anyway.
Even when we send an arrow buffer, the underlying sequence of bytes is
probably going to be different and we will rely on the allocator to
reuse bytes so let's remove the extra copy.
karel-rehor
Mark Rushakoff
Jonathan A. Sternberg
kelwang
Jade McGough
Jorge Landivar
Deniz Kusefoglu
Daniel Campbell
Kelvin Wang
Brandon Farmer
Lyon Hill
Alirie Gray
Christopher Henn
Iris Scholten
zhulongcheng