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.

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

Event Generator does not show data in fixed time mode. #4879

Closed
2 of 5 tasks
akhenry opened this issue Feb 17, 2022 · 3 comments · Fixed by #4883
Closed
2 of 5 tasks

Event Generator does not show data in fixed time mode. #4879

akhenry opened this issue Feb 17, 2022 · 3 comments · Fixed by #4883

Comments

@akhenry
Copy link
Contributor

akhenry commented Feb 17, 2022

Summary

The event generator does not show any events when the conductor is in fixed mode except for events generated in real-time mode.

Expected vs Current Behavior

The example event generator should provide events for any fixed time window configured by the user.

Steps to Reproduce

  1. Switch the time conductor to fixed mode.
  2. Create a new event message generator
  3. Click on the event message generator and observe that no event messages are displayed.
  4. Switch the conductor to real-time mode
  5. Observe that event messages begin appearing.

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 with no functional impact?
@scottbell
Copy link
Contributor

scottbell commented Feb 21, 2022

Testing Instructions:

  • Switch the time conductor to fixed mode.
  • Create a new event message generator
  • Click on the event message generator and observe that event messages are displayed.

(@jvigliotta edit)

  • also test tests (in example folder) to make sure new regex change is working

@shefalijoshi
Copy link
Contributor

Verified fixed (locally)

@akhenry
Copy link
Contributor Author

akhenry commented Apr 4, 2022

Verified fixed.

@unlikelyzero unlikelyzero removed the needs:e2e Needs an e2e test label May 4, 2022
@unlikelyzero unlikelyzero removed this from To triage in Improve Test Coverage May 4, 2022
@shefalijoshi shefalijoshi mentioned this issue May 5, 2022
20 tasks
@unlikelyzero unlikelyzero added this to the Target:2.0.2 milestone Mar 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants