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 a snippet for Spatial3DView and fix issues related to _RERUN_TEST_FORCE_SAVE #6120

Merged
merged 4 commits into from Apr 26, 2024

Conversation

jleibs
Copy link
Member

@jleibs jleibs commented Apr 25, 2024

What

  • Introduce a new snippet that also sends a blueprint

It turned out that _RERUN_TEST_FORCE_SAVE is totally broken when using blueprints since the blueprint stream stomps on the recording.

  • Make it so _RERUN_TEST_FORCE_SAVE works with blueprints
  • Remove redundant store_kind since this led to bugs opting out blueprint memory recordings from the force-save path.

Checklist

  • I have read and agree to Contributor Guide and the Code of Conduct
  • I've included a screenshot or gif (if applicable)
  • I have tested the web demo (if applicable):
  • The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
  • If applicable, add a new check to the release checklist!

To run all checks from main, comment on the PR with @rerun-bot full-check.

@jleibs jleibs added 🟦 blueprint The data that defines our UI 📖 documentation Improvements or additions to documentation exclude from changelog PRs with this won't show up in CHANGELOG.md labels Apr 25, 2024
@jleibs jleibs marked this pull request as ready for review April 25, 2024 18:27
@jleibs jleibs changed the title Introduce a snipper for Spatial3DView and fix issues related to compare_snippet_output.py Introduce a snippet for Spatial3DView and fix issues related to compare_snippet_output.py Apr 25, 2024
@@ -13,6 +13,7 @@ log_line = [ # Not a complete example -- just a single log line
"rust",
"py",
]
spatial3dview = ["cpp", "rust"] # Missing examples
Copy link
Member

@emilk emilk Apr 26, 2024

Choose a reason for hiding this comment

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

think we should put all space view snippets into their own folder. That way we can easily add checks like "Make sure all spaceviews has a snippet". As is, we can't even do that as an eye-ball check (i.e. answer the question "which space views have we added snippets for?")

Copy link
Member Author

Choose a reason for hiding this comment

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

@jleibs jleibs changed the title Introduce a snippet for Spatial3DView and fix issues related to compare_snippet_output.py Introduce a snippet for Spatial3DView and fix issues related to _RERUN_TEST_FORCE_SAVE Apr 26, 2024
@jleibs jleibs merged commit 8ede58b into main Apr 26, 2024
38 of 42 checks passed
@jleibs jleibs deleted the jleibs/blueprint_snippets branch April 26, 2024 13:44
jleibs added a commit that referenced this pull request Apr 26, 2024
### What
- Builds on top of: #6120
  - Rebase after merging and then remove `do-no-merge` label.

Add blueprint views to the python docs index.

Create a reference page for each view with documentation of its view
properties and an example when provided.

Generating pages for all the blueprint archetypes and cross-linking
still felt a bit overwhelming. Since these properties are almost always
only used in the context of the view, I decided to inline instead.

### Checklist
* [x] I have read and agree to [Contributor
Guide](https://github.com/rerun-io/rerun/blob/main/CONTRIBUTING.md) and
the [Code of
Conduct](https://github.com/rerun-io/rerun/blob/main/CODE_OF_CONDUCT.md)
* [x] I've included a screenshot or gif (if applicable)
* [x] I have tested the web demo (if applicable):
* Using examples from latest `main` build:
[rerun.io/viewer](https://rerun.io/viewer/pr/6121?manifest_url=https://app.rerun.io/version/main/examples_manifest.json)
* Using full set of examples from `nightly` build:
[rerun.io/viewer](https://rerun.io/viewer/pr/6121?manifest_url=https://app.rerun.io/version/nightly/examples_manifest.json)
* [x] The PR title and labels are set such as to maximize their
usefulness for the next release's CHANGELOG
* [x] If applicable, add a new check to the [release
checklist](https://github.com/rerun-io/rerun/blob/main/tests/python/release_checklist)!

- [PR Build Summary](https://build.rerun.io/pr/6121)
- [Recent benchmark results](https://build.rerun.io/graphs/crates.html)
- [Wasm size tracking](https://build.rerun.io/graphs/sizes.html)

To run all checks from `main`, comment on the PR with `@rerun-bot
full-check`.
@emilk emilk mentioned this pull request Apr 27, 2024
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🟦 blueprint The data that defines our UI 📖 documentation Improvements or additions to documentation exclude from changelog PRs with this won't show up in CHANGELOG.md
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants