OHDSI/Arachne

SyntaxWarning: invalid escape sequence '\w' when starting execution engine

Closed this issue · 3 comments

This isn't causing any usage problem as far as I see these warnings when I start up Arachne using docker compose

Attaching to arachne-datanode, arachne-datanode-postgres, arachne-execution-engine
arachne-execution-engine   | /usr/bin/systemctl:1541: SyntaxWarning: invalid escape sequence '\w'
arachne-execution-engine   |   expanded = re.sub("[$](\w+)", lambda m: get_env1(m), cmd.replace("\\\n",""))
arachne-execution-engine   | /usr/bin/systemctl:1543: SyntaxWarning: invalid escape sequence '\w'
arachne-execution-engine   |   new_text = re.sub("[$][{](\w+)[}]", lambda m: get_env2(m), expanded)
arachne-execution-engine   | /usr/bin/systemctl:1628: SyntaxWarning: invalid escape sequence '\w'
arachne-execution-engine   |   cmd3 = re.sub("[$](\w+)", lambda m: get_env1(m), cmd2)
arachne-execution-engine   | /usr/bin/systemctl:1631: SyntaxWarning: invalid escape sequence '\w'
arachne-execution-engine   |   newcmd += [ re.sub("[$][{](\w+)[}]", lambda m: get_env2(m), part) ]
arachne-execution-engine   | /usr/bin/systemctl:1541: SyntaxWarning: invalid escape sequence '\w'
arachne-execution-engine   |   expanded = re.sub("[$](\w+)", lambda m: get_env1(m), cmd.replace("\\\n",""))
arachne-execution-engine   | /usr/bin/systemctl:1543: SyntaxWarning: invalid escape sequence '\w'
arachne-execution-engine   |   new_text = re.sub("[$][{](\w+)[}]", lambda m: get_env2(m), expanded)
arachne-execution-engine   | /usr/bin/systemctl:1628: SyntaxWarning: invalid escape sequence '\w'
arachne-execution-engine   |   cmd3 = re.sub("[$](\w+)", lambda m: get_env1(m), cmd2)
arachne-execution-engine   | /usr/bin/systemctl:1631: SyntaxWarning: invalid escape sequence '\w'
arachne-execution-engine   |   newcmd += [ re.sub("[$][{](\w+)[}]", lambda m: get_env2(m), part) ]
arachne-execution-engine   |  * Starting periodic command scheduler cron
arachne-execution-engine   |    ...done.

Not often, but we saw the same in our environment. It looks like it's somehow happens in amazoncorretto docker image. May be we should consider to switch to another vendor for base image.

The problem was addressed in OHDSI/ArachneExecutionEngine#416

Available in the latest release of Execution Engine