[GitHub] [mesos] andreaspeters commented on pull request #415: Explicitely fail content length fetch in case of error

andreaspeters commented on pull request #415: URL: https://github.com/apache/mesos/pull/415#issuecomment-992960952 Ok, I understand. More risk then we can win makes also no sense for me. But in these case, I think we should close these PR. :-) -- This is an automated message from the

[GitHub] [mesos] andreaspeters commented on pull request #415: Explicitely fail content length fetch in case of error

andreaspeters commented on pull request #415: URL: https://github.com/apache/mesos/pull/415#issuecomment-990681467 May I asked where you see potential backward compatibility problems? -- This is an automated message from the Apache Git Service. To respond to the message, please log on

[GitHub] [mesos] andreaspeters commented on pull request #415: Explicitely fail content length fetch in case of error

andreaspeters commented on pull request #415: URL: https://github.com/apache/mesos/pull/415#issuecomment-988962972 @cf-natali for me it looks fine and with the response code handling more "nice" then before. :+1: -- This is an automated message from the Apache Git Service. To respond

[GitHub] [mesos] andreaspeters commented on pull request #415: Explicitely fail content length fetch in case of error

andreaspeters commented on pull request #415: URL: https://github.com/apache/mesos/pull/415#issuecomment-988939467 @cf-natali @qianzhangxa can u help here? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL