search

51Degrees / Device-Detection

THE Fastest and most Accurate device detection for C / PHP / Perl / Python and Node.js - professionally maintained device data
https://51degrees.com/device-detection
Other
112 stars 46 forks source link

Error downloading object: 20000 Evidence Records.yml #58

Closed Radi-Mortada closed 1 year ago

Radi-Mortada commented 1 year ago

Cloning fails because the LFS bandwidth quota has been exceeded.

➜  repos git clone https://github.com/51Degrees/device-detection-data
Cloning into 'device-detection-data'...
remote: Enumerating objects: 145, done.
remote: Counting objects: 100% (12/12), done.
remote: Compressing objects: 100% (11/11), done.
remote: Total 145 (delta 3), reused 7 (delta 1), pack-reused 133
Receiving objects: 100% (145/145), 27.28 KiB | 473.00 KiB/s, done.
Resolving deltas: 100% (41/41), done.
Downloading 20000 Evidence Records.yml (4.2 MB)
Error downloading object: 20000 Evidence Records.yml (ed53f4f): Smudge error: Error downloading 20000 Evidence Records.yml (ed53f4fdccc763e143dfeaacfbb9652583ceb277bd791bd7543df7318ca647a1): batch response: This repository is over its data quota. Account responsible for LFS bandwidth should purchase more data packs to restore access.

Errors logged to '/Users/radi/Documents/repos/device-detection-data/.git/lfs/logs/20230920T125143.503175.log'.
Use `git lfs logs last` to view the log.
error: external filter 'git-lfs filter-process' failed
fatal: 20000 Evidence Records.yml: smudge filter lfs failed
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'

Since it happened other times (I opened two other issues), may I suggest, if possible, to set up an automated system that notifies automatically when the quota is exceeded? Thanks.

kirstin51D commented 1 year ago

Hi! Thanks for raising this. We were aware of the exceeded quota, and were waiting for GitHub to allocated the additional storage. I can confirm this was allocated this morning, so this problem shouldn't be present. Noted regarding your suggestion of an automated system. We're exploring a few other avenues to prevent this in future. Thanks!