`files.upload_stream` returns 408 Request Timeout error

[edward-ly]

Describe the bug

Since version 0.21.0, the files.upload_stream function always raises an exception with an error message like this:
[408] Request Timeout <upload_stream(v=True): user=admin, path=Media/example1.gif, cur_size=331398>

If version 0.20.2 or below is installed, the upload works just fine. I suspect, then, it has something to do with the migration to the niquests library, but I'm not sure why.

Steps/Code to Reproduce

You can follow the ExApp tutorial as an example. In requirements.txt, change the first line to nc_py_api[app]==0.21.1 to reproduce the error.

Expected Results

The upload succeeds.

Actual Results

The upload fails, with a server log entry created containing the error message described above.

Setup configuration

nc_py_api >= 0.21.0
nextcloud = 33.0.0

[bigcat88]

I can't reproduce this with standalone call to:

nc.files.upload_stream("10mb_video.mp4", "10mb_video.mp4")
nc.files.upload_stream("100mb_video.mp4", "100mb_video.mp4")

need more information to be able to reproduce.

by the way, does you the icon display for you?

there is issue reported in AppAPI but I can't find time to check it: nextcloud/app_api#630

[edward-ly]

Oh yeah, I forgot to mention this was seen in GitHub Codespaces (follow the Codespaces version of the tutorial), so maybe it's that?

I saw the icon on the first run, but whenever I made code changes and restarted the app, it disappeared. I'm not sure why either.

[oleksandr-nc]

Closing as stale and related only to GitHub Codespaces which is not reproducible locally

[edward-ly]

FYI I was finally able to find a workaround for this, which is basically to set the chunk_size argument of NextcloudApp.files.upload_stream to a low enough value (50 * 1024 worked for me). I'm not sure why this only happens in the codespace, though; just something to keep in mind.

Another odd observation/behavior that's not unique to the codespace: sometimes, the ExApp file action initially doesn't appear in the dropdown menu for individual files, but after I do something in the current folder such as upload/delete/rename the file, the file action appears again. It's not consistent, though, but my guess is that there's an issue whenever ui.files_dropdown_menu.register_ex is called multiple times (at time same time, calling ui.files_dropdown_menu.unregister before register_ex does not affect this behavior either). Anyway, this still requires more investigation to get to the root of.