Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #2951

Closed
Open
Created Feb 10, 2013 by Administrator@rootOwner

Internal API `allowed` fails from Gitlab-shell

Created by: davispuh

I just tried newest gitlab master branch with gitlab-shell and when I tried fetch or push using ssh it failed with

Started GET "/api/v3/internal/allowed?key_id=3&action=git-receive-pack&ref=_any&project=/somegroup/some-project" for 2a00:f48:1025:feed:b00b:feed:b90c:fc82 at 2013-02-10 14:26:58 +0000

NoMethodError (undefined method `protected_branch?' for nil:NilClass):
  lib/api/internal.rb:22:in `block (2 levels) in <class:Internal>'

it's because in lib/api/internal.rb Project.find_with_namespace(params[:project]) returns nil, I didn't looked further..

Assignee
Assign to
Time tracking