<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=476693) </details> <!--IssueSummary end--> <!--This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal <!--Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues.--> <!--Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section.--> <!--Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/--> In this [Issue](https://gitlab.com/gitlab-org/gitlab/-/issues/411836#summary) "Forking projects with large number of LFS files fail with no error message" [two improvements](https://gitlab.com/gitlab-org/gitlab/-/issues/411836#note_1642551080) 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](https://gitlab.zendesk.com/agent/tickets/546052) 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: ```plaintext "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. {width=631 height=136}