Closed jprochazk closed 2 weeks ago
Tested by installing rerun-notebook
, then updating crate versions to 0.21.0-alpha.1
and installing rerun-sdk
:
I tried using the warnings
module for this, but I don't really understand how it works. I had to set a filter to actually see the warning, which seems bad? Should this just be a print
instead?
What
Side note: Should this close the above issue? We said we'd prefer to express version requirements in the context of pip instead of a warning
Checklist
[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested the web demo (if applicable):
main
build: rerun.io/viewernightly
build: rerun.io/viewer[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!
[x] If have noted any breaking changes to the log API in
CHANGELOG.md
and the migration guidePR Build Summary
Recent benchmark results
Wasm size tracking
To run all checks from
main
, comment on the PR with@rerun-bot full-check
.