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

Fix error when logging segmentation image #6449

Merged
merged 7 commits into from
May 29, 2024

Conversation

Wumpf
Copy link
Member

@Wumpf Wumpf commented May 28, 2024

What

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.

@Wumpf Wumpf added 🪳 bug Something isn't working include in changelog labels May 28, 2024
@Wumpf Wumpf added this to the 0.16.1 milestone May 28, 2024
@@ -560,12 +560,14 @@ impl ImageVisualizer {
let tensor_stats = ctx
.cache
.entry(|c: &mut TensorStatsCache| c.entry(tensor_data_row_id, tensor));
let depth_texture = re_viewer_context::gpu_bridge::depth_tensor_to_gpu(
let depth_texture = re_viewer_context::gpu_bridge::tensor_to_gpu(
Copy link
Member Author

Choose a reason for hiding this comment

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

not exposing the inner methods of tensor_to_gpu is nice from a crate isolation perspective & doesn't cause any overhead here :). This callsite was the only one that needed adjustment

@Wumpf Wumpf force-pushed the andreas/annotation-context-log-issue branch from 597d961 to ca2338b Compare May 28, 2024 15:03
Copy link
Member

@abey79 abey79 left a comment

Choose a reason for hiding this comment

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

I didn't get all the subtleties of the original issue, but tested with Jeremy's repro and code lgtm

@Wumpf Wumpf merged commit 9adb3e4 into main May 29, 2024
33 of 34 checks passed
@Wumpf Wumpf deleted the andreas/annotation-context-log-issue branch May 29, 2024 10:03
abey79 pushed a commit that referenced this pull request May 29, 2024
* Fixes #6443
* the problem was that we use row ids for hashing texture manager
entries. Instead, we need to use a combination of texture meaning + row
id, because the same row may give rise to several textures!
* Fixes this also for any other combination of textures on the same row
(e.g. depth + regular)
* Fixes bad error message display

* [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/6449?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/6449?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/6449)
- [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`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🪳 bug Something isn't working include in changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unexpected error when logging Segmentation Image and Annotation Context together
3 participants