500 error when following unsubscribe link in epic "new comment" notification email

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

I received the following notification email:


Re: GitLab.org | Support keyless signing when CI config is located outside of the project (#11637 (closed))

Tim Knight commented on a discussion:

@nrosandich with help from Kate Grechishkina on support we've got it working again, not exactly sure how the claims had gone wrong, but adding the -d to cosign -d ${DIGEST} and fixing something in one of the Dockerfiles (can't see how that would related) seems to have fixed the issue


Reply to this email directly or view it on GitLab.
You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread · Manage all notifications · Help


Clicking the Unsubscribe link (https://gitlab.com/-/sent_notifications/REDACTED/unsubscribe) results in a 500 error:

json.exception.class      ActionController::UrlGenerationError

json.exception.message
No route matches {:action=>"show", :controller=>"projects/issues", :id=>#<Issue id:146108417 gitlab-org#11637>, :namespace_id=>nil, :project_id=>nil}, possible unmatched constraints: [:namespace_id, :project_id]

Steps to reproduce

Subscribe to &11637 for update notifications, have someone add a comment to the epic, click on the Unsubscribe link in the notification email you receive.

Example Project

What is the current bug behavior?

Unsubscribe link errors

What is the expected correct behavior?

User should be unsubscribed from notifications about changes on the epic.

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of: \\\`sudo gitlab-rake gitlab:env:info\\\`) (For installations from source run and paste the output of: \\\`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production\\\`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of: \`sudo gitlab-rake gitlab:check SANITIZE=true\`) (For installations from source run and paste the output of: \`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true\`) (we will only investigate if the tests are passing)

Possible fixes

Edited by 🤖 GitLab Bot 🤖