I've been going over the failing streams on the dashboard and noticed the case of http://vocab.nerc.ac.uk/ldes/P01/ which fails with a strange error message:
Replicating stream from http://vocab.nerc.ac.uk/ldes/P01/
TypeError: fetch failed
at node:internal/deps/undici/undici:12500:13
at async ActorHttpFetch.getResponse (/Users/konstantin/Developer/imec/ldes-registry/node_modules/@comunica/actor-http-fetch/lib/ActorHttpFetch.js:43:34)
at async ActorHttpFetch.run (/Users/konstantin/Developer/imec/ldes-registry/node_modules/@comunica/actor-http-fetch/lib/ActorHttpFetch.js:122:30)
at async ActorDereferenceHttp.run (/Users/konstantin/Developer/imec/ldes-registry/node_modules/@comunica/actor-dereference-http/lib/ActorDereferenceHttpBase.js:62:28)
at async ActorDereferenceRdfParse.run (/Users/konstantin/Developer/imec/ldes-registry/node_modules/@comunica/bus-dereference/lib/ActorDereferenceParse.js:56:29)
at async Fetcher.fetch (/Users/konstantin/Developer/imec/ldes-registry/node_modules/ldes-client/dist/lib/pageFetcher.js:44:26) {
[cause]: SocketError: other side closed
at Socket.<anonymous> (node:internal/deps/undici/undici:7613:28)
at Socket.emit (node:events:531:35)
at endReadableNT (node:internal/streams/readable:1696:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
code: 'UND_ERR_SOCKET',
socket: {
localAddress: '192.168.1.25',
localPort: 62801,
remoteAddress: '192.171.196.70',
remotePort: 80,
remoteFamily: 'IPv4',
timeout: undefined,
bytesWritten: 2914,
bytesRead: 15283
}
}
}
It's not clear if the issue is malformed LDES or something else. I manually retrieved the initial fragment but couldn't find a reference to 192.171.196.70. It will be very helpful if information about the failing target URI is included in the Error. Even the specific fragment URI where the failing link was found would be helpful to troubleshoot such cases.
I've been going over the failing streams on the dashboard and noticed the case of
http://vocab.nerc.ac.uk/ldes/P01/which fails with a strange error message:It's not clear if the issue is malformed LDES or something else. I manually retrieved the initial fragment but couldn't find a reference to
192.171.196.70. It will be very helpful if information about the failing target URI is included in the Error. Even the specific fragment URI where the failing link was found would be helpful to troubleshoot such cases.