From a0b70bf3e31e396ad704443b63e43a6d07628d85 Mon Sep 17 00:00:00 2001
From: Stef Pletinck <stef.pletinck@ugent.be>
Date: Thu, 10 Apr 2025 14:33:34 +0200
Subject: [PATCH] Fix ObeliskError message spelling

When Producer.send throws an ObeliskError,
it would set the field `messasge` instead of `message` on said error.
Woops.
---
 src/obelisk/asynchronous/producer.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/obelisk/asynchronous/producer.py b/src/obelisk/asynchronous/producer.py
index b3f5b19..b0ad4f9 100644
--- a/src/obelisk/asynchronous/producer.py
+++ b/src/obelisk/asynchronous/producer.py
@@ -48,7 +48,7 @@ async def send(self, dataset: str, data: List[dict],
         response = await self.http_post(f'{self._ingest_url}/{dataset}', data=data,
                                         params=params)
         if response.status_code != 204:
-            msg = f'An error occured during data ingest. Status {response.status_code}, messasge: {response.text}'
+            msg = f'An error occured during data ingest. Status {response.status_code}, message: {response.text}'
             self.log.warning(msg)
             raise ObeliskError(msg)
         return response