Issue Summary

When filtering files in the source browser, it fails if the repository's file tree is too large to fetch.

Steps to Reproduce

1. Open a repository with a high number of files (200k+)
2. Search for a file in the main branch.
3. The search will timeout and no file is returned.

Expected Results

To return the searched file in the branch. Additionally, when files are filtered within the actual path folder where they are located, and we click on a file from the search results, the expected behavior is to redirect us to the URL https://bitbucket.org/workspace/repo/src/master/<path_to_file_or_directory>.

Actual Results

If the repository is huge (in size or in file number) the file is not searched even if it exists in the Child/subdirectories of the searched branch. Although when files are filtered within the actual path folder where the files are located, the search results display the files that match the text search. However, when we click on a file from the search results, it redirects us to the URL https://bitbucket.org/workspace/repo/src/master/<file_or_directory> instead of the expected URL format: https://bitbucket.org/workspace/repo/src/master/<path_to_file_or_directory>.

Workaround

The only workaround at the moment is to browse the repository on the local filesystem, find the path of the file or directory that you would like to view in the Bitbucket UI, and update the URL manually.
Eg.:
https://bitbucket.org/workspace/repo/src/<ref>/<path_to_file_or_directory>