TraceMachina / TraceMachina/nativelink
Bazel builds manifest InvalidArgument server-side
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 244
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 54
Description
This occurs occasionally:
2025-03-03T17:26:44.974998Z ERROR nativelink_service::bytestream_server: error: status: InvalidArgument, message: "Expected WriteRequest struct in stream : In ByteStreamServer::write", details: [], metadata: MetadataMap { headers: {} }
at nativelink-service/src/bytestream_server.rs:641
in nativelink_service::bytestream_server::write with request: Streaming
in nativelink_util::task::http_executor
in nativelink::services::http_connection with remote_addr: 192.168.191.244:56972, socket_addr: 0.0.0.0:50051
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the error at nativelink-service/src/bytestream_server.rs:641 and trace ByteStreamServer::write for the malformed stream. Reproduce the occasional Bazel build failure while collecting the server log and request context. Done means identifying the cause of the InvalidArgument response and confirming affected builds no longer produce it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100