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
Windows RSP Auto-Start: Hardened RSP backend discovery on Windows — filter out processes with a null CommandLine in the WMI query (which previously made the whole PowerShell pipeline fail) and broadened RSP process matching.
Korean Log Corruption (VSCode): Tomcat console log encoding is now aligned with the RSP backend JVM's default charset (MS949 on Korean Windows for JDK ≤ 17), so server logs streamed into VSCode's output view render Korean correctly.
Korean Log Corruption (Launcher UI): Child JVMs (Maven, Spring Boot) on Windows are forced to UTF-8 output via JAVA_TOOL_OPTIONS; isolated CATALINA_BASE copies pin their console handler to UTF-8 to match the launcher's UTF-8 web UI.
Docker Container Recovery: Containers stuck in Created state (e.g. after a failed port bind on docker run) are now removed and recreated instead of endlessly retrying docker start; host-port conflicts (such as a locally installed MySQL service on 3306) fail fast with a clear message before pulling images, and docker start failures include the daemon's error output.
VSCode Extension Detection: Extension status/install now uses the bin\code.cmd CLI shim when the configured VSCode path points at the GUI binary (Code.exe), which silently ignores --list-extensions/--install-extension — previously the launcher kept reporting an already-installed Server Connector extension as missing and could not install it.
RSP Fallback Diagnostics: When the RSP backend is not detected, the file-based fallback now logs why instead of proceeding silently.