dimensionalOS / dimensionalOS/dimos
xarm_grasp_sim.tar.gz: LFS object missing on server (404)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 808
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 233
Description
Summary
The Git LFS object backing data/.lfs/xarm_grasp_sim.tar.gz is missing from the server — the pointer file exists in the repo, but the object returns 404 from the LFS batch API.
Pointer contents (current main, unchanged since introduction):
oid sha256:7541ab8f252219be685e7c98cd79c08acc40cd783dccaa3d5f634617d596db6a
size 2295052
Introduced in 29fe5f550 ("feat(sim): xarm-grasp-sim scene package"), touched again by ff08c4d21 / #3760 ("feat: add headless xarm room simulation").
Reproduce
git lfs pull -I "data/.lfs/xarm_grasp_sim.tar.gz"
# [7541ab8f...] Object does not exist on the server (404)
Equivalently, the LFS batch API (POST https://github.com/dimensionalOS/dimos.git/info/lfs/objects/batch) reports "Object does not exist on the server" for this oid, while sibling archives such as xarm7.tar.gz resolve fine.
Impact
xarm-room-simblueprint (dimos/robot/manipulators/xarm/blueprints/simulation.py,XARM_ROOM_SCENE_PATH = LfsPath("xarm_grasp_sim/scene.xml")) fails at runtime with "Failed to download LFS file"- Any consumer of the xArm grasp-sim scene package (e.g. eval suites referencing the tabletop scene) cannot run from a fresh clone
Possibly the object was pushed to a contributor fork's LFS store during #3760 and never made it into dimensionalOS/dimos. Re-pushing the original xarm_grasp_sim.tar.gz (2.3 MB) from whoever has the original file should fix it.
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 by checking the pointer for data/.lfs/xarm_grasp_sim.tar.gz and the xarm-room-sim entry in dimos/robot/manipulators/xarm/blueprints/simulation.py. Run git lfs pull -I "data/.lfs/xarm_grasp_sim.tar.gz" and verify the batch API response; done means the object is available from a fresh clone and the blueprint can load scene.xml.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100