Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sharing a WF report in a page does not share underlying datasets leading to blank spaces #12116

Closed
hexylena opened this issue Jun 9, 2021 · 3 comments

Comments

@hexylena
Copy link
Member

hexylena commented Jun 9, 2021

The history was not made public, just the WF report in a galaxy page. @shiltemann tried sharing the "Public URL" (it was not actually public, we should change that column title)

image

After getting a report from the consumer, and going back to publish the page she double checked in a private browsing session and noticed her datasets were missing:

image

It seems the history datasets that are referenced by the report are still private to her account and not made public.

This is on EU with default dataset privacy=true, I'm guessing that's why this wasn't caught?

I guess publishing a report should say "make report (and also all referenced datasets) public?" and then do that

@hexylena hexylena changed the title Sharing a WF report in a page Sharing a WF report in a page does not share underlying datasets leading to blank spaces Jun 9, 2021
@hexylena
Copy link
Member Author

hexylena commented Jun 2, 2022

Just a follow up on this, https://usegalaxy.org/u/helena-rasche/p/invocation-report-961f98d2b8a397dc for a publicly accessible example. Most things work (e.g. images) except not the table:

image

Pinging this because the GTN is adding training for WF reports that will be part of GCC. galaxyproject/training-material#3478

@mvdbeek
Copy link
Member

mvdbeek commented Nov 29, 2023

Duplicate of #13926 ?

@mvdbeek mvdbeek closed this as completed Nov 29, 2023
@mvdbeek
Copy link
Member

mvdbeek commented Nov 29, 2023

or the other way around, but one of them should be enough :)

@martenson martenson closed this as not planned Won't fix, can't repro, duplicate, stale Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants