msiExecCmd not usable from Python Rules about irods_rule_engine_plugin_python

[korydraughn]

I see. I missed the line where you mentioned that that code may appear in core.py.

[jaguc]

and still not working

[trel]

Hi @jaguc - is this a blocker in any way for you?

[d-w-moore]

Although it may be beside the point, the subprocess module can perform the same function, including trapping the output of stdout and stderr.

[trel]

@d-w-moore Can you share an example here as a workaround?

[d-w-moore]

Sure, a rough example fashioned as a rule - and usage of same - might appear in the core.py:

import subprocess
  
def msiExecCmd_ish(args, dummy_callback, dummy_rei):
    command = ['/var/lib/irods/msiExecCmd_bin/'+args[0]] + args[1].split()
    p = subprocess.Popen( command, stdout=subprocess.PIPE, stderr=subprocess.PIPE )
    (out,err) = p.communicate()
    args[2] = out
    args[3] = err

def use_it(arg,callback,rei):
    ret = callback.msiExecCmd_ish("hello",#program
                                  "a b",  #args
                                  "","")
    callback.writeLine("stdout is",ret['arguments'][2])  # print returned stdout
    callback.writeLine("stderr is",ret['arguments'][3])  # print returned stderr

Although if using this through a py_remote call, it may be necessary to contrive the return of stderr and stdout either through the iRODS Rule language, or if that's not installed, by use of TCP/IP sockets.

[korydraughn]

Why do you need to call msiExecCmd_ish through the callback parameter?
Can't it just be called directly?

[d-w-moore]

Why do you need to call msiExecCmd_ish through the callback parameter? Can't it just be called directly?

You don't really need to, but if the idea is to have a rule/msvc analog to msiExecCmd that is remote-callable from another arbitrary iRODS server, this might be how to do it.

[jaguc]

Hi @jaguc - is this a blocker in any way for you?

Hi @trel actually not. I was trying things and I was wondering why was not working, so I ended here and I saw that @d-w-moore had the same issue, so I posted that was still open

[trel]

@jaguc yes, it's still open. no activity on it so far, other than this thread. thanks for the follow up.