Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to view project triggers page when last selected branch was deleted #8580

Closed
hnrkndrssn opened this issue Jan 24, 2024 · 2 comments
Closed
Assignees
Labels
kind/bug This issue represents a verified problem we are committed to solving

Comments

@hnrkndrssn
Copy link

hnrkndrssn commented Jan 24, 2024

Severity

Not blocking

Version

2024.1.8803

Latest Version

I could reproduce the problem in the latest build

What happened?

If the branch you last had selected is deleted and you try to access the project triggers page it will fail with a An unexpected error occurred in Octopus v2024.1.8803: Cannot read properties of null (reading 'Links') error and the page will not show.

Reproduction

  1. Create a version controlled project
  2. Create a new branch and switch to it in the UI
  3. Delete the new branch and wait for the git cache to be invalidated
  4. Access the project triggers page
  5. Observer error on page and triggers page not loading

Error and Stacktrace

There is a call to the project `summary` endpoint which is returning a 404.

Request URL: https://azure-cockatoo.armada.octopushq.com/api/Spaces-1/projects/Projects-1//summary
Request Method: GET
Status Code: 404 Not Found

More Information

We had a similar issue a while back which manifested slightly differently.

Workaround

Go to a version controlled page and switch to a branch that exists.

@hnrkndrssn hnrkndrssn added the kind/bug This issue represents a verified problem we are committed to solving label Jan 24, 2024
@octoreleasebot
Copy link

Release Note: Fix an unexpected error that occurs on the triggers page if a branch has been deleted.

@Octobob
Copy link
Member

Octobob commented May 16, 2024

🎉 The fix for this issue has been released in:

Release stream Release
2024.2 2024.2.6087
2024.3+ all releases

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

No branches or pull requests

4 participants