You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Calling string() on environment variables with empty values fails on Windows #554
When I have environment variables with no values (somehow I have two on my system - COMPLUS_InstallRoot and COMPLUS_Version), when I iterate over values of boost::process::environment::current() and try to call string() on the empty value, it fails.
boost::unordered_map<std::string, std::string> currentProcessEnvironment;
for (const auto& env : boost::process::environment::current())
{
currentProcessEnvironment[env.key().string()] = env.value().string(); // fails if env.value().empty()
}
Fix for this should be simple, all needed should be just to apply this for size_as_utf8 and convert_to_utf8: f372a9a
I'll merge it after the current release is complete.
@klemens-morgenstern: Any update on this? Boost 1.92.0 has been released approx. a month ago, so now the pull request fixing this issue (#560) could be reviewed.
Activity
klemens-morgenstern commentedon May 1, 2026
Do you want to create a PR?
aliquis162 commentedon May 6, 2026
I am too busy with other things. I can create PR later but I don't know when.
striezel commentedon Jul 12, 2026
@aliquis162 + @klemens-morgenstern
I created a PR for this: #560
klemens-morgenstern commentedon Jul 12, 2026
Ok, I'll merge it after the current release is complete.
fix(ipc):子进程环境构造逐项隔离空值与不可转换条目
striezel commentedon Sep 7, 2026
@klemens-morgenstern: Any update on this? Boost 1.92.0 has been released approx. a month ago, so now the pull request fixing this issue (#560) could be reviewed.
guard WideCharToMultiByte() against empty strings