You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Steps to reproduce:
List the minimal actions needed to reproduce the behavior.
Generate a few tokens in the LoadData > Tokens page
Disable some of the tokens
Sort by description - appears to work fine
Sort by Status (assuming status implies enabled || disabled )
The sort order does not seem to apply to the enabled || disabled state.
Expected behavior:
As the disabled/enabled toggle is aligned over a column under the status header, expected that all disabled tokens would be sorted to the top of the list, all enabled to the bottom and on a further sort click the reverse would happen.
Actual behavior:
There seems to be no order based on enabled/disabled state. See screencast.
Screencast
Environment info:
System info: Run uname -srm and copy the output here
Linux 4.4.0-164-generic x86_64
InfluxDB version: Run influxd version and copy the output here
This was discovered in a nightly build docker image. From the docker log:
ts=2019-09-30T07:53:42.727140Z lvl=info msg="Welcome to InfluxDB" log_id=0ICIQIHl000 version=nightly commit=7d4c8491f build_date=2019-09-30T07:15:02Z
Other relevant environment details: Container runtime, disk info, etc Browser: Chrome 76.
Config:
Copy any non-default config values here or attach the full config as a gist or file.
Started with e2e testing enabled:
--e2e-testing=true
Logs:
Nothing in console.log
The text was updated successfully, but these errors were encountered:
Steps to reproduce:
List the minimal actions needed to reproduce the behavior.
The sort order does not seem to apply to the enabled || disabled state.
Expected behavior:
As the disabled/enabled toggle is aligned over a column under the status header, expected that all disabled tokens would be sorted to the top of the list, all enabled to the bottom and on a further sort click the reverse would happen.
Actual behavior:
There seems to be no order based on enabled/disabled state. See screencast.
Screencast
Environment info:
uname -srm
and copy the output hereinfluxd version
and copy the output hereThis was discovered in a nightly build docker image. From the docker log:
Browser: Chrome 76.
Config:
Copy any non-default config values here or attach the full config as a gist or file.
Started with e2e testing enabled:
Logs:
Nothing in console.log
The text was updated successfully, but these errors were encountered: