Bound archive and metadata processing without blocking the dashboard

Open
#222 0 comments 0 reactions 0 assignees View on GitHub

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

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

enhancement

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Isopod-Project/Isopod

All issues in Isopod-Project/Isopod

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.