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

Introduce new API to send a dataframe to Rerun #8461

Merged
merged 8 commits into from
Dec 16, 2024
Merged

Conversation

jleibs
Copy link
Member

@jleibs jleibs commented Dec 13, 2024

What

This is not perfect, since Sorbet hasn't been formalized.

This decodes the place-holder sorbet data we currently use in our query results, as well as some of the Rerun-chunk metadata.

Eventually we should move this onto the rust-side of things, but as this is largely just metadata processing, doing it in python is not terrible.

@jleibs jleibs added the 🐍 Python API Python logging API label Dec 13, 2024
@jleibs jleibs marked this pull request as ready for review December 13, 2024 19:30
@jleibs jleibs requested a review from teh-cmc December 13, 2024 19:31
Copy link

github-actions bot commented Dec 13, 2024

Web viewer built successfully. If applicable, you should also test it:

  • I have tested the web viewer
Result Commit Link Manifest
53da877 https://rerun.io/viewer/pr/8461 +nightly +main

Note: This comment is updated whenever you push a commit.

Copy link
Member

@teh-cmc teh-cmc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At least one basic test would be nice, I can see this silently starting to fail in a few weeks...

Comment on lines 124 to 125
Self::Time => write!(f, "Time"),
Self::Sequence => write!(f, "Sequence"),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we really want to introduce casing issues here? Or is all sorbet metadata case-insensitive (but then what about our case-sensitive entity paths...?).

Also I wish we could just get rid of this whole notion of time vs. sequence somehow (e.g. make it a display setting in the viewer, not a property of the timeline itself):

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Our typing is already all over the map: semantic_type / semantic_family are already cased, as they are derived from Component/Archetype names. This seemed symmetric with that policy.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also realizing this doesn't need to be here at all. Dropping the change so we don't need to worry about it.

@jleibs jleibs merged commit 8466c45 into main Dec 16, 2024
32 checks passed
@jleibs jleibs deleted the jleibs/send_dataframe branch December 16, 2024 17:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants