chore: fix node integration tests failing with HTTP 500 error #799
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ssing, mapped from HTTP status code 500" errors. The root cause was that the node process was started with `Stdio::piped()` for stdout/stderr, and when the pipe buffers filled up during heavy logging, the node would block on I/O writes, causing gRPC requests to fail. The fix changes the node process to use `Stdio::null()` instead, which prevents blocking. For debugging, users can run the node manually with `RUST_LOG=debug`.
greenhat
force-pushed
the
greenhat/i766-node-500-error
branch
from
80c2853 to
1c86c8c
Compare
otrho
approved these changes
Nov 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Close #766
This PR is stacked on #797 and should be merged after it.
The error "grpc-status header missing mapped from HTTP status code 500" errors. The root cause was that the node process was started with
Stdio::piped()for stdout/stderr, and when the pipe buffers filled up during heavy logging, the node would block on I/O writes, causing gRPC requests to fail.The fix changes the node process to use
Stdio::null()instead, which prevents blocking. For debugging, users can run the node manually withRUST_LOG=debug.