So, we have a metalink and the client goes and tries each one of the links and each one fails with some erro other than file not found (e.g. authentication error). The actual reported error to the apprilixcation becomes ENOENT (file not found) which is clearly misleading. This has caused quite a few good chases along the way. Could the client keep track of the most comment error and append it to the error message. Perhaps something like:

File not found likely because .....

where .... is the error message text of the most relevant error. Even using the last non-enoent error would be better than always reporting ENOENT.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1071?email_source=notifications\u0026email_token=AA7NRDTYYHN2B7QHK33PKDTQOTT3RA5CNFSM4JAUREG2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HRWTX6Q", "url": "https://github.com/xrootd/xrootd/issues/1071?email_source=notifications\u0026email_token=AA7NRDTYYHN2B7QHK33PKDTQOTT3RA5CNFSM4JAUREG2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HRWTX6Q", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1