[Time Conductor] Pan/Zoom causes duplicate bounds events

[jvigliotta]

Summary

Pan/Zoom on conductor causes two bounds events to be emitted, resulting in double requests for views listening to those events.

This is due to zoom/pan being calculated based off of width of selection, which can result in decimal timestamps. The solution would be to normalize those measurements before setting the bounds with them.

Expected vs Current Behavior

One request should be made when panning or zooming on the conductor.

Impact Check List

• Data loss or misrepresented data?
• Regression? Did this used to work or has it always been broken?
• Is there a workaround available?
• Does this impact a critical component?
• Is this just a visual bug?

Steps to Reproduce

1. View telemetry with network tab open
2. If you zoom or pan on the conductor time axis two duplicate requests are being made

Testing

This should only be one reqeust.

[khalidadil]

Verified Fixed in Testathon on 10/08/2021