Print

Print


OK, I didn't look at the HTTP TPC code. Then that means the correct flags
are not being set in the ErrInfo object (assuming the code directly uses
the OFS plugin). Before I get myself into a contorted state I really need
to understand what that code really does. Any pointers ahead of time would
be appreciated.

Andy

On Thu, 18 Apr 2019, Brian P Bockelman wrote:

> Why do you think this is coming from the bridge and not the SFS object? My understanding of @olifre's description is that everything else works except TPC (which is the only place where we invoke the filesystem directly).
>
> --
> You are receiving this because you were mentioned.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/968#issuecomment-484614911


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

{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/xrootd/xrootd","title":"xrootd/xrootd","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/xrootd/xrootd"}},"updates":{"snippets":[{"icon":"PERSON","message":"@abh3 in #968: OK, I didn't look at the HTTP TPC code. Then that means the correct flags \nare not being set in the ErrInfo object (assuming the code directly uses \nthe OFS plugin). Before I get myself into a contorted state I really need \nto understand what that code really does. Any pointers ahead of time would \nbe appreciated.\n\nAndy\n\nOn Thu, 18 Apr 2019, Brian P Bockelman wrote:\n\n\u003e Why do you think this is coming from the bridge and not the SFS object? My understanding of @olifre's description is that everything else works except TPC (which is the only place where we invoke the filesystem directly).\n\u003e\n\u003e -- \n\u003e You are receiving this because you were mentioned.\n\u003e Reply to this email directly or view it on GitHub:\n\u003e https://github.com/xrootd/xrootd/issues/968#issuecomment-484614911\n"}],"action":{"name":"View Issue","url":"https://github.com/xrootd/xrootd/issues/968#issuecomment-484619077"}}} [ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/968#issuecomment-484619077", "url": "https://github.com/xrootd/xrootd/issues/968#issuecomment-484619077", "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