After file transfer with beam, app dumps an Error message

[ryanramage]

I was testing beam on some various places and found this one strange one

1. success creating the sending beam
2. running the receiving beam I get this

spork beam REDACTED > received-file.json
▶ Connecting pipe...
▶ Joined the DHT - remote address is ---REDACTED---
▶ Success! Encrypted tunnel established to remote peer
node:internal/errors:464
    ErrorCaptureStackTrace(err);
    ^

Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
    at new NodeError (node:internal/errors:371:5)
    at healthCheck (node:dgram:909:11)
    at Socket.address (node:dgram:760:3)
    at HyperDHT._checkIfFirewalled (/home/ryan/.nave/installed/16.x/lib/node_modules/@atek-cloud/spork/node_modules/dht-rpc/index.js:590:79)
    at HyperDHT._updateNetworkState (/home/ryan/.nave/installed/16.x/lib/node_modules/@atek-cloud/spork/node_modules/dht-rpc/index.js:505:54)
    at HyperDHT.bootstrap (/home/ryan/.nave/installed/16.x/lib/node_modules/@atek-cloud/spork/node_modules/dht-rpc/index.js:179:24)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  code: 'ERR_SOCKET_DGRAM_NOT_RUNNING'

spork exits, and the file received-file.json exists - but the error message is a bit disturbing.

I see the same error is reported (and resolved) here holepunchto/dht-rpc#30

I also have checked the version of dht-rpc locally, and it looks like the most recent version

"name": "dht-rpc",
  "version": "5.0.1",

So I am not sure if this is still an dht-rpc issue, or somehow spork can ignore this and not print it out.