harrypart commited on
Commit
04c0a6f
·
verified ·
1 Parent(s): 5a8b007

Disable truss-transfer range downloads: HF CDN now pins signed URLs to the resolving request's Range header, which 403s chunked range reuse

Browse files
Files changed (1) hide show
  1. truss/config_nvfp4_4gpu.yaml +6 -0
truss/config_nvfp4_4gpu.yaml CHANGED
@@ -51,6 +51,12 @@ model_cache:
51
  use_volume: true
52
 
53
  environment_variables:
 
 
 
 
 
 
54
  # NVFP4 is Blackwell-only and needs the modelopt_fp4 path plus two disable flags
55
  # (see start_server.sh). GLM5V_CKPT must match volume_folder above.
56
  GLM5V_CKPT: /app/model_cache/glm5v_nvfp4
 
51
  use_volume: true
52
 
53
  environment_variables:
54
+ # huggingface.co signs its CDN redirects for the exact Range header of the
55
+ # resolving request, so truss-transfer's range mode (probe bytes=0-0, reuse the
56
+ # URL for real chunks) gets 403s on every shard. Whole-file streaming avoids the
57
+ # pinning; 16 parallel files keep the 466GB transfer under ~10 minutes.
58
+ TRUSS_TRANSFER_USE_RANGE_DOWNLOAD: "0"
59
+ TRUSS_TRANSFER_NUM_WORKERS: "16"
60
  # NVFP4 is Blackwell-only and needs the modelopt_fp4 path plus two disable flags
61
  # (see start_server.sh). GLM5V_CKPT must match volume_folder above.
62
  GLM5V_CKPT: /app/model_cache/glm5v_nvfp4