Closed
Description
The prebuild log page appears to have an infinite loop when there is a system error.
I reproduced this in a preview environment with incorrectly configured minio.
Navigating to the prebuild log page will trigger the loop and the dev console will show repeated messages like below:
The websocket will show continuously repeated requests hitting our server.
12:20:16.282 re-trying headless-logs because: error while listening to stream Error: Headless logs for 958474e9-cc7c-4364-8025-e549f3675d26 not found
Babel 3
n messages.js:36
o main.js:449
o main.js:276
o main.js:260
f setImmediate.js:40
f setImmediate.js:69
n setImmediate.js:109
[PrebuildLogs.tsx:121:20](https://alex-self-b68dfaed52.preview.gitpod-dev.com/static/js/components/PrebuildLogs.tsx)
12:20:17.530 re-trying headless-logs because: error while listening to stream Error: Headless logs for 958474e9-cc7c-4364-8025-e549f3675d26 not found
Babel 3
n messages.js:36
o main.js:449
o main.js:276
o main.js:260
f setImmediate.js:40
f setImmediate.js:69
n setImmediate.js:109
PrebuildLogs.tsx:121:20
12:20:18.777 re-trying headless-logs because: error while listening to stream Error: Headless logs for 958474e9-cc7c-4364-8025-e549f3675d26 not found
Babel 3
n messages.js:36
o main.js:449
o main.js:276
o main.js:260
f setImmediate.js:40
f setImmediate.js:69
n setImmediate.js:109
The original cause of the error in my case was:
re-trying headless-logs because: error while listening to stream Error: Request getHeadlessLog failed with message: 2 UNKNOWN: cannot list objects: Get "http://minio.default.svc.cluster.local:9000/gitpod-user-16c59a60-91be-4434-8ac0-daadf62f5d3c/?location=": dial tcp 10.43.21.48:9000: connect: connection refused
Metadata
Metadata
Assignees
Type
Projects
Status
No status