#4 Zero length input message to an sqlUpserAction produces backtrace

[Adam Tauno Williams]

An effectively zero length sql action input message produces an error of

Traceback (most recent call last):
  File "/srv/test3/coils/src/coils/logic/workflow/services/process.py", line 453, in work
action_name, description = self.run_stanza(action_uuid)
  File "/srv/test3/coils/src/coils/logic/workflow/services/process.py", line 209, in run_stanza
parameters=stanza.get('params'))
  File "/srv/test3/coils/src/coils/core/context.py", line 143, in run_command
command.run()
  File "/srv/test3/coils/src/coils/core/logic/action.py", line 227, in run
self.do_action()
  File "/srv/test3/coils/src/coils/logic/workflow/actions/sql/upsert.py", line 47, in do_action
for keys, fields in self._read_rows(self._rfile, []):
  File "/srv/test3/coils/src/coils/logic/workflow/actions/sql/command.py", line 108, in _read_rows
fields[element.tag] = value
UnboundLocalError: local variable 'fields' referenced before assignment

"Effectively" means that the input data has one line, but the format states: "skipLeadingLines: 1" which e
Thus the field list is never initialized as no record is ever processes.
Translated input was:

<?xml version="1.0" encoding="UTF-8"?><ResultSet formatName="MTAWarehouseMaster" className="SimpleDelimitedFieldFormat" tableName="warehouse_master"></ResultSet>

[Adam Tauno Williams]