On Oct 1, 2012, at 12:50 PM, Langhorst, Brad wrote:
> On Oct 1, 2012, at 12:16 PM, Nate Coraor <n...@bx.psu.edu>
>> Hi Derrick,
>> If you're using Postgres, it's now possible to clean these up using
> I hope this is not considered hijacking…
> I just tried to run the pgcleanup.py script and got this error message.
> __load_config INFO 2012-10-01 12:47:18,628 Reading config from
> __connect_db INFO 2012-10-01 12:47:18,637 Connecting to database with URL:
> _run ERROR 2012-10-01 12:47:18,722 Unknown action in sequence:
> _run CRITICAL 2012-10-01 12:47:18,723 Exiting due to previous error(s)
> <module> ERROR 2012-10-01 12:47:18,723 Caught exception in run sequence:
> Traceback (most recent call last):
> File "scripts/cleanup_datasets/pgcleanup.py", line 769, in <module>
> File "scripts/cleanup_datasets/pgcleanup.py", line 158, in _run
> SystemExit: 1
> I have not yet started digging into this yet… so maybe it only affects me -
> but I thought this information might be useful to you.
Whoops. Use --help to get the options list. I'll have it spit that out when
you don't specify an action in a commit in just a minute.
> Brad Langhorst
> Please keep all replies on the list by using "reply all"
> in your mail client. To manage your subscriptions to this
> and other Galaxy lists, please use the interface at:
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at: