[go: up one dir, main page]

Skip to content

Display an error message when the limit of 100,000 limit setting is hit

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Proposal

In this Issue "Forking projects with large number of LFS files fail with no error message" two improvements were suggested:

Display an error message when the limit of 100,000 limit setting

Allow users to increase the limit via an application setting

The first one does not seem like it was explored, this issue is to track work on that.

A customer faced this issue when forking a project with a large amount of LFS objects.

The UI error is not clear, and this needed digging in the logs and code to track. The error in the logs is the following:

"error_message": "Unable to fork project 12345 for repository 
@hashed/11/22/encoded-path-> 
@hashed/33/44/encoded-new-path: Source project has too many LFS objects"

It stays as below for a long while but the errors do record that the issue is with size.

This should also reflect on the UI.

Screenshot 2024-08-02 at 13.04.25.png

Edited by 🤖 GitLab Bot 🤖