Print

Print

looks like recent xroot (4.12.3-llifpc2) insert (at least at times) a non ASCII character at the end of an error message, see screenshot below.
This breaks current code which reports and parse those messages.
Can it be avoided ?
While I only have an example from using CMS code , @makortel says that in this case it just prints xrootd message "as is"
Screenshot from 2021-08-31 17-48-12
Of course we can filter for non-ASCII on our side, but @klannon suggested to report this to you as well for a proper resolution. In this I am the current maintainer of a tool which relies on CMS framework reports, so am 2 software layers (CMSSW and CMS/WMCore) away from xroot, simply acting as messenger here, but I doubt I can be of further help.
Thanks

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1501", "url": "https://github.com/xrootd/xrootd/issues/1501", "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