buildbox-casd and buildbox-fuse mismatch when having both wheel and system installed versions
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- grpc, python
- Domain
- build-system
Research direction
Start by reproducing the installation scenario with buildbox-casd in PATH and buildbox-fuse from the wheel, then trace how BuildStream selects each executable. Use the reported buildboxcasd_fusestager.cpp failure and gRPC error to identify the version mismatch boundary. Done should mean incompatible system and wheel components are no longer silently combined.
Written by the indexing model from the issue text.
Description
When having buildbox installed in the PATH and in the wheel, buildstream mismatches them. IIRC, it will use the buildbox-casd from the PATH and buildbox-fuse from the wheel.
If the two versions are incompatible, this can result in a buildstream crash with the error:
grpc._channel._MultiThreadedRendezvous: <_MultiThreadedRendezvous of RPC that terminated with:
status = StatusCode.INTERNAL
details = "std::runtime_error exception thrown at [buildboxcasd_fusestager.cpp:144], errMsg = "The FUSE stager child process unexpectedly died with exit code 1""
debug_error_string = "UNKNOWN:Error received from peer {created_time:"2024-11-20T09:16:31.255363002+00:00", grpc_status:13, grpc_message:"std::runtime_error exception thrown at [buildboxcasd_fusestager.cpp:144], errMsg = \"The FUSE stager child process unexpectedly died with exit code 1\""}"
- Dominant language
- Python
- Stars
- 151
- Forks
- 49
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 6
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from apache/buildstream
-
logging
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
apache/buildstream#2150 · 3 comments ·
-
question
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
apache/buildstream#2143 · 2 comments · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 74/100
apache/buildstream#2196 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
apache/buildstream#2194 ·
-
Modification time of an element with an open workspace propagates into consumer element's sandboxOpenbug
Difficulty 3/5 1-2 days Newbie friendliness 58/100
apache/buildstream#2186 · 2 comments · 2 reactions ·
All issues in apache/buildstream
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
raullenchai/Rapid-MLX#4042 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
LearningCircuit/local-deep-research#7067 ·
Maintainers usually reply within 1 day
-
#bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
apache/superset#44923 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
lawndoc/stack-back#123 ·