4.4 years ago by
United States
Hi Brad,
I didn't check the galaxy-dev@bx.psu.edu mailing list to see if you explored the issue there yet. But you might try posting there to reach the dev community, the majority are using that venue still. That said, I did bring this post to the attention of our dev team later last week. A reply here is still a potential.
If you do/did come to a solution, through the dev list or other method, it would be great to post that back here. As a link if on the dev list (nabble or other) or if you have time for it, the actual solution written out (any source) to place it in the archives here as a searchable "A" post. You can answer your own Q's. Tthis applies to anyone who wishes to share learned solutions - more issue example "Q"'s with solutions "A"'s are always a good thing - one never knows what may be the key to unlock a future issue! Sometimes it is hard to know what the root cause is, and initial diagnostic clues can be interpreted many ways, by new and experienced alike.
Please know that dev questions are certainly welcome at Galaxy Biostar. While started for end-user Q's, we think the Biostar model is a great way to communicate and are letting the community as a whole (end users and dev alike) decide on the preferred forum going forward for support and general discussion. Any cross-over/transition takes early adaptors/advocates plus good measure of encouragement and patience :) Both may co-exit always, or not, we'll see!
Sorry I can't help more with the details, but while I can take a guess, I'd rather not head you down the wrong path and waste your time.
Best!! Jen, Galaxy team
That workaround is less than ideal :) not sure what to do about this though. Maybe we need to update Galaxy's version of this egg... what tool produces this error?
Another solution would be to find the tools that actually need Galaxy's lib dir and have them assert something so the job script template only includes PYTHONPATH for those tools. Unless this is one of those tools.