Kazuhiro Sera

Hi @iamarjun, thanks for writing in! We recently received a similar feedback and that was due to some server-side issue: https://github.com/slackapi/python-slack-sdk/issues/1162#issuecomment-1016209037 In the case where HTTP status 408 is returned...

That may be due to some connectivity issue between your host and Slack but I'm unable to help you out for it. Trying the same script in a different host...

@iamarjun Thanks for sharing more details! I've checked internal reports and found that other people are also facing this server-side issue with relatively large size files (I know that your...

@locomike I'm sorry to say this but I don't have anything further that I can suggest at this moment. We will continue communicating with the server-side teams.

I just excluded this issue from the auto-triage process. We are sorry again for the disruption that many apps have been experiencing with `files.upload` API. In the last few weeks,...

Note: I observe this warning with **aiohttp 3.6.2 + Python 3.8.x** while **it doesn't appear with Python 3.7.x**. It may be related to the internals of asyncio or the combination...

I'm not planning to actively work on this in the short term. If someone finds a solution and shares it with us, it'd be greatly appreciated.

Hi all, let me share some updates on this issue. Firstly, sincere apologies for taking a long time to resolve this issue on the Slack platform side. We do understand...

@elongl For better compatibility with legacy `files.upload`, the v2 method calls files.info to fetch the uploaded files' full metadata. We know that some people do not want to have `files:read`...

@elongl It is due to Slack server-side reasons and we won't change it, unfortunately. The underlying [`files.completeUploadExternal` API method](https://api.slack.com/methods/files.completeUploadExternal), which is part of files_upload_v2, works with only `files:write` scope, but...