Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

check_ui.sh: refuse an unknown test module before building anything

Open Beginner friendly
#421 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
85/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
bash, docker, python

Research direction

Start in scripts/check_ui.sh: the argument comment is at lines 6-7, and the existing early FLUX_UI_BROWSER check at lines 11-17 shows the pattern to follow before any docker command. Arguments reach python3 -m unittest at lines 64-68, which run in app/tests/ui/. Done when an unknown module such as test_doc exits with status 2 and the stderr message before Docker starts, test_docs and Module.Class.test still work, and the header comment mentions the early refusal.

Written by the indexing model from the issue text.

Description

good first issue

./scripts/check_ui.sh test_doc (a typo for test_docs) builds the images and starts the Compose stack before unittest fails with a missing-module error, several minutes later. The script already rejects a wrong FLUX_UI_BROWSER before Docker starts; module names should get the same early check.

Where to look

  • scripts/check_ui.sh (lines 6–7): the comment that describes the arguments (test_docs, or Module.Class.test).
  • scripts/check_ui.sh (lines 11–17): the existing early FLUX_UI_BROWSER check, which runs before Docker or temporary secrets.
  • scripts/check_ui.sh (lines 64–68): where the arguments reach python3 -m unittest in the ui-test container (working directory /work/tests/ui, which is app/tests/ui/ in the repository).

Acceptance criteria

  • For each argument, the module part (the text before the first .) must be a file app/tests/ui/<module>.py; otherwise the script prints unknown UI test module: <module> to stderr and exits with status 2 before any docker command runs.
  • Module.Class.test arguments and running with no arguments keep working as today.
  • The header comment says that unknown modules are refused early.

How to check
./scripts/check_ui.sh test_doc exits at once with the message and no Docker activity (docker ps shows no new flux-ui-* project). ./scripts/check_ui.sh test_docs still runs that module. Then the repository checks: python3 scripts/check_agent_setup.py, python3 -m unittest discover -s tests -p 'test_*.py', git diff --check.

New to Flux? Start with CONTRIBUTING. Comment here to say you are taking it.

Dominant language
TypeScript
Stars
3
Forks
0
Avg merge
14h 40m
Merged PRs (30d)
242

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ColdPhase/flux

All issues in ColdPhase/flux

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.