Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is mainly to start a discussion with the Arduino CLI team about whether handler-level buffering is the right approach. I do not really know these things, but I would like to use them downstream. Thank you!
What
CONFIGURE keys (defaults)
_buffer.hwm
n>=1 (1) – size trigger_buffer.interval_ms
ms>=0 (0) – time trigger (0 = disabled)_buffer.line
true|false|on|off|0|1 (false) – flush on \n_buffer.queue
n>=1 (32) – queued payloads between aggregator and TCP writer_buffer.overflow
<drop|wait> (drop) – on full queue_buffer.overflow_wait_ms
ms>=0 (0) – wait budget when overflow=waitRef: #33
Arduino CLI: arduino/arduino-cli#2975