Populate max_total_pixels from imageflow job constraints
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Context
imageflow_core creates ImageJob instances via zenpipe. It needs to map its existing constraint system to Limits::max_total_pixels so animated image budgets are enforced for imageflow users.
TODO
- Find where imageflow_core constructs
zenpipe::Limits(orImageJob::with_limits()) - Map imageflow's existing frame/pixel constraints to
max_total_pixels - If imageflow has no equivalent constraint, add a sensible default (e.g., SERVER's 1B) when processing animated inputs
- Add integration test: animated GIF exceeding total pixel budget returns error, not OOM
Depends on imazen/zenpipe#17 (done) and imazen/zenpipe#18 (zencodecs wiring).
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
Locate where imageflow_core constructs zenpipe::Limits or calls ImageJob::with_limits(), then inspect the existing frame and pixel constraints. Map those constraints to max_total_pixels, or confirm the appropriate default for animated inputs. Done means an integration test shows an animated GIF over the total-pixel budget returns an error instead of causing an OOM.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100