Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

LAD views should respond to conductor bounds changes #2929

Closed
akhenry opened this issue Apr 13, 2020 · 6 comments
Closed

LAD views should respond to conductor bounds changes #2929

akhenry opened this issue Apr 13, 2020 · 6 comments
Assignees
@jvigliotta
Labels
type:bug
Projects
Bug Tracker

Comments

@akhenry
Copy link
Contributor

akhenry commented Apr 13, 2020

Similar to #2712, LAD Tables and display layout telemetry views should observe conductor bounds. This means re-requesting LAD historical data when conductor bounds or time system change, and inspecting the timestamp of incoming subscription telemetry to ensure values fall within the start and end bounds.

Until we support multiple timeframes concurrently, it is important that all of the telemetry values on screen observe the configured time conductor bounds.
@jvigliotta jvigliotta mentioned this issue Apr 16, 2020
Merged
@akhenry
Copy link
Contributor Author

akhenry commented Jun 22, 2020

Closed by #2946

@akhenry akhenry closed this as completed Jun 22, 2020
@jvigliotta
Copy link
Contributor

Founds some bugs that need to be addressed, reopening.

@jvigliotta jvigliotta reopened this Jun 22, 2020
@jvigliotta jvigliotta mentioned this issue Jun 24, 2020
Closed
@jvigliotta
Copy link
Contributor

closed this issue, does not need to be tested in 06/04/2021 2 testathon

@akhenry akhenry added this to Needs triage in Bug Tracker via automation Jun 4, 2021
@akhenry akhenry moved this from Needs triage to Current Sprint in Bug Tracker Jun 4, 2021
@shefalijoshi
Copy link
Contributor

Verified fixed.

@charlesh88
Copy link
Contributor

Verified fixed Testathon 6/4/2021

@nikhilmandlik
Copy link
Contributor

Verified Fixed.

@unlikelyzero unlikelyzero moved this from Current Sprint to Closed in Bug Tracker Jun 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jvigliotta jvigliotta

Labels
type:bug
Projects
Bug Tracker
Done
Milestone
No milestone
Development

No branches or pull requests
6 participants
@charlesh88 @nikhilmandlik @akhenry @shefalijoshi @jvigliotta @unlikelyzero