We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
1.8
If I have time, I'll try to create a minimal reproduction.
When I upgraded my app (deployed to fly.io as a Node service) to Remix 1.8 (from 1.7.6), I got alerts that my server was repeatedly crashing. The errror returned comes from @remix-run/web-fetch@4.3.2 https://github.com/remix-run/web-std-io/blob/main/packages/fetch/src/fetch.js#L342 where the error message says "Premature Close".
@remix-run/web-fetch@4.3.2
Reverting back to @remix-run/node@1.7.6 and @remix-run@web-fetch@4.31 solved the issue for me.
No fetch errrors.
Fetch errors.
The text was updated successfully, but these errors were encountered:
CC @jacob-ebey
Sorry, something went wrong.
Do you have a minimal example of the application code that is causing this codepath?
@jacob-ebey Can you check this? #4741 (comment)
Same issue as #4993
I'll close this issue for now as the other ticket has a failing test case that can be used to debug.
jacob-ebey
No branches or pull requests
What version of Remix are you using?
1.8
Steps to Reproduce
If I have time, I'll try to create a minimal reproduction.
When I upgraded my app (deployed to fly.io as a Node service) to Remix 1.8 (from 1.7.6), I got alerts that my server was repeatedly crashing. The errror returned comes from
@remix-run/web-fetch@4.3.2
https://github.com/remix-run/web-std-io/blob/main/packages/fetch/src/fetch.js#L342 where the error message says "Premature Close".Reverting back to @remix-run/node@1.7.6 and @remix-run@web-fetch@4.31 solved the issue for me.
Expected Behavior
No fetch errrors.
Actual Behavior
Fetch errors.
The text was updated successfully, but these errors were encountered: