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

update_history doesn't change state of "published" field for history #31

Open
pcm32 opened this issue Jun 15, 2020 · 2 comments
Open

update_history doesn't change state of "published" field for history #31

pcm32 opened this issue Jun 15, 2020 · 2 comments

Comments

@pcm32
Copy link

pcm32 commented Jun 15, 2020

Running

parsec histories update_history --published db81bf5b52f28f9f

with proper credentials just gives me the status of the history, but doesn't change the state of published. This is trying against usegalaxy.eu.

This with parsec just installed via pip:

pip list
Package                  Version
------------------------ ----------
bioblend                 0.13.0
boto                     2.49.0
certifi                  2020.4.5.2
chardet                  3.0.4
click                    7.1.2
future                   0.18.2
galaxy-parsec            1.13.0
galaxy-workflow-executor 0.2.0
idna                     2.9
junit-xml                1.7
justbackoff              0.6.0
pip                      20.1.1
PyYAML                   5.3.1
requests                 2.23.0
requests-toolbelt        0.9.1
setuptools               41.2.0
six                      1.15.0
urllib3                  1.25.9
wrapt                    1.12.1
xunit-wrapper            0.12
@pcm32
Copy link
Author

pcm32 commented Jun 15, 2020

The same happens with a 19.05 separate instance I just tried.

@hexylena
Copy link
Member

So as far as I can tell, these parameters are non-functional? The current route that is used seems to be

Request URL:https://usegalaxy.eu/api/histories/$ID/sharing

but I don't have time to dig into the code. I think this might be a bioblend issue? (Exposing old route parameters that are no longer the main way to change this attribute.) @nsoranzo do you have an opinion?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants