summaryrefslogtreecommitdiff
path: root/include/async_resolve.hpp
diff options
context:
space:
mode:
authorEd Tanous <edtanous@google.com>2022-02-28 21:20:59 +0300
committerEd Tanous <ed@tanous.net>2022-03-07 21:04:33 +0300
commit8cc8edec45fb504457933c2c3f2625fa876493e6 (patch)
tree86f7a8028f8b07dbb42a383828c0b456d4c7f4ee /include/async_resolve.hpp
parent5b9ef70bd343047bb3c1f204b4a2de1030354704 (diff)
downloadbmcweb-8cc8edec45fb504457933c2c3f2625fa876493e6.tar.xz
Don't rely on operator << for object logging
In the upcoming fmt patch, we remove the use of streams, and a number of our logging statements are relying on them. This commit changes them to no longer rely on operator>> or operator+ to build their strings. This alone isn't very useful, but in the context of the next patch makes the automation able to do a complete conversion of all log statements automatically. Tested: enabled logging on local and saw log statements print to console Signed-off-by: Ed Tanous <edtanous@google.com> Change-Id: I0e5dc2cf015c6924037e38d547535eda8175a6a1
Diffstat (limited to 'include/async_resolve.hpp')
-rw-r--r--include/async_resolve.hpp3
1 files changed, 2 insertions, 1 deletions
diff --git a/include/async_resolve.hpp b/include/async_resolve.hpp
index 0945001537..7387f4de29 100644
--- a/include/async_resolve.hpp
+++ b/include/async_resolve.hpp
@@ -89,7 +89,8 @@ class Resolver
return;
}
endpoint.port(portNum);
- BMCWEB_LOG_DEBUG << "resolved endpoint is : " << endpoint;
+ BMCWEB_LOG_DEBUG << "resolved endpoint is : "
+ << endpoint.address().to_string();
endpointList.push_back(endpoint);
}
// All the resolved data is filled in the endpointList