id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
10246	"asynchronous_sink sometimes ""misses"" an attribute"	bielecki.b@…	Andrey Semashev	"Using following
{{{
boost::log::sinks::asynchronous_sink<
    boost::log::sinks::text_ostream_backend
>

boost::log::sources::severity_channel_logger_mt<Level, Group> scl;
}}}

with helper keywords (Level and Group and enums)
{{{
namespace {
    BOOST_LOG_ATTRIBUTE_KEYWORD(level, ""Severity"", Level)
    BOOST_LOG_ATTRIBUTE_KEYWORD(group, ""Channel"", Group)
}
}}}

configured to use following format
{{{
void formatter(
    blog::record_view const& record,
    blog::formatting_ostream& stream
) {
    stream << ""["" << record[level] << ""]"";
    stream << ""["" << record[group] << ""]"";
    stream << "" "" << record[expr::smessage];
}
}}}

In the std::cout and/or in file output one of the attributes (I only noticed this happens for level) is (sometimes) missing, even though that they are always passed. Example:

{{{
BOOST_LOG_CHANNEL_SEV(scl, Group::General, Level::Error) << ""Foo"";
}}}

Possible outputs:[[BR]]
[Error][General] Foo[[BR]]
[][General] Foo

This doesn't happen in case of synchronous sink.

Visual Studio 2013"	Bugs	closed	To Be Determined	log	Boost 1.55.0	Problem	invalid