-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Suppress filenames in SAM merge using egrep #4
Conversation
Based on fix suggested by Roberto Alonso (at CIPF) on the mailing list, see: https://lists.galaxyproject.org/pipermail/galaxy-dev/2015-February/021589.html
+1 Option "-h" is supported also on OS X: https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/egrep.1.html I was also suggesting to Roberto to open a PR, but including also the changes to lib/galaxy/datatypes/sequence.py . |
Fixing |
If someone is going to be looking into this anyway, it might be nice to make sure that we are using a list of arguments instead of a string when calling the external command. And also probably not use os.system. But this change looks good to me. |
Suppress filenames in SAM merge using egrep
This is an automated message. Thanks for your contribution, a Trello card to track this issue has been created. Apply this patch for testing. |
Fix Guru's name in CONTRIBUTORS.md
Resolves the merge conflict, one minor whitespace fix.
Update docs, re-instate backwards compatability
Fix execution order and short-circuit issue when installing tools
Stays up-to-date with dev of galaxy project
Force update repository manager to launch postfork.
propagate allowed username changes to form hints
I feel that mapping from ``` - from: blast+ to: blast ``` should be the same as ``` - from: name: blast+ version: Null to: blast ``` since it should just be syntatic sugar. And I think that second version reads like it should by default apply to all versions. I feel therefore it is probably better to explicitly require stating that a mapping only applies to unversioned requirements. This commit does that by introducing the syntax: ``` - from: name: blast+ unversioned: true to: name: blast version: 1.3.4 ``` It feels better to have strongly typed entities like this than to introduce magic constants such as: ``` - from: name: blast+ version: __unversioned__ to: name: blast version: 1.3.4 ``` which is another route this could have gone I guess.
Fixes #18633: ``` ValueError: dictionary update sequence element #4 has length 1; 2 is required File "galaxy/tools/__init__.py", line 1969, in handle_single_execution rval = self.execute( File "galaxy/tools/__init__.py", line 2066, in execute return self.tool_action.execute( File "galaxy/tools/actions/model_operations.py", line 89, in execute self._produce_outputs( File "galaxy/tools/actions/model_operations.py", line 120, in _produce_outputs tool.produce_outputs( File "galaxy/tools/__init__.py", line 3816, in produce_outputs new_labels_dict = dict(source_new_label) Exception caught while attempting to execute tool with id '__RELABEL_FROM_FILE__': ```
Based on fix suggested by Roberto Alonso (at CIPF) on the mailing list, see:
https://lists.galaxyproject.org/pipermail/galaxy-dev/2015-February/021589.html