User Request
Type: bug
Target: Console Application
Submitted by: @aashu2006
Console Request ID: 40401ff1-e896-40ad-a86a-6a096403cf0e
Description
What happened:
In pkg/api/handlers/nightly_e2e.go:358-362 and 775, GitHub error response bodies are read with io.ReadAll and no LimitReader. A GitHub outage returning a large HTML error page or any upstream response manipulation can consume unbounded memory.
What I expected:
All io.ReadAll calls on external response bodies should use io.LimitReader with a defined maximum size constant.
Steps to reproduce:
- Simulate a GitHub outage returning a large HTML error page
- Trigger a nightly E2E endpoint
- Observe the full error page is buffered in memory with no size limit
This issue was automatically created from the KubeStellar Console.
User Request
Type: bug
Target: Console Application
Submitted by: @aashu2006
Console Request ID: 40401ff1-e896-40ad-a86a-6a096403cf0e
Description
What happened:
In
pkg/api/handlers/nightly_e2e.go:358-362and775, GitHub error response bodies are read withio.ReadAlland noLimitReader. A GitHub outage returning a large HTML error page or any upstream response manipulation can consume unbounded memory.What I expected:
All
io.ReadAllcalls on external response bodies should useio.LimitReaderwith a defined maximum size constant.Steps to reproduce:
This issue was automatically created from the KubeStellar Console.