Bound archive and metadata processing without blocking the dashboard
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- backend, performance
Research direction
Start by tracing the backend paths that download packs and imports, process JAR metadata, and decode images; the issue does not name specific files or tests. Map where transfer, decompression, metadata, and image work runs, then identify the existing test setup for isolated fixtures. Done means enforcing shared nested-content budgets, moving blocking work to bounded workers with cleanup, adding the specified boundary and responsiveness tests, and updating the wiki with limits and recovery steps.
Written by the indexing model from the issue text.
Description
What to build
Apply explicit transfer, member-count, per-member, expanded-byte and image-size budgets to downloaded packs, imports, JAR metadata and images. Run heavy processing in bounded workers so normal dashboard requests remain responsive.
Context
Distinct from #213: that ticket limits game-server containers, while this work bounds content processing inside the dashboard backend. No outage was demonstrated by the audit.
This follows the November 17 source audit. Treat it as a hardening/validation task, not a confirmed exploit report. Detailed audit evidence and validation limitations remain in the local audit report; report any confirmed vulnerability privately under SECURITY.md.
Acceptance criteria
- Define and enforce explicit budgets at download, decompression, metadata and image-decoding stages; nested content shares an aggregate budget.
- Move blocking parsing/extraction work off async request handlers into bounded workers with deadlines and cleanup on failure/cancellation.
- Reject over-budget dummy fixtures predictably without leaving incomplete downloads or partial installed content.
- Add isolated tests for accepted content, limit boundaries, cleanup and ordinary dashboard responsiveness; do not stress shared services.
- Update the wiki with new content limits, rejection messages and recovery steps.
Blocked by
None (can start independently). Coordinate with related issues without expanding their scope.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 13h 12m
- Merged PRs (30d)
- 57
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from Isopod-Project/Isopod
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Isopod-Project/Isopod#220 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
Isopod-Project/Isopod#200 ·
Maintainers usually reply within 1 day
-
Dashboard drives high GPU usage while a server starts or restartsPossibly taken @tacoz234 claimed this 12 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Isopod-Project/Isopod#191 · 1 comment ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Isopod-Project/Isopod#134 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Isopod-Project/Isopod#113 ·
Maintainers usually reply within 1 day
All issues in Isopod-Project/Isopod
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hemilabs/ui-monorepo#2711 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
code-yeongyu/senpi#6929 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 72/100
lingdojo/kana-dojo#34261 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
embedpdf/embed-pdf-viewer#1116 ·
Maintainers usually reply within 1 day
-
current task
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Sunday-School-Software/Sunday-School-Scheduler#87 ·
Maintainers usually reply within 1 day