Print

Print

OK, I now understand the issue. It's the bloody gridmap file processing that has haunted us from the day it was introduced by Globus (gotta love those folks). What I really want is a maintainable patch. To help with this, could you resubmit this pull as a new one so we don't see all the amendments as it makes it very difficult to figure out where we can isolate the code. I'll close the old one once you do. Frankly, we don't need the history on this pull request. At that point I can recommend alternatives. Also, ATLAS has been living with this issue for some time. It's not like it's stopping them from doing TPC (albeit maybe not HTTP TPC) but that is not on a critical path. I am involved with that WLCG group and there are a lot of politics there and politics shouldn't make us deploy something that will be hard to maintain just because.

Now, there are two more issues here 1) where is the R5 version of this patch? 2) have you tested that this does not break GSI?

Mind you, we cannot accept a backport-only patch that is deemed critical as this would make R5 irrelevant. So, let's just slow down a bit and get a workable solution across all releases.

—
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/pull/1224#issuecomment-651624764", "url": "https://github.com/xrootd/xrootd/pull/1224#issuecomment-651624764", "name": "View Pull Request" }, "description": "View this Pull Request 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