We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We call send_warning, which raises an exception, which we attempt to catch and re-send, which in turn raises a new exception.
Very related to: #3715
The text was updated successfully, but these errors were encountered:
rerun.AnyValues
None
Refactor rerun.AnyValues to handle None` input more gracefully (#3725)
rerun.AnyValues to handle
1a78cb7
### What - Rename `_send_warning` -> `_send_warning_or_raise` to make the behavior clearer. - Default to ignore Nones in AnyValues when the type is unknown. - Update the docstrings. - Expand the unit-tests. Resolves: - #3715 - #3716 ### 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 [demo.rerun.io](https://demo.rerun.io/pr/3725) (if applicable) - [PR Build Summary](https://build.rerun.io/pr/3725) - [Docs preview](https://rerun.io/preview/5540cb4172d7bbef4749daf200ee14672af010e7/docs) <!--DOCS-PREVIEW--> - [Examples preview](https://rerun.io/preview/5540cb4172d7bbef4749daf200ee14672af010e7/examples) <!--EXAMPLES-PREVIEW--> - [Recent benchmark results](https://ref.rerun.io/dev/bench/) - [Wasm size tracking](https://ref.rerun.io/dev/sizes/)
Fixed in #3725
Sorry, something went wrong.
_send_warning
jleibs
No branches or pull requests
We call send_warning, which raises an exception, which we attempt to catch and re-send, which in turn raises a new exception.
Very related to: #3715
The text was updated successfully, but these errors were encountered: