1. 06 Aug, 2020 2 commits
  2. 31 Jul, 2020 1 commit
  3. 30 Jul, 2020 1 commit
  4. 24 Jul, 2020 1 commit
  5. 23 Jul, 2020 1 commit
  6. 16 Jul, 2020 4 commits
  7. 15 Jul, 2020 2 commits
    • Jacob Vosmaer's avatar
      Merge branch '217392-read-references' into 'master' · ce696bcf
      Jacob Vosmaer authored
      Read and parse LSIF references
      
      See merge request gitlab-org/gitlab-workhorse!524
      ce696bcf
    • Patrick Bajao's avatar
      Read and parse LSIF references · 978671ce
      Patrick Bajao authored
      In order to be able to "Find references" of a given range or
      definition, we need to be able to read `references` items from
      the LSIF file.
      
      This will then be written to the JSON file for each range via
      `references` property.
      
      The property will look something like:
      
      ```
      "references": [
        {
          "path": "main.go#L7"
        }
      ]
      ```
      
      Each reference will be an object with `path` property. The `path`
      property will point to the exact line where it is being used.
      
      This is currently behind a feature flag (`code_navigation_references`)
      which will set `ProcessLsifReferences` header to `true` when
      enabled. If `false`, the `references` won't be read and generated.
      978671ce
  8. 14 Jul, 2020 3 commits
  9. 13 Jul, 2020 3 commits
  10. 03 Jul, 2020 3 commits
  11. 25 Jun, 2020 2 commits
  12. 17 Jun, 2020 4 commits
  13. 15 Jun, 2020 2 commits
  14. 11 Jun, 2020 4 commits
  15. 09 Jun, 2020 2 commits
  16. 04 Jun, 2020 2 commits
  17. 03 Jun, 2020 2 commits
  18. 02 Jun, 2020 1 commit
    • Nick Thomas's avatar
      Test the behaviour of SendURL with less-common upstreams · c21c2cbf
      Nick Thomas authored
      Two cases in particular, lacking a `Content-Type`,  gave us trouble:
      
      * Transfer-Encoding: chunked
      * No content-type and no transfer-encoding
      
      Both of these are permitted by the HTTP RFC (cases 3 and 7), and we
      can talk to arbitrary HTTP servers via sendurl, so it's imperative that
      we handle them correctly. This commit adds tests for both cases.
      
      Responses of the latter type are transparently converted to responses
      of the former type. This is an automatic behaviour of the Go stdlib,
      which doesn't really support making the second type of response
      directly. Since Transfer-Encoding is a hop-by-hop header, this type of
      encoding is extremely common, and we're still streaming, instead of
      accumulating, the data, I think this is acceptable.
      c21c2cbf