Bug: Git Material API getting timed out while saving existing git repository

[tayalrishabh96]

📜 Description

It bugs out while saving existing git repo if shallow cloning is enabled and enable_file_stats is set to true. The corresponding api call /orchestrator/app/material takes extensively longer time even if repo size is quite small and sometimes gets timed out.

👟 Reproduction steps

1. Make sure shallow cloning is enabled and enable_file_stats is true in orchestrator configMap.
2. Go to git repository section in app configurations.
3. Try saving existing git repo, here /orchestrator/app/material api will either get timed out or will take extensive amount of time.

👍 Expected behavior

This api doesn't validate if repository exists or not as putting garbage will get saved too then this api should get executed within milliseconds.

👎 Actual Behavior

It takes extensive amount of time if shallow cloning and file_stats is enabled

☸ Kubernetes version

NA

Cloud provider

NA

🌍 Browser

Chrome

🧱 Your Environment

NA

✅ Proposed Solution

NA

👀 Have you spent some time to check if this issue has been raised before?

• [X] I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

• [X] I have read the Code of Conduct

AB#9764