 |
 |
Right, will open a pull request. The test was intended to be reproducible on top of plain xrootd, no eos (but it probably needs c++14 to compile), with a server setup as standalone, i.e. based on the 'standalone' configuration template. Since you needed to ask, I suppose the reproducer wasn't easily or reliably reproducing the problem, sorry about that. This problem does cause a crash, but I don't think the impact was high (the service would restart), and I believe the crash is also rare across the cluster (about once per month), so not high urgency either. So overall I would think the priority is medium at most. -- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1898#issuecomment-1422300264 You are receiving this because you are subscribed to this thread. Message ID: <[log in to unmask]> ######################################################################## 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