TraceMachina / TraceMachina/nativelink
Could not unwrap first stream message
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 244
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 54
Description
Some of my RBE executions result in the following message server-side:
2025-03-03T19:52:08.641989Z ERROR nativelink_service::bytestream_server: error: status: Internal, message: "Error receiving first message in stream : Could not unwrap first stream message", 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:51500, socket_addr: 0.0.0.0:50051
Another manifestation of toolchain issues? My builds do not fail.
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 at nativelink-service/src/bytestream_server.rs:641 and inspect the bytestream server's handling of the first message in a streaming write request. Reproduce the server-side error with an RBE execution if possible, then determine what distinguishes the failing stream from builds that complete successfully; done means the cause and a verifiable correction or diagnostic are identified.
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
- 25/100