overengineeringstudio / overengineeringstudio/effect-utils
Shard tsgolint into memory-budgeted Buck actions
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 82
- Forks
- 2
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 121
Description
Outcome
Run tsgolint as per-project Buck actions with a declared memory budget. Keep the same lint authority without requiring a larger runner.
Evidence
The lint lane reached 14.78 GiB on a 16 GiB runner and recorded an OOM kill. The Buck daemon held 4–5 GiB resident in that run; local measurements observed daemon residency up to 10.4 GiB. A second fresh isolation daemon can overlap the whole-repository tsgolint process.
Acceptance
- tsgolint is sharded by TypeScript project as cacheable Buck actions
- each action has an explicit memory budget and bounded concurrency
- fresh gate isolation daemons are reaped by the owning gate
- lint output and failure semantics remain equivalent
- a fresh 16 GiB CI run completes without OOM
- measured peak RSS and per-shard action counts are recorded
Refs #1147
Refs #1227
Posted on behalf of @schickling
| field | value |
|---|---|
agent_identity |
dev3.direct.omp.x7qqfv7y |
session |
dev3.x7qqfv7y |
agent_persona |
generalist |
agent_supervisor |
unavailable |
agent_tool |
OMP |
agent_tool_version |
18.1.7 |
agent_runtime |
OMP 18.1.7 |
tooling_profile |
dotfiles@c5db483 |
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 Buck configuration and CI gate entry points that invoke tsgolint, then trace how TypeScript projects and isolation daemons are handled. Verify completion against the acceptance list: cacheable per-project actions, memory budgets, bounded concurrency, daemon cleanup, equivalent lint results, and recorded RSS and shard counts on a fresh 16 GiB run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100