Open FTWinston opened 3 years ago
Thanks @FTWinston, you are correct it is a good idea to have an increased default timeout for POST
requests and also make it configurable.
Either of those sound good to me. Both sound great!
On Sun, 8 Nov 2020, 11:20 Erez Rokah, notifications@github.com wrote:
Thanks @FTWinston https://github.com/FTWinston, maybe it would be a good idea to have an increased default timeout for POST requests and also make it configurable.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/netlify/netlify-cms/issues/4538#issuecomment-723563209, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOG32MGOEJNTRRUEBHHDD3SOZ5INANCNFSM4TNVBKPQ .
I'm going to work on this issue 🎉
Hi,
I changed the timeout to 120 in the unsentRequest.js file.
Then I start getting the error below:
It's coming directly from GitHub and I couldn't find the root cause. How should we proceed?
@KancerEzeroglu I found this which seems to imply this is an HTTP post buffer size limitation. Is it possible to reduce the buffer Netlify CMS uses?
Hi,
I played with timeouts on our side but I still got errors from Github API, for me, it seems there are some limitations on the Github site. I couldn't find any option to set timeout and/or buffer size in the APIs.
As an improvement, we can show a more user-friendly error instead of logging an error to the console.
@erezrokah wdyt?
I missed the last comment on this issue.
If someone would like to pick this up, it would be great to share the error received from GitHub when we increase the timeout, and possibly report it to GitHub's support to see if that's expected.
As for ⬇️
@KancerEzeroglu I found this which seems to imply this is an HTTP post buffer size limitation. Is it possible to reduce the buffer Netlify CMS uses?
The CMS doesn't use git
directly, so that setting is not relevant for the CMS
Has there been any update on this issue? I'm also getting this error on Gitlab, I've already tried updating the CMS to the latest version and adding Large Media to see if that helps but still the request times out before completing.
Hi @modi98, nothing had changed since https://github.com/netlify/netlify-cms/issues/4538#issuecomment-752636207 though we've been mostly focused on GitHub.
If someone would like to take a look at fixing this for GitLab by increasing the timeout, happy to accept a contribution
I'm also experiencing this timeout with gitlab
I could take a look at fixing it if someone pointed me in the right direction. Haven't looked at the netlify-cms code base before
If I understand the Github docs regarding large files correctly, file uploads (via browsers) are limited to 25MB only: https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-large-files-on-github#about-size-limits-on-github
Describe the bug When uploading a large media file to a new post, the upload repeatedly times out after 60s. As it's a big file (~50MB), I'd expect the upload to take longer than 60s, but the CMSs repeatedly aborts and retries after 60s. It looks like this is intentional, perhaps caused by #3649?
Console output below:
To Reproduce
Expected behavior Saving should eventually succeed.
Applicable Versions:
CMS configuration config.yml
Additional context If this timeout were configurable, or could be disabled when uploading files, that would seem to me to prevent this problem.
Alternatively, if this is simply a much larger file than I ought to be storing in the CMS, then by all means tell me that.
Thanks in advance!