Error: Repository storage limit reached (Max: 1 GB)

Beginners
1

Hi
I cloned a working space ,but when I try modifying the code and commit to main, I receive this error. My general space is ok, just 59GB used. Also, even just factory reset or restart of the space doesn’t work, it stuck in endless building process, without any output on log file . Any ideas ?
Thanks for reading

5 Likes
2

I am having exactly same issue.
I tried with hubapi also, but same.
Any fix for this?

1 Like
3

The build stack is probably the same as this. Also, the free CPU space was probably 2 cores, 16GB RAM, 0GB VRAM, and 50GB SSD…

4

I have the same issue too!
Today, I tried to edit my space code, but cannot commit new updates due to storage limit.
Any solution for this? I am using ZeroGPU.

1 Like
5

I am using ZeroGPU.

It’s definitely a bug. The storage capacity of the Zero GPU space is so large that it’s impossible to use it all, so there is a very high possibility that the error message is wrong.

6

Experiencing this too, yesterday was able to commit changes to main.

1 Like
7

I reported it to HF Discord. I just reported it.

1 Like
8

I wonder if the processing for the capacity limit that suddenly appeared today is buggy.

9

Please can someone from HuggingFace support fix this issue as soon as posible? It is blocking some important updates we need at the Space.

2 Likes
10

Same Problem here

1 Like
11

Same thing here, i assume a bug with new storage limits change yesterday, even tho repo is under 1 GB

1 Like
12

This has been fixed for me now thanks Huggingface :slight_smile:

1 Like
13

I’m having the same issue. How did you get your fixed?

1 Like
14

Also having the same issue still.

1 Like
16

Even bought the pro sub.
still facing the same issue. what can you even do with 1GB

2 Likes
17

We can put data in the Public model repo or dataset repo for free, even if it’s several terabytes, so I think they want us to load it from there when the Spaces program is started.
Downloading to Spaces is very fast.
However, there are some troublesome things when we bring in the github sample as it is.:sweat_smile:

Anyway, it seems like a bug that a 1GB error occurs even though the file has not reached 1GB. It seems like it would be better not to put large files in the git of Spaces in the future.