- galaxy-dev - lists.galaxyproject.org

TestToolShed failure, Exception: History in error state.
by Peter Cock 01 Aug '14

01 Aug '14

Hi all, I'm not sure when this started (having hardly looked at my Tool Shed test results since GCC2014), but I think this is a fairly recent problem with my BLAST RBH tests failing (which has held me back from posting this to the main Tool Shed). This could be some silly mistake in my tar-ball, but usually missing test files and the like get an explicit error. The tests are passing on my GitHub/TravisCI setup (using Twill and the API backend): e.g. https://travis-ci.org/peterjc/galaxy_blast/builds/30592097 Here is the current error (the same for the last few Test Tool Shed runs), https://testtoolshed.g2.bx.psu.edu/view/peterjc/blast_rbh Traceback (most recent call last): File "/var/opt/buildslaves/buildslave-ec2-2/buildbot-install-test-test-tool-shed-py27/build/test/functional/test_toolbox.py", line 108, in test_tool self.do_it( td ) File "/var/opt/buildslaves/buildslave-ec2-2/buildbot-install-test-test-tool-shed-py27/build/test/functional/test_toolbox.py", line 35, in do_it self._verify_outputs( testdef, test_history, shed_tool_id, data_list, galaxy_interactor ) File "/var/opt/buildslaves/buildslave-ec2-2/buildbot-install-test-test-tool-shed-py27/build/test/functional/test_toolbox.py", line 69, in _verify_outputs galaxy_interactor.verify_output( history, output_data, output_testdef=output_testdef, shed_tool_id=shed_tool_id, maxseconds=maxseconds ) File "/var/opt/buildslaves/buildslave-ec2-2/buildbot-install-test-test-tool-shed-py27/build/test/base/interactor.py", line 53, in verify_output self.wait_for_history( history_id, maxseconds ) File "/var/opt/buildslaves/buildslave-ec2-2/buildbot-install-test-test-tool-shed-py27/build/test/base/interactor.py", line 107, in wait_for_history self.twill_test_case.wait_for( lambda: not self.__history_ready( history_id ), maxseconds=maxseconds) File "/var/opt/buildslaves/buildslave-ec2-2/buildbot-install-test-test-tool-shed-py27/build/test/base/twilltestcase.py", line 2453, in wait_for result = func() File "/var/opt/buildslaves/buildslave-ec2-2/buildbot-install-test-test-tool-shed-py27/build/test/base/interactor.py", line 107, in <lambda> self.twill_test_case.wait_for( lambda: not self.__history_ready( history_id ), maxseconds=maxseconds) File "/var/opt/buildslaves/buildslave-ec2-2/buildbot-install-test-test-tool-shed-py27/build/test/base/interactor.py", line 257, in __history_ready return self._state_ready( state, error_msg="History in error state." ) File "/var/opt/buildslaves/buildslave-ec2-2/buildbot-install-test-test-tool-shed-py27/build/test/base/interactor.py", line 316, in _state_ready raise Exception( error_msg ) Exception: History in error state. Is a more detailed log available which might help debug this? Thanks, Peter As an aside, this looks like the Test Tool Shed is still using the Twill backend for the functional tests?

4 5

bx version conflict causes failure for some tools (e.g. subtract interval tool)
by Langhorst, Brad 01 Aug '14

01 Aug '14

see: https://biostar.usegalaxy.org/p/8095/ I can work around the problem by adding a stdio block to these tools, how should the underlying problem be solved? Brad -- Bradley W. Langhorst, Ph.D. Applications and Product Development Scientist

1 0

Error while installing tools from main toolshed: "HTTPerror : HTTP error 307 : temporary redirect"
by Perley, Danielle 01 Aug '14

01 Aug '14

Hi, I'm trying to install tools from the main toolshed, but I keep getting the same error regardless of the tool that I'm installing HTTPError: HTTP Error 307: Temporary Redirect URL: http://localhost:8080/admin_toolshed/prepare_for_install?tool_shed_url=http… Module weberror.evalexception.middleware:364 in respond view >> app_iter = self.application(environ, detect_start_response) Module paste.recursive:84 in __call__ view >> return self.application(environ, start_response) Module paste.httpexceptions:633 in __call__ view >> return self.application(environ, start_response) Module galaxy.web.framework.base:132 in __call__ view >> return self.handle_request( environ, start_response ) Module galaxy.web.framework.base:190 in handle_request view >> body = method( trans, **kwargs ) Module galaxy.web.framework:377 in decorator view >> return func( self, trans, *args, **kwargs ) Module galaxy.webapps.galaxy.controllers.admin_toolshed:1116 in prepare_for_install view >> updating=updating ) Module tool_shed.util.common_install_util:110 in get_dependencies_for_repository view >> all_repo_info_dict = get_required_repo_info_dicts( trans, tool_shed_url, util.listify( repo_info_dict ) ) Module tool_shed.util.common_install_util:451 in get_required_repo_info_dicts view >> response = urllib2.urlopen( request ).read() Module urllib2:127 in urlopen view >> return _opener.open(url, data, timeout) Module urllib2:410 in open view >> response = meth(req, response) Module urllib2:523 in http_response view >> 'http', request, response, code, msg, hdrs) Module urllib2:442 in error view >> result = self._call_chain(*args) Module urllib2:382 in _call_chain view >> result = func(*args) Module urllib2:608 in http_error_302 view >> new = self.redirect_request(req, fp, code, msg, headers, newurl) Module urllib2:569 in redirect_request view >> raise HTTPError(req.get_full_url(), code, msg, headers, fp) HTTPError: HTTP Error 307: Temporary Redirect I've just installed Galaxy locally for the first time on a Mac OS 10.9.3. The only changes I've made to the universe_wsg.ini file are: setting host=0.0.0.0 (The error also occurred with host=127.0.0.1?) specifying a full path for Tool_depenendency_dir giving myself administrator privileges with admin_users=myemail any ideas? Danielle

1 0

Toolshed tool_dependency.xml git archive configure issue
by Dooley, Damion 01 Aug '14

01 Aug '14

Hi folks, Having a difficult time with coding the "configure" step in this new tool_dependency.xml file, namely that an error "/bin/sh: configure: command not found" results when I try to install my beta development tool from a local test toolshed (which is downloading and installing other tools just fine). <actions> <action type="shell_command">git clone https://github.com/myuser/mygitstuff.git .</action> <action type="shell_command">git reset --hard 1819482db93bf0025c2588b5264cc0ec8c61029c</action> <action type="shell_command">configure --disable-gui --prefix=$INSTALL_DIR</action> <action type="make_install"></action> <action type="move_directory_files"> <source_directory>bin</source_directory> <destination_directory>$INSTALL_DIR/bin</destination_directory> </action> <action type="set_environment"> <environment_variable name="PATH" action="prepend_to">$INSTALL_DIR/bin</environment_variable> </action> </actions> Any hints about why this isn't being found or what the /bin/sh needs to get it going? When I do a git reset --hard, the "configure" file is definitely there, with executable flag set. Any other permission oddities? I've also tried <action type="autoconf"></action> , which yeilds same error. (Skipping that line and doing <action type="make_install"></action> at least finds and runs "make", though it errors out for lack of input data). Regards, Damion Hsiao lab, BC Public Health Microbiology & Reference Laboratory, BC Centre for Disease Control 655 West 12th Avenue, Vancouver, British Columbia, V5Z 4R4 Canada

2 5

galaxy install nginx
by ngsflow＠hygenomics.com 01 Aug '14

01 Aug '14

dear sir: nginx postgress galaxy which one first install ? ngsflow(a)hygenomics.com

2 1

Announcement: Galaxy IPython Integration - interactive programming in Galaxy
by Björn Grüning 01 Aug '14

01 Aug '14

Hi all, we proudly present the first release of the Galaxy IPython project. Galaxy IPython is a visualization plugin which should enable Galaxy users with coding skills to easily process their data in the most flexible way. With this plugin, it is possible to analyse and post-process data without downloading datasets or entire histories. One of our aims was to make Galaxy more attractive and accessible to bioinformaticians and programmers, and we hope that this project will build some bridges. Screencast: http://www.youtube.com/watch?v=jQDyTuYnn1k Disclaimer: Even though the Ipython notebooks can be stored and reused, this plugin will break the Galaxy philosophy of reproducibility, I feel personally bad about that, but I also think it is a great opportunity to get more bioinformaticians into Galaxy, and to get Galaxy used more often as a teaching resource. By being able to teach not only about workflows but also about data analysis tasks often necessary with Bioinformatics, Galaxy will be significantly more useful in teaching environments. Keep in mind to write a nice Tool Shed Tool if you catch yourself using IPython in Galaxy to often for the same task. A few features we have up and running: Use IPython directly in the main window or in the Scratchbook Completely encapsulated IPython environment with matplotlib, biopython, pandas and friends already installed. IPython runs completely self-contained within a docker container, separate from your Galaxy data Easy access to datasets from your current history via pre-defined IPython functions Manipulate and plot data as you like and export your new files back into your Galaxy history Save IPython Notebooks across analysis sessions in your Galaxy history with the click of a button. View saved IPython Notebooks directly in HTML format, or re-open them to continue your analysis. Self-closing and self-cleaning IPython docker container Notebooks are secure, only accessible to the intended user Please follow the installation instruction on our project page under: https://github.com/bgruening/galaxy-ipython The underlying IPython Notebook (+Galaxy sugar) is stored under: https://github.com/bgruening/docker-ipython-notebook https://registry.hub.docker.com/u/bgruening/docker-ipython-notebook/ You can also install a ipynb datatype: https://github.com/bgruening/galaxytools/tree/master/datatypes/json https://testtoolshed.g2.bx.psu.edu/view/iuc/datatyp_ipynb Comments welcome! Happy research! Eric & Björn

1 0

Galaxy Security Vulnerability
by Nate Coraor 31 Jul '14

31 Jul '14

A security vulnerability was recently discovered by Inge Alexander Raknes that would allow a malicious person to execute arbitrary code on a Galaxy server. The vulnerability was in a method that uses Python "pickle" functionality to decode state information from tool forms. Because pickles can be used to instantiate arbitrary Python objects, tool states could be constructed to exploit this vulnerability. Because this vulnerability allows for arbitrary code execution, administrators are strongly encouraged to apply this fix IMMEDIATELY. We have tried to make it as easy and quick as possible for server administrators to update their Galaxy instances. The fix has been applied to every stable release from 2013.01.13 until the tip, so it is possible to get this fix on older releases without updating to a newer feature release. You can do this by identifying your current release and updating to the `latest_<release_date>` tag corresponding to your release. For example, if you are running release_2013.11.04 (or a subsequent commit to the stable branch of Galaxy between release_2013.11.04 and release_2014.02.10), you can update with: % hg pull % hg update latest_2013.11.04 For the changes to take effect, YOU MUST RESTART ALL GALAXY SERVER PROCESSES. If you do not want to pull any upstream changes, we have also created a standalone patch that fixes this problem, with multiple versions depending on your current Galaxy release: - pickle-2013.11.04.patch - This patch should apply cleanly (with offset/fuzz) to releases from 2013.11.04 up to the current stable tip. Available at: https://depot.galaxyproject.org/patch/pickle-2013.11.04.patch - pickle-2013.01.13.patch - This patch should apply cleanly (with offset/fuzz) to releases from 2013.01.13 up to 2013.08.12, and possibly older versions of Galaxy as well. Available at: https://depot.galaxyproject.org/patch/pickle-2013.01.13.patch If you happen to be running a very recent revision on the default branch or the newly created next-stable branch, a pickle-default.patch file exists at the same place. For older releases or instances with conflicting local modifications, manual application of the patch should not be difficult as it only includes a few small changes. To apply the patch, navigate to the root of your Galaxy directory, then run (replacing <url_to_patch> with the URL above that is correct for your release): % wget -O pickle.patch <url_to_patch> or: % curl -o pickle.patch <url_to_patch> and then: % patch -p1 < pickle.patch patching file lib/galaxy/util/__init__.py Hunk #1 succeeded at 575 with fuzz 2 (offset -113 lines). patching file lib/galaxy/webapps/galaxy/controllers/ucsc_proxy.py Again, for the changes to take effect, YOU MUST RESTART ALL GALAXY SERVER PROCESSES. The Galaxy Team would like to extend special thanks to Inge Alexander Raknes and colleagues, who privately disclosed the vulnerability, with a full analysis and proof of concept. Credit for the fix and subsequent testing goes to my fellow Galaxy Team members John Chilton and Dannon Baker. On behalf of the Galaxy Team, --nate

1 0

package_r_2_11_0 and ggplot2
by Evan Bollig 31 Jul '14

31 Jul '14

I want to install ggplot2 into package_r. The library ggplot2 is no longer available from the CRAN mirror for R v2.11.0. How do you guys handle this situation? Can I install another package_r and have packages that depend on package_r_2_11_0 use the newer version? -Evan Bollig Research Associate | Application Developer | User Support Consultant Minnesota Supercomputing Institute 599 Walter Library 612 624 1447 evan(a)msi.umn.edu boll0107(a)umn.edu

2 6

fastq-mcf parameter bug
by Michael Mason 31 Jul '14

31 Jul '14

First time posting so I hope I do this correctly. I am using galaxy locally and installed the ea-utils fastq-mcf (FastqMcf). When using the trimming options (not defaults) the -C option gets set to the -s option. I checked the fastq-mcf.xml wrapper and indeed there is an mistake on line 42. -s $trimming.sampcnt Should be -C $trimming.sampcnt I hope this helps, Cheers, Mike ________________________________ --CONFIDENTIALITY NOTICE--: The information contained in this email is intended for the exclusive use of the addressee and may contain confidential information. If you are not the intended recipient, you are hereby notified that any form of dissemination of this communication is strictly prohibited. www.benaroyaresearch.org

1 0

Secure Passwords
by Shaun Webb 30 Jul '14

30 Jul '14

Hi, is there any current functionality or plans to enforce secure passwords when registering a new account? By secure I mean tests on length, use of capitals and alphanumeric characters etc. Thanks Shaun Webb -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.

2 1