You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, we have found a possible regression on master branch. When request body exceeds buffer body size it is stored on disk and never cleared up, which results into possible storage problems.
Here is repo with minimal setup. Nginx is configured to store data in /tmp folrder. There is for sure possibility that error is in configuration. But we didn't found it. We have fallbacked to version v1.0.1. Fallback is tested in branch fix.
The text was updated successfully, but these errors were encountered:
As you suggest, I cannot rule out a configuration issue, but, like you, I don't immediately see a problem there either.
On the other hand, the post-v1.0.1 commit 83682d2 may have caused an unintended side-effect like what you describe.
If you're interested, you could consider confirming that commit is indeed the cause of the difference in behaviour (i.e. try using both versions of the code both pre- and post- that commit).
Hello, we have found a possible regression on master branch. When request body exceeds buffer body size it is stored on disk and never cleared up, which results into possible storage problems.
Here is repo with minimal setup. Nginx is configured to store data in /tmp folrder. There is for sure possibility that error is in configuration. But we didn't found it. We have fallbacked to version v1.0.1. Fallback is tested in branch fix.
The text was updated successfully, but these errors were encountered: