Seen earlier today while looking through extension+sidecar output channel logs, after the extension had been left running overnight. First logs appeared with a timestamp of 2024-11-11 12:21:27,779 ~8hr20min before the last logs in the output channel with a timestamp of 2024-11-11 20:39:41,300:
But tailing the log file directly shows the most recent log lines (bottom half of the screenshot).
Seen earlier today while looking through extension+sidecar output channel logs, after the extension had been left running overnight. First logs appeared with a timestamp of
2024-11-11 12:21:27,779~8hr20min before the last logs in the output channel with a timestamp of2024-11-11 20:39:41,300:But tailing the log file directly shows the most recent log lines (bottom half of the screenshot).
Upon opening the sidecar log file (
$TMPDIR/vscode-confluent-sidecar.log), it appears to have rotated/reset, as the earliest timestamp now shows2024-11-12 07:24:40,786. We likely need to update the manager'sstartTailingSidecarLogs()method to restart in this scenario and reset its.logTailer: https://github.com/confluentinc/vscode/blob/256616ec184cb73dcb4634ae5f5a765b4a8266b0/src/sidecar/sidecarManager.ts#L98-L100