[berkleblebiciii]

Description

On Linux, the server console permanently stops executing commands after a plugin or component puts stdin (fd 0) into non-blocking mode - for example a component embedding node.js, where node:process / libuv switches stdin to non-blocking. The console still echoes keystrokes, but no command is ever executed and not even Unknown command or variable: is printed. Windows is unaffected.

Root cause

The console reader thread does:

while (true)
{
    if (std::getline(std::wcin, line) && threadData->valid)
    {
        ...dispatch command...
    }
    else
    {
        threadData->isRunning = false;
        return;   // <- reader thread dies forever
    }
}

With fd 0 in non-blocking mode the underlying read() fails with EAGAIN, std::getline sets failbit, and the thread treats it as EOF and exits permanently. The stream stays in the failed state, so nothing is ever read again.

Fix

On the failure path, when the thread is still valid, check fd 0's status flags: if O_NONBLOCK is set, restore blocking mode, clear() the stream state and retry. Real EOF (stdin closed while blocking) still ends the thread exactly as before, so shutdown behaviour is unchanged.

Tested with a node.js-embedding component running:

import process from "node:process";
process.stdin.on('data', (chunk) => { console.log(`Received data: ${chunk}`); });

Before: first console input printed Unknown command or variable: foo, after that the console never responded again. After the fix the console keeps working.

Fixes #1268

[NexiusTailer]

How its different to this one? In which ways it's better than the already suggested method?