Skip to content
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

Running a workflow and only first steps are executed #4127

Closed
yvanlebras opened this issue May 31, 2017 · 5 comments
Closed

Running a workflow and only first steps are executed #4127

yvanlebras opened this issue May 31, 2017 · 5 comments

Comments

@yvanlebras
Copy link
Contributor

I have encountered some issues on a Galaxy 17.05 test server and have seen the same behaviour on usegalaxy.org. Some workflows are not executed completely e.g. only first 4 steps for example are executed and nothing (apparently no queued jobs so not the same issue than #3816) for the last X steps....

Has anyone seen this as well?

@mvdbeek
Copy link
Member

mvdbeek commented May 31, 2017

It would be very helpful if you could share a workflow demonstrating this problem.

@yvanlebras
Copy link
Contributor Author

yvanlebras commented May 31, 2017

After making some tests, I've found the problem! This is related to my other issue #4128. As I was thinking that tagging a dataset through a workflow step "configure output" option was not working, I have made tests and one was to tag with a #tag, term instead of the classical #tag syntax.... So it's due to an improper use of tag expression!

image

@mvdbeek mvdbeek reopened this May 31, 2017
@mvdbeek
Copy link
Member

mvdbeek commented May 31, 2017

That's not exactly the same issue though, here the workflow fails to schedule, while the other issue is that you don't get these colorful tags.

FWIW, I can reproduce this (with a trailing , in the hashtag), this is the traceback:

galaxy.workflow.run ERROR 2017-05-31 12:17:32,494 Failed to execute scheduled workflow.
Traceback (most recent call last):
  File "/Users/mvandenb/src/galaxy/lib/galaxy/workflow/run.py", line 80, in __invoke
    outputs = invoker.invoke()
  File "/Users/mvandenb/src/galaxy/lib/galaxy/workflow/run.py", line 169, in invoke
    jobs = self._invoke_step( step )
  File "/Users/mvandenb/src/galaxy/lib/galaxy/workflow/run.py", line 241, in _invoke_step
    jobs = step.module.execute( self.trans, self.progress, self.workflow_invocation, step )
  File "/Users/mvandenb/src/galaxy/lib/galaxy/workflow/modules.py", line 849, in execute
    self._handle_post_job_actions( step, job, invocation.replacement_dict )
  File "/Users/mvandenb/src/galaxy/lib/galaxy/workflow/modules.py", line 914, in _handle_post_job_actions
    ActionBox.execute( self.trans.app, self.trans.sa_session, pja, job, replacement_dict )
  File "/Users/mvandenb/src/galaxy/lib/galaxy/jobs/actions/post.py", line 397, in execute
    ActionBox.actions[pja.action_type].execute(app, sa_session, pja, job, replacement_dict)
  File "/Users/mvandenb/src/galaxy/lib/galaxy/jobs/actions/post.py", line 337, in execute
    app.tag_handler.set_tags_from_list( job.user, dataset_assoc.dataset, tags)
  File "/Users/mvandenb/src/galaxy/lib/galaxy/managers/tags.py", line 46, in set_tags_from_list
    self.apply_item_tags( user, item, unicodify( new_tags_str, 'utf-8' ) )
  File "/Users/mvandenb/src/galaxy/lib/galaxy/managers/tags.py", line 165, in apply_item_tags
    self.apply_item_tag( user, item, name, value )
  File "/Users/mvandenb/src/galaxy/lib/galaxy/managers/tags.py", line 131, in apply_item_tag
    lc_name = name.lower()
AttributeError: 'NoneType' object has no attribute 'lower'

So we should do some additional validation for the correct syntax of tags.

@dannon dannon self-assigned this May 31, 2017
@dannon
Copy link
Member

dannon commented May 31, 2017

(replied in #4128, I'm taking a look at this workflow tag editor this morning)

dannon added a commit to dannon/galaxy that referenced this issue Jun 1, 2017
dannon added a commit to dannon/galaxy that referenced this issue Jun 1, 2017
@mvdbeek
Copy link
Member

mvdbeek commented Jun 2, 2017

Closing this as it has been fixed in #4139. Feel free to re-open if the problem pops up again.

@mvdbeek mvdbeek closed this as completed Jun 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants