Skip to content

Commit 7acb3c8

Browse files
authored
Clear encoding_buffer rather than resize to avoid leading 0's in encoded message (#176)
1 parent d43249a commit 7acb3c8

File tree

1 file changed

+2
-4
lines changed
  • opentelemetry-etw-metrics/src/exporter

1 file changed

+2
-4
lines changed

opentelemetry-etw-metrics/src/exporter/mod.rs

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -49,10 +49,8 @@ fn emit_export_metric_service_request(
4949
if (export_metric_service_request.encoded_len()) > etw::MAX_EVENT_SIZE {
5050
otel_warn!(name: "MetricExportFailedDueToMaxSizeLimit", size = export_metric_service_request.encoded_len(), max_size = etw::MAX_EVENT_SIZE);
5151
} else {
52-
encoding_buffer.resize_with(
53-
export_metric_service_request.encoded_len(),
54-
Default::default,
55-
);
52+
// `encoding_buffer` is assumed to be reused, so ensure it is empty before using it for encoding
53+
encoding_buffer.clear();
5654

5755
export_metric_service_request
5856
.encode(encoding_buffer)

0 commit comments

Comments
 (0)