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

Logging data with the same time point leads to unactionable log messages #5586

Open
jleibs opened this issue Mar 20, 2024 · 0 comments
Open
Labels
😤 annoying Something in the UI / SDK is annoying to use ⛃ re_datastore affects the datastore itself

Comments

@jleibs
Copy link
Member

jleibs commented Mar 20, 2024

However, this warning shows up as a somewhat spammy pop-message in the viewer such as:

[2024-03-19T22:07:45Z WARN re_data_store::store_write] Found over 512 rows with the same timepoint "frame_index"=#0 - perhaps you forgot to update or remove the timeline?

[2024-03-19T22:07:45Z WARN re_data_store::store_write] Found over 512 rows with the same timepoint "seconds"=+0s - perhaps you forgot to update or remove the timeline?

The content of the message itself is also somewhat cryptic -- it doesn't mention which entity is the problem, why this is a problem in the first place, or a concrete next step for the user to take.

@jleibs jleibs added ⛃ re_datastore affects the datastore itself 😤 annoying Something in the UI / SDK is annoying to use labels Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
😤 annoying Something in the UI / SDK is annoying to use ⛃ re_datastore affects the datastore itself
Projects
None yet
Development

No branches or pull requests

1 participant