User Request
Type: bug
Target: Console Application
Submitted by: @aashu2006
Console Request ID: 728f6d23-bbd1-4ce5-8b0b-df66c6a7075d
Description
What happened:
In pkg/api/handlers/nightly_e2e.go:409-422, one goroutine is spawned per failed workflow run with no semaphore. Each detectGPUFailure call makes a GitHub API request with no per-goroutine timeout. A burst of failures across 17+ workflows fans out to dozens of concurrent GitHub API requests with no backpressure.
What I expected:
A semaphore (e.g. golang.org/x/sync/semaphore) should limit concurrent detectGPUFailure calls to a reasonable maximum.
Steps to reproduce:
- Have 20+ workflow runs fail simultaneously
- Observe 20+ concurrent GitHub API requests fired with no backpressure
This issue was automatically created from the KubeStellar Console.
User Request
Type: bug
Target: Console Application
Submitted by: @aashu2006
Console Request ID: 728f6d23-bbd1-4ce5-8b0b-df66c6a7075d
Description
What happened:
In
pkg/api/handlers/nightly_e2e.go:409-422, one goroutine is spawned per failed workflow run with no semaphore. EachdetectGPUFailurecall makes a GitHub API request with no per-goroutine timeout. A burst of failures across 17+ workflows fans out to dozens of concurrent GitHub API requests with no backpressure.What I expected:
A semaphore (e.g.
golang.org/x/sync/semaphore) should limit concurrentdetectGPUFailurecalls to a reasonable maximum.Steps to reproduce:
This issue was automatically created from the KubeStellar Console.