You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
According to #195, max_upload_size can be set in Cargo.toml to specify crate's max size. However, in 94e3e1b, which seems like some kind of daily refactor commit, this field is set to None.
To Reproduce
Set max_upload_size to some value larger than 10MiB and upload a crate bigger than 10MiB.
Expected behavior
Crate upload normally.
Question
Actually, I' m not sure if this is on purpose. If team don't want this filed to be set, this field should just be removed.
The text was updated successfully, but these errors were encountered:
max_upload_size can be set in Cargo.toml to specify crate's max size
I'm not sure where in #195 you've read that, but I don't think that's how it works.
The max_upload_size column in the database is meant for increasing the regular 10MB upload limit on a case-by-case basis. The column value is manually adjusted in the database, which is also why it's usually just set to None for new crates.
max_upload_size is set manually in the database on a per-crate basis after requesting an increase over the default limit. max_upload_size is used during publish and should not be removed.
Describe the bug
According to #195,
max_upload_size
can be set in Cargo.toml to specify crate's max size. However, in 94e3e1b, which seems like some kind of daily refactor commit, this field is set toNone
.To Reproduce
Set
max_upload_size
to some value larger than 10MiB and upload a crate bigger than 10MiB.Expected behavior
Crate upload normally.
Question
Actually, I' m not sure if this is on purpose. If team don't want this filed to be set, this field should just be removed.
The text was updated successfully, but these errors were encountered: