Adding the same claim (same claimName and gpu name) will increment usage but not actually allocate it multiple times
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 3
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Adding the same claim (same claimName and gpu name) is filtered in the k8s updating logic, but not when persisting it to the deployment in the db, causing usage to go up but not actually use more resources.
Fix: filter out duplicates before persising to db.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace the Go deployment persistence path and compare it with the Kubernetes updating logic, where duplicate claims are already filtered. Reproduce or test two claims with the same claimName and GPU name, then verify that the persisted deployment contains one claim and usage is incremented only once.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, database
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100