Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NetworkControlError/NetworkTimeoutError "feature not supported" in logs #1107

Closed
bfrederix opened this issue Apr 9, 2024 · 1 comment
Closed
Labels

Comments

@bfrederix
Copy link

Question
I'm using the Go library and running Tus in Google Cloud Run. I'm able to upload files fine using Uppy+Tus but I keep seeing this type of error in the logs:
WARN NetworkControlError/NetworkTimeoutError for PATCH request with error "feature not supported"

I'm not sure why these are happening. Maybe you can see from my code? I tried the configurations you see on line 122 but those actually made Tus stop working all together. Is there something I'm missing?

I know the NewHandler is probably recommended over the NewUnroutedHandler and handles everything, but I want to use the datadog muxtrace for observability purposes.

Here is the code for reference:
https://gist.github.com/bfrederix/1d88c109c0a5ae07f52f75764b6aa750

Thank you.

Setup details

  • Operating System: Google Cloud Run
  • Used tusd version: v2.2.2
  • Used tusd data storage: Google Cloud Storage
  • Used tusd configuration: You can see the config in the gist above (running the Go library)
  • Used tus client library: tusd (Golang imported library)
@Acconut
Copy link
Member

Acconut commented Apr 10, 2024

There was a similar question a few weeks ago that should help you understand what this error means: #1100

What I assume is that some middleware or router is wrapping the ResponseWriter in a way that does not support the ResponseController, which is necessary for tusd to properly handle timeouts. The corresponding middleware should then be adjusted as mentioned in #1100 (comment).

I hope this helps! Since this is already the second time someone ran into this, we should add this to the documentation somewhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants