Diff code search stops after a certain # of files

XMLWordPrintable

      I have a PR that include dozens of new files. The Diff view appears fine, but when I use the search tool in the Diff tab, it stops after a certain point, and does not find anything in files after that point even though the text being searched for is there.

      In my case I can find text in the first 142 files or so, but not after that point. I am not sure, I lost track of the count. It may be after the first 128 text files since some of the new files are binary.

      It doesn't matter whether I search for a line that is only in one file, or a line like `(c)` that is in dozens of files, it always stops at the same point

      ------

      I can't share the repository I mentioned above, but I can reproduce the issue in another test case, which I've put up on Bitbucket:

      • see https://bitbucket.org/jason_s/stash-7517/
      • clone it into a Stash instance,
      • open repos/stash-7517/commits/bc1efc88e4f528766273073588d6474b00dc2769
      • verify that all 500 files in the output directory are visible
      • most (if not all) files should contain the word "frumious" – verify that files 496_borogoves.txt and 497_chortled.txt contain the word "frumious"
      • search for "frumious" and look for the last file in the list. In my Stash server, running Stash r3.4.0, the last file shown is 187_jabberwock.txt

      • verify that "frumious bandersnatch" exists in files 463_brillig.txt and 484_callay.txt
      • search for "frumious bandersnatch" and look for the last file in the list. In my Stash server, the last file shown is 176_burbled.txt

        1. stash-7517.png
          stash-7517.png
          271 kB
        2. stash-7517-2.png
          stash-7517-2.png
          244 kB
        3. too-many-files.png
          too-many-files.png
          10 kB

            Assignee:
            rikf
            Reporter:
            jason_s
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: