Skip to content

[26.0] Fix job access check for collection-only outputs#22603

Open
mvdbeek wants to merge 1 commit into
galaxyproject:release_26.0from
mvdbeek:access-check-fix
Open

[26.0] Fix job access check for collection-only outputs#22603
mvdbeek wants to merge 1 commit into
galaxyproject:release_26.0from
mvdbeek:access-check-fix

Conversation

@mvdbeek
Copy link
Copy Markdown
Member

@mvdbeek mvdbeek commented Apr 30, 2026

JobManager.get_accessible_job raised "Job has no output datasets" for non-owners (incl. anonymous users) on jobs that produced only dataset collections, even when the underlying datasets were public. Extend the access check to also consider output_dataset_collection_instances and fall back to HistoryManager.is_accessible on the job's history.

Fixes #22602

How to test the changes?

(Select all options that apply)

  • I've included appropriate automated tests.
  • This is a refactoring of components with existing test coverage.
  • Instructions for manual testing are as follows:
    1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

  • I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

`JobManager.get_accessible_job` raised "Job has no output datasets" for
non-owners (incl. anonymous users) on jobs that produced only dataset
collections, even when the underlying datasets were public. Extend the
access check to also consider `output_dataset_collection_instances` and
fall back to `HistoryManager.is_accessible` on the job's history.

Fixes galaxyproject#22602
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Needs Review

Development

Successfully merging this pull request may close these issues.

1 participant