leanprover / leanprover/lean-workbench
Impose resource limits
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 1
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 35
Description
The following could be configurable in config.json:
- Maximum editor sessions for a given user
- Maximum editor sessions overall
"auto"variant could set this based on available memory
- Maximum editor sessions per project
- Per-session max memory usage (e.g. via
prlimit)
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
Start by locating the config.json handling and the code that creates and tracks editor sessions. Review how per-user, overall, and per-project sessions are represented, then investigate the proposed per-session limit using prlimit. Done means the four requested limits are configurable, including the auto overall-session variant, and are enforced consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, typescript
- Domain
- backend, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100