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:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.