Test-suite interop: run functional tests against presswork (Rust cupsd reimplementation)
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 44/100
Research direction
First check how the functional suite is run in CI and whether it exercises a daemon, then determine whether a second daemon is welcome. The proposal names no files or tests, so locate the suite's CI entry point and identify how it installs and starts stock cupsd. Done means an experimental CI leg runs the functional suite against presswork and reports actionable failures.
Written by the indexing model from the issue text.
Description
Hi - I'm the author of presswork, a drop-in replacement for the CUPS 2.x scheduler/daemon written in Rust (Apache-2.0 OR MIT). Same IPP wire protocol, config files, spool layout, and backend contract; upstream ipptool matrix 34/0/1, upstream test/5.x client suite 34/34.
Proposal: scp's test suite exercises real daemon behavior (queue create/delete, job ops, device URIs) - running it against presswork in addition to stock cupsd would validate both sides' IPP semantics and surface divergences as actionable bugs.
Happy to do the work (a CI leg installing presswork via the .deb or ghcr.io/vindeckyy/presswork:latest image, marked experimental). Is the functional suite currently daemon-backed in CI, and is a second-daemon leg welcome?
- Dominant language
- Python
- Stars
- 209
- Forks
- 111
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 8
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 OpenPrinting/system-config-printer
-
Job viewer shows "Printer error" for cups-waiting-for-job-completedPossibly taken @RonitMehta08 claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
OpenPrinting/system-config-printer#494 ·
Maintainers usually reply within 2 days
-
[Release Tracking] system-config-printer 1.5.19 milestonePossibly taken @alexpevzner claimed this 16 days ago. Open
OpenPrinting/system-config-printer#492 · 1 comment · 2 assignees ·
Maintainers usually reply within 2 days
-
ScannerOpen
Difficulty 3/5 1-2 days Newbie friendliness 25/100
OpenPrinting/system-config-printer#407 · 1 comment ·
Maintainers usually reply within 2 days
-
Doesn't run with PYTHONSAFEPATH enabledPossibly taken @xovishnukosuri claimed this 250 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
OpenPrinting/system-config-printer#387 ·
Maintainers usually reply within 2 days
-
system-config-printer can't open printer properties because job-cancel-after value is NonePossibly taken @xovishnukosuri claimed this 250 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
OpenPrinting/system-config-printer#385 · 1 comment ·
Maintainers usually reply within 2 days
All issues in OpenPrinting/system-config-printer
Similar issues
-
ready-for-agent
Difficulty 1/5 1-3 hours Newbie friendliness 79/100
gregwebs/agent-vm-images#216 ·
Maintainers usually reply within 1 day
-
Layout accepts a step threshold of 0 or less, then in-toto-verify crashes with StopIterationPossibly taken @BahaaMattar claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
gcivil-nyu-org/team5-mon-fall26#145 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gcivil-nyu-org/team3-mon-fall26#156 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
antlr/grammars-v4#5220 ·
Maintainers usually reply within 1 day