Two setup-config inaccuracies trip up new (UV) users:
GITLAB_TOKEN sits in the top "Credentials" block as if required, but it's Docker-only (env/docker-ops.sh registry login; skipped when absent). A live WANDB_ENTITY placeholder also caused an "entity not found" 404 (username ≠ entity; blank = account default).
LOCAL_DATA_PATH/DATA_PATH is labeled as holding target_data/, but shipped targets use repo-relative target_path:; $DATA_PATH is only a fallback (binder_eval_utils.py:256). Design needs no real DATA_PATH.
Severity: Low · Status: fixed in .env_example; upstream docs open
Steps to reproduce
- Follow the setup docs / fill
.env as written, on the UV runtime.
- → users think a GITLAB_TOKEN is required; the entity placeholder 404s W&B; users think a real
DATA_PATH is required just to run design.
Fix
Mark GITLAB_TOKEN Docker-only, comment out WANDB_ENTITY, and clarify DATA_PATH is a training/fallback path. (Done locally in .env_example.)
Environment
NVIDIA A100 80GB PCIe · driver 565.57.01 · CUDA 12.7 · repo branch dev @ 916eaae · UV runtime.
Two setup-config inaccuracies trip up new (UV) users:
GITLAB_TOKENsits in the top "Credentials" block as if required, but it's Docker-only (env/docker-ops.shregistry login; skipped when absent). A liveWANDB_ENTITYplaceholder also caused an "entity not found" 404 (username ≠ entity; blank = account default).LOCAL_DATA_PATH/DATA_PATHis labeled as holdingtarget_data/, but shipped targets use repo-relativetarget_path:;$DATA_PATHis only a fallback (binder_eval_utils.py:256). Design needs no realDATA_PATH.Severity: Low · Status: fixed in
.env_example; upstream docs openSteps to reproduce
.envas written, on the UV runtime.DATA_PATHis required just to run design.Fix
Mark
GITLAB_TOKENDocker-only, comment outWANDB_ENTITY, and clarifyDATA_PATHis a training/fallback path. (Done locally in.env_example.)Environment
NVIDIA A100 80GB PCIe · driver 565.57.01 · CUDA 12.7 · repo branch
dev@916eaae· UV runtime.