---------- Forwarded message ----------
From: John Mettraux <[email protected]>
Date: 2011/11/15
Subject: Re: ruote 2.0 : subprocess :ref => uri
To: Snifi <[email protected]>



On Tue, Nov 15, 2011 at 12:06:56AM -0800, Snifi wrote:
>
> I'm playing around with ruote for some time now, and first I have to
> say it is a great tool. Very mighty but at the same time as simple as
> possible.

Hello Snifi,

you're much welcome.

> Now I faced a problem regarding the quoted post and the feature
> subprocess pointing to an URI.
> When I try to use a subprocess pointing to an file on same machine, my
> process always hangs --> it cannot resolve the subprocess but also
> doesn't complain that it did not find any subprocess.
> So I am not sure whether from Syntax side I am really correct?
>
> So this is my process (in simplyfied version):
>
> (...)

I wrote this quick test script:

---8<---
require 'ruote'

#ruote = Ruote::Dashboard.new(Ruote::Worker.new(Ruote::HashStorage.new))
ruote = Ruote::Engine.new(Ruote::Worker.new(Ruote::HashStorage.new))
ruote.noisy = true

FileUtils.mkdir('subprocesses') rescue nil
File.open('subprocesses/send_mail', 'wb') do |f|
 f.puts(%{
#Ruote.define 'send_mail' do
Ruote.process_definition 'send_mail' do
 echo '** sent mail'
end
 })
end

wfid = ruote.launch(Ruote.define do
 echo '* in'
 subprocess :ref => 'subprocesses/send_mail'
 echo '* out'
end)

ruote.wait_for(wfid)
--->8---

and it worked fine with ruote 2.2.0 (gem) and ruote 2.2.1 (master).

> I already tried with the full path as subprocess ref (/home/snifi/
> subprocesses/send_mail) but it didn't help.
> For the subprocess itself I tried different versions: with first and
> last line and without, with giving a name to the definition and
> without.
>
> My process always hangs on searching/waiting for the subprocess/
> participant send_mail
> As nowhere is defined how the subprocess file has to look like, I
> assume my error should be in that file, but up to now I didn't find
> any information, how to solve the problem.

I have the impression that your flow is stuck in an error.

Try to run with engine.noisy = true and it will log each workflow
operation to the STDOUT, including the detailed error if any.

If you can't do that you could do something like:

---8<---
p engine.process(wfid)
--->8---

And it will print the complete state of your workflow instance.

If you're using ruote-kit, look at /_ruote/errors/ (IIRC).

For more information, look at:

 http://ruote.rubyforge.org/process_administration.html


I hope this will help, cheers,

--
John Mettraux - http://lambda.io/processi

-- 
you received this message because you are subscribed to the "ruote users" group.
to post : send email to [email protected]
to unsubscribe : send email to [email protected]
more options : http://groups.google.com/group/openwferu-users?hl=en

Reply via email to