-
Notifications
You must be signed in to change notification settings - Fork 528
Source default batcher settings from sink #10620
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
Conversation
Web viewer built successfully. If applicable, you should also test it:
Note: This comment is updated whenever you push a commit. |
Latest documentation preview deployed successfully.
Note: This comment is updated whenever you push a commit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Neat.
That's both pretty tricky and very sensitive to regressions though, a few tests would be welcome:
- Make sure setting the env does override the per-sink logic and vice-versa
- Make sure updating the sink during logging does update the conf properly etc
b571e5f
to
ab3095e
Compare
@rerun-bot full-check |
Started a full build: https://github.com/rerun-io/rerun/actions/runs/16292479612 |
) ### What We changed the behavior of the batcher in: #10620 However, the only way to override this behavior was to set environment variables, which can be tricky/annoying in some circumstances. This plumbs through the configuration settings so that this can be specified explicitly now. --------- Co-authored-by: Clement Rey <[email protected]>
### Related * Introduced in #10620 ### What Environment variables are annoying
### Related * Introduced in #10620 ### What Environment variables are annoying
Related
What
Makes the default flush tick 200ms for file & memory sinks and leaves it at 8ms for grpc sinks.
To facilitate this, I introduced per sink batcher config defaults and had to make the batcher configuration updatable (since Python always first creates a recording stream with a memory sink and then patches it in later). Unfortunately not all config optionscan be updated after the fact, but I think the solution here is good enough for what is practically needed.