mirror of
https://github.com/galaxyproject/galaxy.git
synced 2026-09-24 16:30:27 +08:00
mvdbeek
efd598802e
DataManagerTool resolves the registry by the <data_manager id> conf id, which may differ from the tool XML id (test_data_manager_async_submission_with_mismatched_conf_id). Eager threads it through load_hidden_tool(data_manager_id=...); lazy materialisation built the tool from the stored source alone, so DataManagerTool.__init__ fell back to the tool id and exec_after_process failed with 'Invalid data manager requested'. Discovery now records the conf id, the index entry carries it, and _create_tool_from_stored_source restores it at materialise time. Also stamp is_local from the discovered guid — it defaulted True, which kept the ToolConfRepository branch of the shed materialise path dead even with repository metadata present.