From b51afbdfb975b676cb885fc4f3559944f99df030 Mon Sep 17 00:00:00 2001
From: Shauren <shauren.trinity@gmail.com>
Date: Fri, 25 Aug 2023 10:40:47 +0200
Subject: Core/Logging: Fixed log message order not being preserved when async
 logging was enabled and ThreadPool was greater than 1

Despite that issue, logging was still threadsafe, just not ordered properly
---
 src/common/Logging/Log.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'src/common/Logging/Log.cpp')

diff --git a/src/common/Logging/Log.cpp b/src/common/Logging/Log.cpp
index c61ebb2bf85..75ea4fae380 100644
--- a/src/common/Logging/Log.cpp
+++ b/src/common/Logging/Log.cpp
@@ -238,7 +238,7 @@ void Log::write(std::unique_ptr<LogMessage> msg) const
     if (_ioContext)
     {
         std::shared_ptr<LogOperation> logOperation = std::make_shared<LogOperation>(logger, std::move(msg));
-        Trinity::Asio::post(*_ioContext, Trinity::Asio::bind_executor(*_strand, [logOperation]() { logOperation->call(); }));
+        Trinity::Asio::post(*_strand, [logOperation]() { logOperation->call(); });
     }
     else
         logger->write(msg.get());
-- 
cgit v1.2.3