Interoperability with Dakota's sendvo.exe

[jdswinbank]

Pierre Le Sidaner reports that Comet rejects VOEvent's submitted by Dakota's sendvo.exe with a GPG error.

Not clear whether this is a fault in Comet, or if Dakota is sending something non-compliant. If it's the latter, consider whether we can be flexible.

[jdswinbank]

Mail to Pierre of 2016-12-28:

I've just been trying to track down the error which you saw when trying
to use Dakota's sendvo.exe to send an event with Comet, as reported in
your slides at
http://wiki.ivoa.net/internal/IVOA/InterOpMay2016-Ops/lesidaner_interop_cap_voevent.pdf.

I'm using the current release of Comet, running like this:

$ twistd -n comet --local-ivo ivo://org.swinbank/comet.broker.test -r

And I ran Dakota's sendvo.exe version 3.0.5.0 as follows:

$ mono ./sendvo.exe --broker=localhost testev.xml

(where textev.xml is the contents of
http://voeventdb.4pisky.org/apiv1/packet/xml/ivo%3A%2F%2Fvoevent.phys.soton.ac.uk%2FAMI- REQUEST%23140430-2033.58).

Both Comet and Dakota seem happy with this transaction: neither reports
an error, sendvo.exe exits cleanly, and Comet goes on to process the
event.

Can you provide any more information on how to reproduce the problem you
saw?

[jdswinbank]

Pierre responds that he will attempt to reproduce, but it'll likely be a couple of months before he's able to spend time on this.

[jdswinbank]

Given the lack of ability to reproduce, I'm not going to let this block future releases.