onnx / onnx/models

Resnet50-v1-12* models and shufflenet-v1-12* models aren't appropriately included for LFS handling

Open
#482 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Jupyter Notebook
Stars
9.8k
Forks
1.6k
PR merge metrics
No merged PRs in 30d

Description

Bug Report

Which model does this pertain to?

The models shown in the below clone:

(base) bmesser:~$ git clone --depth 1 https://github.com/onnx/models.git
Cloning into 'models'...
remote: Enumerating objects: 498, done.
remote: Counting objects: 100% (498/498), done.
remote: Compressing objects: 100% (475/475), done.
remote: Total 498 (delta 20), reused 400 (delta 15), pack-reused 0
Receiving objects: 100% (498/498), 256.58 MiB | 18.33 MiB/s, done.
Resolving deltas: 100% (20/20), done.
Updating files: 100% (400/400), done.
Encountered 8 file(s) that should have been pointers, but weren't:
        vision/classification/resnet/model/resnet50-v1-12-int8.onnx
        vision/classification/resnet/model/resnet50-v1-12-int8.tar.gz
        vision/classification/resnet/model/resnet50-v1-12.onnx
        vision/classification/resnet/model/resnet50-v1-12.tar.gz
        vision/classification/shufflenet/model/shufflenet-v2-12-int8.onnx
        vision/classification/shufflenet/model/shufflenet-v2-12-int8.tar.gz
        vision/classification/shufflenet/model/shufflenet-v2-12.onnx
        vision/classification/shufflenet/model/shufflenet-v2-12.tar.gz
Describe the bug

Instead of being properly included inside the git lfs, these models are coming down as part of the git clone itself.

Reproduction instructions

System Information

This happens on a RHEL 8.4 LoZ server and a Ubuntu 20.04 WSL2 instance. The git clone shown above should be sufficient to recreate the handling.

Notes

No additional notes needed at this time. My plan is to come back through and clean this up myself. It should be a simple adjustment.

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 with the listed model paths under vision/classification/resnet/model and vision/classification/shufflenet/model, then inspect the repository's Git LFS configuration. Reproduce the problem with the shallow clone command; done when the affected model files are handled as LFS pointers and the clone no longer reports them as non-pointers.

Written by the indexing model from the issue text.

Assessment

Tech stack
git
Domain
machine-learning, tooling
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.