gradient_pattern_resolver.py cannot be imported — UnsupportedFillError missing from pipeline_api.py #100

New issue

Closed

opened 2026-07-25 19:14:47 +00:00 by Mark · 0 comments

Mark commented

2026-07-25 19:14:47 +00:00

Owner

Summary

The untracked file src/svg_parser/gradient_pattern_resolver.py (309 lines) contains a complete GradientPatternResolver class for linear/radial gradient flattening and pattern tiling, but cannot be imported or used because it references a non-existent exception.

Reproduction steps

Clone Mark/easystitch and check out main
Run: cd src && python3 -c "from src.pipeline_api import UnsupportedFillError"
→ ImportError: cannot import name UnsupportedFillError
Run: cd src && python3 -c "from svg_parser.gradient_pattern_resolver import GradientPatternResolver"
→ ImportError: cannot import name UnsupportedFillError (same root cause, line 9 of resolver)

Actual behavior

src/svg_parser/gradient_pattern_resolver.py line 9: from src.pipeline_api import UnsupportedFillError
UnsupportedFillError is not defined anywhere in src/ or tests/
The resolver file is never imported by any code in src/ or tests/ — grep for gradient_pattern_resolver or GradientPatternResolver returns only the file itself
No tests exist for gradient/pattern fills (tests/test_gradient_pattern_fills.py does not exist)

This was found during a post-deploy probe (kanban task t_8c8167c8) for parent fixit t_20642ccc which was supposed to implement issue #96.

Expected behavior

Either:

UnsupportedFillError is defined in pipeline_api.py and the resolver is properly integrated into the parser pipeline, OR
The resolver uses an existing exception type

Additional context

Original feature request: Mark/easystitch#96 (still OPEN)
Process finding (fixit completed prematurely): Mark/easystitch#99
Three stashes exist with earlier attempts that reference a different module name (fill_resolver) and exception (UnsupportedSVGFeatureError) — naming inconsistency vs current untracked file
.pyc artifacts confirm fill_resolver.py existed previously but was deleted/renamed
An implementation plan exists at .kilo/plans/easystitch-96-gradient-pattern-fills.md (122 lines, 5 slices)

Linking

Filed from kanban task t_8c8167c8. Relates to Mark/easystitch#96 and Mark/easystitch#99.

## Summary The untracked file `src/svg_parser/gradient_pattern_resolver.py` (309 lines) contains a complete `GradientPatternResolver` class for linear/radial gradient flattening and pattern tiling, but **cannot be imported or used** because it references a non-existent exception. ## Reproduction steps 1. Clone `Mark/easystitch` and check out `main` 2. Run: `cd src && python3 -c "from src.pipeline_api import UnsupportedFillError"` → `ImportError: cannot import name UnsupportedFillError` 3. Run: `cd src && python3 -c "from svg_parser.gradient_pattern_resolver import GradientPatternResolver"` → `ImportError: cannot import name UnsupportedFillError` (same root cause, line 9 of resolver) ## Actual behavior - `src/svg_parser/gradient_pattern_resolver.py` line 9: `from src.pipeline_api import UnsupportedFillError` - `UnsupportedFillError` is **not defined** anywhere in `src/` or `tests/` - The resolver file is **never imported** by any code in `src/` or `tests/` — grep for `gradient_pattern_resolver` or `GradientPatternResolver` returns only the file itself - No tests exist for gradient/pattern fills (`tests/test_gradient_pattern_fills.py` does not exist) This was found during a post-deploy probe (kanban task `t_8c8167c8`) for parent fixit `t_20642ccc` which was supposed to implement issue #96. ## Expected behavior Either: - `UnsupportedFillError` is defined in `pipeline_api.py` and the resolver is properly integrated into the parser pipeline, OR - The resolver uses an existing exception type ## Additional context - Original feature request: Mark/easystitch#96 (still OPEN) - Process finding (fixit completed prematurely): Mark/easystitch#99 - Three stashes exist with earlier attempts that reference a different module name (`fill_resolver`) and exception (`UnsupportedSVGFeatureError`) — naming inconsistency vs current untracked file - `.pyc` artifacts confirm `fill_resolver.py` existed previously but was deleted/renamed - An implementation plan exists at `.kilo/plans/easystitch-96-gradient-pattern-fills.md` (122 lines, 5 slices) ## Linking Filed from kanban task `t_8c8167c8`. Relates to Mark/easystitch#96 and Mark/easystitch#99.