Small Compiler fix

[harryeetsource]

Bluespawn.cpp changes:
catch(const std::exception& e) {
Bluespawn::io.InformUser(StringToWidestring(options.help()));
LOG_ERROR(e.what());
Eventlog.cpp changes:
// Open the channel config
EventWrapper hChannel{ EvtOpenChannelConfig(NULL, channel.c_str(), 0) };
if(reinterpret_cast(NULL) == hChannel) {
LOG_ERROR(L"EventLogs::IsChannelOpen: EvtOpenChannelConfig failed with " + std::to_wstring(GetLastError()) +
L" for channel " + channel);
return false;
}

[Jack-McDowell]

I can't approve this for a couple of reasons.

1. Looks like you somehow messed up the submodules - their files are being considered part of BLUESPAWN, which shouldn't be the case. Make sure they're still submodules and not just repos dumped in bluespawn's source directories.
2. I'm seeing a lot of source files being recorded as completely changed when they're not really being touched. That screws up git history. I'm guessing you swapped tabs for spaces or something.
3. Changes like this should go into develop, not master. We keep master pointing to the latest version of release code.

If you clean the git stuff up, it should be good (once I confirm with a bit of testing)!

[harryeetsource]

My apologies, ill remove this pull request and properly format it before submitting it again. Thank you

…

On Sat, Jul 29, 2023, 4:43 PM Jack McDowell ***@***.***> wrote: I can't approve this for a couple of reasons. 1. Looks like you somehow messed up the submodules - their files are being considered part of BLUESPAWN, which shouldn't be the case. Make sure they're still submodules and not just repos dumped in bluespawn's source directories. 2. I'm seeing a lot of source files being recorded as completely changed when they're not really being touched. That screws up git history. I'm guessing you swapped tabs for spaces or something. 3. Changes like this should go into develop, not master. We keep master pointing to the latest version of release code. If you clean the git stuff up, it should be good (once I confirm with a bit of testing)! — Reply to this email directly, view it on GitHub <#417 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWZHHQNHK63TVUMU4J6RK63XSWN3NANCNFSM6AAAAAA2G5EBOU> . You are receiving this because you authored the thread.Message ID: ***@***.***>