Skip to content

GitLab

  • Menu
    • Projects Groups Snippets
      Help
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
  • #5729

Closed
Open
Created 11 years ago by Administrator@rootOwner
  • New issue

  • Report abuse

  • New issue

  • Report abuse

notifications page doesn't work

Closed

notifications page doesn't work

Created by: leventyalcin

After 6.3 update Notifications page started to response with 500

Started GET "/profile/notifications" for 127.0.0.1 at 2013-11-29 06:56:27 -0800
Processing by Profiles::NotificationsController#show as HTML
  Rendered profiles/notifications/_settings.html.haml (4.7ms)
  Rendered profiles/notifications/_settings.html.haml (3.8ms)
  Rendered profiles/notifications/_settings.html.haml (5.4ms)
  Rendered profiles/notifications/_settings.html.haml (4.6ms)
  Rendered profiles/notifications/_settings.html.haml (4.4ms)
  Rendered profiles/notifications/_settings.html.haml (2.1ms)
  Rendered profiles/notifications/show.html.haml within layouts/profile (33.5ms)
Completed 500 Internal Server Error in 38.3ms

ActionView::Template::Error (undefined method `name' for nil:NilClass):
    7:         - if membership.kind_of? UsersGroup
    8:           = link_to membership.group.name, membership.group
    9:         - else
    10:           = link_to_project(membership.project)
    11:     .span7
    12:       = form_tag profile_notifications_path, method: :put, remote: true, class: 'update-notifications' do
    13:         = hidden_field_tag :notification_type, type, id: dom_id(membership, 'notification_type')
  app/helpers/projects_helper.rb:8:in `block in link_to_project'
  app/helpers/projects_helper.rb:7:in `link_to_project'
  app/views/profiles/notifications/_settings.html.haml:10:in `_app_views_profiles_notifications__settings_html_haml___1295931723471331615_69975272788560'
  app/views/profiles/notifications/show.html.haml:58:in `block in _app_views_profiles_notifications_show_html_haml__2649154071091061897_69975269733960'
  app/views/profiles/notifications/show.html.haml:56:in `_app_views_profiles_notifications_show_html_haml__2649154071091061897_69975269733960'
  app/controllers/application_controller.rb:54:in `set_current_user_for_thread'
System information
System:     Ubuntu 12.04
Current User:   git
Using RVM:  no
Ruby Version:   2.0.0p247
Gem Version:    2.0.3
Bundler Version:1.3.5
Rake Version:   10.1.0

GitLab information
Version:    6.3.0
Revision:   b56f85c
Directory:  /home/git/gitlab
DB Adapter: mysql2
URL:        http://git.sj.koding.com
HTTP Clone URL: http://git.sj.koding.com/some-project.git
SSH Clone URL:  git@git.sj.koding.com:some-project.git
Using LDAP: no
Using Omniauth: no

GitLab Shell
Version:    1.7.9
Repositories:   /home/git/repositories/
Hooks:      /home/git/gitlab-shell/hooks/
Git:        /usr/bin/git
Checking Environment ...
Git configured for git user? ... yes
Has python2? ... yes
python2 is supported version? ... yes
Checking Environment ... Finished

Checking GitLab Shell ...
GitLab Shell version >= 1.7.9 ? ... OK (1.7.9)
Repo base directory exists? ... yes
Repo base directory is a symlink? ... no
Repo base owned by git:git? ... yes
Repo base access is drwxrws---? ... yes
update hook up-to-date? ... yes
update hooks in repos are links: ...
Running /home/git/gitlab-shell/bin/check
Check GitLab API access: OK
Check directories and files:
    /home/git/repositories: OK
    /home/git/.ssh/authorized_keys: OK
    /usr/bin/redis-cli: OK
gitlab-shell self-check successful
Checking GitLab Shell ... Finished

Checking Sidekiq ...
Running? ... yes
Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished

Checking GitLab ...
Database config exists? ... yes
Database is SQLite ... no
All migrations up? ... yes
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Init script exists? ... yes
Init script up-to-date? ... yes
projects have namespace: ...
Redis version >= 2.0.0? ... yes
Your git bin path is "/usr/bin/git"
Git version >= 1.7.10 ? ... yes (1.7.10)
Checking GitLab ... Finished

Linked issues
...

    Related merge requests

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: bspindler-shopzilla

      This was reported in Issue #4852 (closed), you'll find a workaround posted there that should at least get it working again for now.

      By Administrator on 2013-12-06T02:56:17 (imported from GitLab project)

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: leventyalcin

      @bspindler-shopzilla ah sorry I couldn't see it before I open that issue.

      at the same time It solved issue #5556 (closed) too

      By Administrator on 2013-12-06T10:55:49 (imported from GitLab project)

    • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
    Please register or sign in to reply
    0 Assignees
    Assign to
    Milestone
    No milestone
    None
    None
    Time tracking
    Due date
    None
    None
    0
    Labels
    None
    Assign labels
    • No matching results
    • Manage project labels
    Confidentiality
    Not confidential

    You are going to turn on confidentiality. Only team members with at least Reporter access will be able to see and leave comments on the issue.

    Lock issue
    Unlocked
    participants
    Reference:

    Menu

    Projects Groups Snippets
    Help