Rust pack retirement: preserve decoder and graphics primitive checks

Open
  • Is something wrong?
#558 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
20/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
python, rust
Domain
computer-graphics, testing

Research direction

Start with the Python checks in test_enigma.py, test_gfx.py and test_png.py, and find the matching Rust decoder, graphics and PNG tests. Add any checks that have no Rust counterpart, and document each drop or existing coverage. Blocked until the palette pause is lifted and the parent PSIV#115 authorization boundaries are confirmed. Done means the focused Rust primitive tests, decoder census parity and full-pack parity pass, and the PR lands.

Written by the indexing model from the issue text.

Description

later

Child of https://github.com/TusanHomichi/PSIV/issues/115. Finish only this task in one fresh session and one PR. The parent's original authorization boundaries still apply; this child grants no additional authority. Do not read earlier sessions' transcripts.

After the palette pause is lifted, map the checks in test_enigma.py, test_gfx.py and test_png.py onto existing Rust decoder, graphics and PNG coverage, adding missing checks. Preserve decoder acceptance and refusal behavior and decoded image content; do not require identical compression streams. Document justified drops and existing coverage. Keep Python and parity; use synthetic committed fixtures and local retail inputs.

Verification: Run focused Rust primitive tests, decoder census parity and full-pack parity. Demonstrate failures for decoding boundaries, color conversion and image-content corruption.

If this is too big, publish any progress, split it with proj split FILE (a JSON array of title/body/check tasks), then end the session. Wait for the PR to land before declaring this task done.

Dominant language
Rust
Stars
1
Forks
0
Avg merge
8h 43m
Merged PRs (30d)
288

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 TusanHomichi/PSIV

All issues in TusanHomichi/PSIV

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.