From fbec281553b1983cb14d61cee05ed8c0efe80fbd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Rafael=20Mu=C3=B1oz?= Date: Thu, 16 Mar 2023 12:38:13 +0100 Subject: [PATCH] Fix typo (#1721) --- .../src/opentelemetry/instrumentation/boto3sqs/__init__.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/instrumentation/opentelemetry-instrumentation-boto3sqs/src/opentelemetry/instrumentation/boto3sqs/__init__.py b/instrumentation/opentelemetry-instrumentation-boto3sqs/src/opentelemetry/instrumentation/boto3sqs/__init__.py index 9f4ede9c3..c34be8218 100644 --- a/instrumentation/opentelemetry-instrumentation-boto3sqs/src/opentelemetry/instrumentation/boto3sqs/__init__.py +++ b/instrumentation/opentelemetry-instrumentation-boto3sqs/src/opentelemetry/instrumentation/boto3sqs/__init__.py @@ -101,7 +101,7 @@ class Boto3SQSInstrumentor(BaseInstrumentor): class ContextableList(list): """ Since the classic way to process SQS messages is using a `for` loop, without a well defined scope like a - callback - we are doing something similar to the instrumentaiton of Kafka-python and instrumenting the + callback - we are doing something similar to the instrumentation of Kafka-python and instrumenting the `__iter__` functions and the `__getitem__` functions to set the span context of the addressed message. Since the return value from an `SQS.ReceiveMessage` returns a builtin list, we cannot wrap it and change all of the calls for `list.__iter__` and `list.__getitem__` - therefore we use ContextableList. It is bound to the