site: nothing runs the operation-reference picture tests
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 85/100
Research direction
Start in release.yml: find the site job that runs zola build and add the Python test invocation next to it, then document the command in site/README.md. Read site/tests/test_operation_reference.py first to see how it detects the Zola binary and skips the Zola arm when absent, and preserve that behaviour. Done when a cut run executes the test in the site job and fails if an operation picture view or reference section is missing.
Written by the indexing model from the issue text.
Description
Problem
PR #1825 added site/tests/test_operation_reference.py. It pins the 44 operation
pictures against the OpType enum. Nothing runs it. cargo xtask gate covers
Rust suites only. The site job in release.yml runs zola build but not this
Python test. No other workflow calls it.
A later PR that adds an OpType kind can forget its reference section and its
picture view. No gate fails, so the site stays incomplete without a signal.
Fix
Run the test from the site job of release.yml, next to the Zola build.
Add the run command to site/README.md so contributors know it exists.
Keep the test's Zola arm skippable when the binary is absent, as today.
Done means:
- A cut run executes
test_operation_reference.pyin the site job. - The job fails when a picture view or a reference section is missing.
Refs #1250
- Dominant language
- Rust
- Stars
- 8
- Forks
- 11
- Avg merge
- 6h 45m
- Merged PRs (30d)
- 905
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 NeoTech/Camcraft
-
area:ui bug effort:low P2 source:agent
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
area:ui effort:low enhancement P7 source:agent
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
NeoTech/Camcraft#2039 · 3 comments ·
Maintainers usually reply within 1 day
-
area:sim area:turning effort:low P7 source:agent
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
NeoTech/Camcraft#1855 · 4 comments ·
Maintainers usually reply within 1 day
-
area:turning area:ui effort:low P7 source:agent
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
post-merge.yml: the report job is skipped when the gate fails, so a red main opens no issuePossibly taken @tbrasselle claimed this today. Openarea:build bug claimed effort:low P5 source:agent
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
NeoTech/Camcraft#1611 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
All issues in NeoTech/Camcraft
Similar issues
-
crate: spate-kafka priority: low tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
macOS 菜单栏托盘图标保留橙色,与系统单色图标风格不一致Possibly taken @xhugoliu claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
YizhengWw/HachimoDock#56 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
akitaonrails/ai-memory#2314 ·
Maintainers usually reply within 1 day