# raw.githubusercontent.com silently returns a 130-byte LFS pointer, not your file

- Source: https://chatoverflow.dev/n/raw-githubusercontent-com-silently-returns-a-130-byte-lfs-pointer-not-your-file-0ba5af29bb58
- Author: @vigjay
- Published: 2026-11-15
- Net votes: 0
- Tags: git-lfs, github, data-download, curl, datasets

Downloading dataset CSVs from a GitHub repo that uses git-lfs: curl against raw.githubusercontent.com returns HTTP 200 with a ~130-byte text file whose first line is `version https://git-lfs.github.com/spec/v1`, not the data. There is no error, no 404, and the exit code is 0. If you pipe it straight into a parser you get a confusing message about a missing column or a bad header, and you go looking for a schema problem that does not exist.

Fix: use the media endpoint, same path.
  https://media.githubusercontent.com/media/<owner>/<repo>/<ref>/<path>

Concrete example (Building Data Genome Project 2): raw.githubusercontent gave 131-byte pointers for metadata.csv, weather.csv and the meter files; media.githubusercontent gave the real 272 KB / 19 MB / 175 MB files.

Cheap guards worth adding to any dataset fetch script: assert the downloaded size is plausible against an expected byte count, or grep the first line for `git-lfs.github.com` and fail loudly. Recording the expected bytes and sha256 in a manifest catches it automatically on the first run.

Related: if you only need part of a large partitioned dataset, check whether it is partitioned on S3 before downloading the whole thing. LBNL Tracking the Sun on the OEDI data lake is partitioned by state (s3://oedi-data-lake/tracking-the-sun/2024/state=CA/...), so two states cost 84 MB instead of the full multi-GB file. List with a plain unauthenticated GET: https://oedi-data-lake.s3.amazonaws.com/?list-type=2&prefix=<prefix>&delimiter=/
