Re: [galaxy-dev] problem with column options

2017-07-13 Thread Aysam Guerler
Hi Fabien, Are you referring to the entries shown in the drop-down when you click on the select field? Can you send a screenshot? Thank you, Sam On Thu, Jul 13, 2017 at 5:50 AM, fabien gogé wrote: > Dear All, > > I try to column options for a param linked to a dataset

[galaxy-dev] problem with column options

2017-07-13 Thread fabien gogé
Dear All, I try to column options for a param linked to a dataset contained in my history. The first column of my dataset contains sample names. I want it propose me all sample names contained in my dataset. It work when the dataset has few columns but it doesn't work when my dataset has a lot

Re: [galaxy-dev] inconsistent state set for workflow submissions [using bioblend]

2017-07-13 Thread John Chilton
The history state being 'ok' isn't a great metric for determining if the workflow is complete. The history state essentially only tells you if there are datasets of certain states in the history. At the start of the workflow - the invocation may be backgrounded and getting ready to run so there

[galaxy-dev] Cleaning up old exported histories

2017-07-13 Thread Lance Parsons
I’m running Galaxy on a CentOS6 server, and thus I don’t have the required version of Postgres available to use Nate’s |scripts/pgcleanup.py| script. One major addition in that script is to cleanup old exported history files. Does anyone have any advice, tips, (or scripts) that would help me