failed to reset memory.peak
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.6k
- Forks
- 438
- PR merge metrics
- No merged PRs in 30d
Description
a lot of
failed to reset memory.peak, interval peak semantics degraded {"service": "orchestrator_template-manager", "internal": true, "pid": 3692383, "trace_id": "f0a5169be0edd839c5775c51193195fb", "span_id": "977ce3dd66bdafb2", "error": "write /sys/fs/cgroup/e2b/sbx-il8ne0g3geuvdtzy7qdsr-8mnmtty6e3guyqvsfjwq/memory.peak: invalid argument"}
Contributor guide
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
The report identifies a failed write to /sys/fs/cgroup/.../memory.peak while resetting interval peak semantics. Start by locating the code that resets memory.peak and run the relevant runtime or cgroup tests, if present. Done means the reset succeeds without the invalid-argument error and interval peak semantics are preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux
- Domain
- infrastructure, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100