Recover from socket hangup during ingest

[demiankatz]

Sometimes, poor network conditions or Fedora problems during ingest (exact cause not yet identified) can lead to a socket hangup. The ingest tool should be able to recover from this situation.

Example log excerpt:

2023-01-13T06:04:38.186Z info: Adding 4 of 8 - Jan034P-0004.tiff
2023-01-13T06:04:38.194Z info: Creating object vudl:776920 with models CoreModel, DataModel, ImageData
2023-01-13T06:04:38.305Z info: Adding relationship info:fedora/vudl:776920 info:fedora/fedora-system:def/model#hasModel info:fedora/vudl-system:CoreModel to vudl:776920
2023-01-13T06:04:38.328Z info: Adding relationship info:fedora/vudl:776920 info:fedora/fedora-system:def/model#hasModel info:fedora/vudl-system:DataModel to vudl:776920
2023-01-13T06:04:38.348Z info: Adding relationship info:fedora/vudl:776920 info:fedora/fedora-system:def/model#hasModel info:fedora/vudl-system:ImageData to vudl:776920
2023-01-13T06:04:38.366Z info: Adding relationship info:fedora/vudl:776920 info:fedora/fedora-system:def/relations-external#isMemberOf info:fedora/vudl:776916 to vudl:776920
2023-01-13T06:04:38.385Z info: Adding relationship info:fedora/vudl:776920 http://vudl.org/relationships#sequence vudl:776916#4 to vudl:776920
2023-01-13T06:04:38.581Z info: Initial Ingest addDatastream - MASTER
2023-01-13T06:04:49.198Z error: Unexpected problem: socket hang up

In this instance there was no MASTER datastream created on vudl:776920, so the error occurred before binary data was written to Fedora.

[demiankatz]

Example exception:

Exception during ingest -- Error: socket hang up
    at connResetException (node:internal/errors:705:14)
    at Socket.socketCloseListener (node:_http_client:467:25)
    at Socket.emit (node:events:525:35)
    at Socket.emit (node:domain:489:12)
    at TCP.<anonymous> (node:net:301:12)