container real-time log shows incomplete

[junotx]

Describe the bug

container real-time log shows no tail log：
view container log and that is normal

but switch to real-time log and can not see the tail log

Versions used(KubeSphere/Kubernetes)

KubeSphere(3.0.0)

Environment

single cluster & allinone

/kind bug

[JohnNiang]

• Correct log format
  

• Log in container log window
  

[JohnNiang]

/priority high

[JohnNiang]

And many redundant and unexpected blank lines may be included into the log content.

[JohnNiang]

/cc @kubesphere/sig-console

[JohnNiang]

/area console

[JohnNiang]

/remove-priority high
/priority medium

[harrisonliu5]

/kind need-to-verify

[jioce]

issue still exists

version used:
kubesphere: v3.2.0

[liuyp2018]

/remove-kind need-to-verify

[harrisonliu5]

/assign @weili520

[JohnNiang]

/unassign @zryfish

[weili520]

I think it is caused by the node.js HTTP receive mechanism. When the HTTP response is chunked, the data didn't lose, it will show with the next response, but the response interval is about 2 minutes.

[JohnNiang]

I think it is caused by the node.js HTTP receive mechanism. When the HTTP response is chunked, the data didn't lose, it will show with the next response, but the response interval is about 2 minutes.

Hi @weili520 , if you don't have a better solution now, you could refer to an existing implementation: https://github.com/tektoncd/dashboard/tree/main/packages/components/src/components/Log

[weili520]

@harrisonliu5 I think we should upgrade the node-fetch to v3.x, this problem is caused by that the fetch response.body is not a nodejs readable stream. It is ESM, the resolution is here Add example for loading ESM from CommonJS.

[weili520]

I have tried it, it works well.

The pods log-generator is created by using the command: kubectl apply -f https://raw.githubusercontent.com/wenchajun/fluentbit-operator/notification/docs/user-guides/forwarding-logs-via-http/kubesphere/log-generator.yaml

it will generate a log every five seconds.

2022-01-05.15.47.25.mov

[weili520]

@harrisonliu5 I think we should upgrade the node-fetch to v3.x, this problem is caused by that the fetch response. body is not a nodejs readable stream. It is ESM, the resolution is here Add example for loading ESM from CommonJS.

This problem will disappear if the user updates the KubeSphere version to v3.2.1.

[jioce]

issue is fixed

version used
kubesphere: v3.3.0-rc.1