Files
galaxy/lib
mvdbeek ef325c6a7a LazyTool: whitelist job-setup/param-validation methods for materialise
The LAZY_TOOL_STRICT=1 lazy Integration run surfaced three execution-path
attributes that were only materialising via the permissive fallback:

  - build_dependency_shell_commands (on __SET_METADATA__, which follows
    most jobs) — the runner builds the dependency/env shell commands for
    the tool it's about to run
  - params_with_missing_data_table_entry / params_with_missing_index_file
    (data-manager / index-file tools) — param validation that walks the
    parsed parameter tree at job time

All three genuinely need a parsed Tool, so add them to _MATERIALIZE_OK.
Under permissive mode this was a silent WARN + materialise; under strict
it raised NotImplementedError and failed every job-running integration
test. This is exactly the audit strict is meant to force — the fix makes
the materialisation explicit rather than accidental.

Claude-Session: https://claude.ai/code/session_018L7ZmCv2ubKA3JNeSL8Pkr
2026-07-28 17:27:26 +02:00
..
2026-07-22 08:11:31 +03:00