Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • G gitlab-ce
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nexedi
  • gitlab-ce
  • Repository

Switch branch/tag
  • gitlab-ce
  • spec
  • requests
  • api
  • projects_spec.rb
Find file BlameHistoryPermalink
  • Stan Hu's avatar
    Log message when upload via API exceeds limit · ba5089fa
    Stan Hu authored Mar 29, 2021
    Since Workhorse started accelerating attachments in the upload API
    (https://gitlab.com/gitlab-org/gitlab/-/merge_requests/57250), the
    `content_length` log in `api_json.log` no longer holds the actual bytes
    used by the uploaded file. It now reports the number of bytes from the
    Workhorse JSON metadata.
    
    In order to determine which projects might be exceeding this limit, we
    log a JSON warning that will make it easier to fill in the allow list
    for https://gitlab.com/gitlab-org/gitlab/-/issues/325788.
    ba5089fa

Replace projects_spec.rb

Attach a file by drag & drop or click to upload


Cancel
GitLab will create a branch in your fork and start a merge request.
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7