Run the frozen document-script packaging test in CI
Maintainers usually reply within 1 day
@MannXo is already working on this.
Since Oct 12, 2026.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
Research direction
Read release-local.yml, worker.spec, and docs/architecture/packaging.md, then inspect surfsense_local/backend/tests/packaging/test_frozen_document_scripts.py and how the workflow freezes the worker. Run the packaging test using the workflow’s environment and verify it runs after freezing. Done means CI runs this test and the Known gap is removed from the packaging documentation.
Written by the indexing model from the issue text.
Description
surfsense_local/backend/tests/packaging/test_frozen_document_scripts.py freezes the worker and runs Word, PDF, PowerPoint, Excel and pandas scripts the way a packaged app does, but no workflow runs it: packaging tests are deselected by default (-m "not packaging"), and release CI smokes only worker --check-vision-runtime. Since #2184, Studio's PowerPoint and Excel also run through the script runner, so a library missing from worker.spec would break every Office format and every agent document in a packaged build with no CI signal.
Done when: the test runs in release-local.yml after the freeze step (or in a workflow on changes to worker.spec), and the Known gap in docs/architecture/packaging.md is gone.
- Dominant language
- Python
- Stars
- 16.3k
- Forks
- 1.6k
- Avg merge
- 13h 17m
- Merged PRs (30d)
- 273
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 MODSetter/SurfSense
-
Security Scan: stop flagging pinned hashes and test fixtures on release PRsPossibly taken @karthikeya1220 claimed this 1 day ago. Opencode quality security
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
MODSetter/SurfSense#2225 · 1 comment ·
Maintainers usually reply within 1 day
-
Check Apple notarization credentials on dry runs and weeklyPossibly taken @Cedric921 claimed this 1 day ago. Opendesktop
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MODSetter/SurfSense#2224 · 1 comment ·
Maintainers usually reply within 1 day
-
Release workflow: keep the macOS certificate off the Windows dry-run buildPossibly taken @Cedric921 claimed this 1 day ago. Opendesktop security
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
MODSetter/SurfSense#2223 · 1 comment ·
Maintainers usually reply within 1 day
-
Write the ADR for chat modesPossibly taken @Cedric921 claimed this 1 day ago. Openarchitecture desktop documentation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
MODSetter/SurfSense#2220 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
All issues in MODSetter/SurfSense
Similar issues
-
documentation good first issue
Difficulty 2/5 Half a day Newbie friendliness 72/100
sujithputta02/Esapay#13 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
gke-labs/kube-agents#3277 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
jbacalso24/mimry#291 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 Under an hour Newbie friendliness 82/100
eli-alvarado/us-watchlist-alerts#14 ·
Maintainers usually reply within 1 day