From 065cff580dfb5d36400d3a353bf8947a9553875f Mon Sep 17 00:00:00 2001 From: Joshua MacDonald Date: Wed, 18 Dec 2024 14:00:23 -0800 Subject: [PATCH] Lint --- docs/rfcs/consistent-timeout-handling.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/rfcs/consistent-timeout-handling.md b/docs/rfcs/consistent-timeout-handling.md index 06349c7c72a..8c197ce4663 100644 --- a/docs/rfcs/consistent-timeout-handling.md +++ b/docs/rfcs/consistent-timeout-handling.md @@ -121,7 +121,7 @@ calculated retry attempt. ### Batch processor and sender: existing These components are expected to have identical batching behavior, -as discussed in a [companion RFC](). As stated in that proposal, +as discussed in a [companion RFC](https://github.com/open-telemetry/opentelemetry-collector/pull/11947). As stated in that proposal, these components are not deadline-aware. For error transmission and consistent treatment of timeout, a batching process should wait for the request to complete, until context cancellation, or until the