I ran a search across a legacy codebase for a particular string - I was looking to see where a particular value was written and read. It found a file with hits in, but 'show all matches' clearly omits some within the file - when I go to the full source of the file and search within the page I get the extra hits.
I assumed this was buggy behaviour. It's a legacy file over 4000 lines long and taking up 220k so I wondered if there was some limit that truncated the file before indexing it?
The bit about only returning 3 chunks per file in the response and comments here might be the explanation:
Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events