Remote Node project app logs broken

[tetchel]

I have seen this problem with new Node projects on my minikube cluster as well as my OCP one. The app logs contain the last 10 lines of package.json and nothing else. Sometimes, it has those 10 lines multiple times.

I can't get the logs to show anything else. The build logs seem OK.

Here's the content of the log-update event:

{
    logName:"app.log"
    logPath:"/codewind-workspace/.logs/nodemk-0de98700-889e-11ea-a602-53da96b7af34"
    logs:"    "express-pino-logger": "^4.0.0",
        "pino": "^5.16.0"
    },
    "devDependencies": {},
    "nodemonConfig": {
        "env": {
        "NODE_HEAPDUMP_OPTIONS": "nosignal"
        }
    }
    }
        "express-pino-logger": "^4.0.0",
        "pino": "^5.16.0"
    },
    "devDependencies": {},
    "nodemonConfig": {
        "env": {
        "NODE_HEAPDUMP_OPTIONS": "nosignal"
        }
    }
    }
        "express-pino-logger": "^4.0.0",
        "pino": "^5.16.0"
    },
    "devDependencies": {},
    "nodemonConfig": {
        "env": {
        "NODE_HEAPDUMP_OPTIONS": "nosignal"
        }
    }
    }
    "
}

The contents of that file within PFE do match the logs in that object.

Tagging both backend areas because i'm not sure which one to start with.

[sujeilyfonseca]

Codewind version: Latest
OS: Mac OS Mojave 10.14.6 (w. OCP 4.3), VM with Windows 10 (w. OCP 3.11)

IDE extension version: 0.12.0
IDE version: Code 1.44.0

I encountered the same problem on Friday. The app.log only presented a few lines from the package.json when creating new Node JS projects in remote scenarios. I didn't see that when creating Node JS projects in local scenarios.

[root@codewind-pfe-k9ehncev-685467f4f7-bbjrx cw-remote-node-express-3efecf90-88bb-11ea-97b2-713b959fb2cd]# cat app.log
    "express-pino-logger": "^4.0.0",
    "pino": "^5.16.0"
  },
  "devDependencies": {},
  "nodemonConfig": {
    "env": {
      "NODE_HEAPDUMP_OPTIONS": "nosignal"
    }
  }
}

[stalleyj]

This problem is a result of the changes made for #1990. Investigating a solution

[jopit]

Two solutions

1. Allow Kube to restart the pod
2. Tail the same file we do in the local case.

Investigate doing 2 for 0.12, and 1 for 0.13

[rwalle61]

#2812 implements solution 1 for 0.12