1. 28 Dec, 2022 1 commit
  2. 22 Dec, 2022 1 commit
  3. 21 Dec, 2022 1 commit
  4. 13 Dec, 2022 1 commit
  5. 12 Dec, 2022 1 commit
  6. 10 Dec, 2022 1 commit
  7. 04 Dec, 2022 1 commit
  8. 20 Nov, 2022 1 commit
  9. 13 Nov, 2022 1 commit
  10. 10 Nov, 2022 1 commit
  11. 09 Nov, 2022 3 commits
  12. 30 Oct, 2022 1 commit
  13. 28 Oct, 2022 1 commit
  14. 27 Oct, 2022 1 commit
  15. 25 Oct, 2022 2 commits
  16. 24 Oct, 2022 1 commit
  17. 17 Oct, 2022 2 commits
  18. 16 Oct, 2022 1 commit
  19. 10 Oct, 2022 1 commit
  20. 08 Oct, 2022 2 commits
  21. 07 Oct, 2022 1 commit
  22. 26 Sep, 2022 1 commit
  23. 22 Sep, 2022 1 commit
    • wxiaoguang's avatar
      Use Go 1.19 fmt for Gitea 1.17, sync emoji data (#21239) · 20c135cd
      wxiaoguang authored
      The images used by Gitea's drone pipeline were upgraded to Go 1.19.x
      It causes the lint fails because Go 1.19 uses new code format.
      
      This PR partially backport #20758 (including the emoji-data sync),
      partially fix the format manually.
      20c135cd
  24. 20 Sep, 2022 1 commit
  25. 17 Sep, 2022 1 commit
  26. 08 Sep, 2022 1 commit
  27. 06 Sep, 2022 1 commit
    • zeripath's avatar
      Fix hard-coded timeout and error panic in API archive download endpoint (#20925) (#21051) · 06f968d6
      zeripath authored
      
      Backport #20925
      
      This commit updates the `GET /api/v1/repos/{owner}/{repo}/archive/{archive}`
      endpoint which prior to this PR had a couple of issues.
      
      1. The endpoint had a hard-coded 20s timeout for the archiver to complete after
         which a 500 (Internal Server Error) was returned to client. For a scripted
         API client there was no clear way of telling that the operation timed out and
         that it should retry.
      
      2. Whenever the timeout _did occur_, the code used to panic. This was caused by
         the API endpoint "delegating" to the same call path as the web, which uses a
         slightly different way of reporting errors (HTML rather than JSON for
         example).
      
         More specifically, `api/v1/repo/file.go#GetArchive` just called through to
         `web/repo/repo.go#Download`, which expects the `Context` to have a `Render`
         field set, but which is `nil` for API calls. Hence, a `nil` pointer error.
      
      The code addresses (1) by dropping the hard-coded timeout. Instead, any
      timeout/cancelation on the incoming `Context` is used.
      
      The code addresses (2) by updating the API endpoint to use a separate call path
      for the API-triggered archive download. This avoids producing HTML-errors on
      errors (it now produces JSON errors).
      Signed-off-by: default avatarPeter Gardfjäll <peter.gardfjall.work@gmail.com>
      Signed-off-by: default avatarPeter Gardfjäll <peter.gardfjall.work@gmail.com>
      Signed-off-by: default avatarAndrew Thornton <art27@cantab.net>
      Co-authored-by: default avatarPeter Gardfjäll <peter.gardfjall.work@gmail.com>
      Co-authored-by: default avatarLunny Xiao <xiaolunwen@gmail.com>
      06f968d6
  28. 04 Sep, 2022 3 commits
  29. 03 Sep, 2022 1 commit
  30. 25 Aug, 2022 1 commit
  31. 23 Aug, 2022 2 commits
  32. 22 Aug, 2022 1 commit
    • zeripath's avatar
      Pad GPG Key ID with preceding zeroes (#20878) (#20885) · bf41958c
      zeripath authored
      
      Backport #20878
      
      The go crypto library does not pad keyIDs to 16 characters with preceding zeroes. This
      is a somewhat confusing thing for most users who expect these to have preceding zeroes.
      
      This PR prefixes any sub 16 length KeyID with preceding zeroes and removes preceding
      zeroes from KeyIDs inputted on the API.
      
      Fix #20876
      Signed-off-by: default avatarAndrew Thornton <art27@cantab.net>
      bf41958c