Skip to content

chore: remove 28 zero-match no_run entries and 5 dead env_vars overrides - #47

Merged
Jammy2211 merged 1 commit into
mainfrom
feature/no-run-config-purge
Jul 23, 2026
Merged

chore: remove 28 zero-match no_run entries and 5 dead env_vars overrides#47
Jammy2211 merged 1 commit into
mainfrom
feature/no-run-config-purge

Conversation

@Jammy2211

Copy link
Copy Markdown
Collaborator

Summary

28 of this repo's 30 no_run.yaml entries matched zero files, as did all 5 env_vars.yaml override patterns. They were copied in from autolens_workspace: 18 of the dead no_run entries and all 5 override patterns name files that exist only in that repo. HowToLens contains only chapter_*/tutorial_*.py, so a workspace path such as gui/mask or imaging/start_here can never match here — it is silently inert, not a skip.

Keeps the only two live entries, tutorial_searches and tutorial_5_borders.

Part of a 5-repo census (#46) that found 50 of 122 no_run.yaml entries (41%) dead across the organism, plus 11 dead env_vars patterns. Root cause is bidirectional copy-paste between the HowTo* repos and their parent workspaces — autolens_workspace carries three HowToLens tutorial stems in return.

Each cleaned file gains a header recording the matcher rule and that the list is repo-local and must not be copied between repos; the copy-paste is the actual defect, and a purge without it just resets the clock.

overrides: [] is written explicitly rather than left as a bare key, because env_config.py:73 reads .get("overrides", []) and an empty key loads as None, which would raise on iteration.

Scripts Changed

None — this PR is config-only.

  • config/build/no_run.yaml — 30 entries → 2 (kept tutorial_searches, tutorial_5_borders)
  • config/build/env_vars.yaml — 5 override patterns → overrides: [] (imaging/start_here, interferometer/start_here, group/start_here, multi/start_here, guides/results/)

Test Plan

  • Smoke tests pass — 6/6 passed
  • Proven behaviour-neutral: for all 47 scripts here, the resolved should_skip set and the fully-resolved build_env_for_script dict are byte-identical before vs after, because every removed entry matched zero files. Verified with the real matcher (PyAutoHands/autobuild/build_util.py:143).
  • Census re-run: 0 zero-match entries remain, across all 10 build targets

Generated by the PyAutoLabs agent workflow.

28 of this repo's 30 no_run.yaml entries matched zero files, as did all 5
env_vars.yaml override patterns. They were copied in from autolens_workspace:
18 of the dead no_run entries and all 5 override patterns name files that
exist only in that repo. HowToLens contains only chapter_*/tutorial_*.py, so
a workspace path such as `gui/mask` or `imaging/start_here` can never match
here — it is silently inert, not a skip.

Keeps the only two live entries, `tutorial_searches` and `tutorial_5_borders`.

`overrides: []` is written explicitly rather than left as a bare key, because
env_config.py reads `.get("overrides", [])` and an empty key loads as None,
which would raise on iteration.

Behaviour-neutral: for all 47 scripts here the resolved should_skip set and
the resolved build_env_for_script dict are identical before and after, since
every removed entry matched zero files.

Closes part of #46

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011ZVaiShnRkv1xbQBegGK1N
@Jammy2211 Jammy2211 added the pending-release PR queued for the next release build label Jul 23, 2026
@Jammy2211
Jammy2211 merged commit 46b6c58 into main Jul 23, 2026
10 checks passed
@Jammy2211
Jammy2211 deleted the feature/no-run-config-purge branch July 23, 2026 12:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pending-release PR queued for the next release build

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant