microsoft / microsoft/SPTAG

Unable to download vectors_9.bin and vectors_12.bin using git lfs pull

Open
#412 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
5k
Forks
622
Avg merge
8h 37m
Merged PRs (30d)
5

Description

Describe the bug:
I am unable to download vectors_9.bin and vectors_12.bin files using git lfs pull. Despite no initial error message when attempting the command, the files fail to download, and an error message appears indicating a timeout issue.

To Reproduce:
Steps to reproduce the behavior:
$ git lfs pull

Expected behavior:
I expected the git lfs pull command to download all vector files, including vectors_9.bin and vectors_12.bin.

Desktop (please complete the following information):
OS: Ubuntu 22.04 (5.15.0-33-generic)
Browser: N/A
Version: Not applicable to this issue

Additional context:
Git LFS version: git-lfs/3.0.2 (GitHub; linux amd64; go 1.18.1)
Error message encountered:

Downloading LFS objects: 0% (0/2), 4 KB | 0 B/s
cannot write data to tempfile "/dataset/SPTAG/.git/lfs/incomplete/f50e029134bc17703be6bc69748953ef2c9bb81b29d2286bda4d006d8bfce34c2743671370": LFS: read tcp 172.16.135.193:34564->185.199.108.154:443: i/o timeout
error: failed to fetch some objects from 'https://github.com/microsoft/SPTAG.git/info/lfs'

This issue occurs specifically for vectors_9.bin and vectors_12.bin files, other files are downloaded as expected.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing git lfs pull on Ubuntu 22.04 and inspect the timeout while downloading vectors_9.bin and vectors_12.bin. Compare those downloads with the vector files that succeed; done means identifying a repository or Git LFS cause and recording a verified resolution, since no source file or test is named.

Written by the indexing model from the issue text.

Assessment

Tech stack
git
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.