Repository detail page is blank and throws errors when opened while the repo is still downloading

[yonasberhe23]

Setup

• Rancher version: Rancher v2.15-fd3d05f4c179b0fc8ad2dd8447775bee8c1bb254-head
• Rancher UI Extensions: Dashboard master 920680f
• Browser type & version:

Describe the bug
Navigating to the detail page of a repository while it is still in the downloading state (status not yet populated) results in a blank page and errors thrown in the browser console.

To Reproduce

1. Go to Apps > Repositories.
2. Click Add Repository and add a new repository.
3. Before the repo finishes downloading, click the repo name to open its detail page.

Result
Detail page renders blank. Console shows:

  TypeError: Cannot read properties of undefined (reading 'downloadTime')
      at get details (catalog.cattle.io.clusterrepo.js:229:36)

  TypeError: Cannot read properties of undefined (reading 'commit')
      at Proxy.l (catalog.cattle.io.clusterrepo.vue:32:29)

Expected Result
Detail page should render without errors while the repo is still downloading.

Screenshots

Screen.Recording.2026-05-07.at.4.18.29.PM.mov

Additional context
Please reenable e2e test checks when this is fixed

dashboard/cypress/e2e/tests/pages/manager/repositories.spec.ts

Lines 82 to 83 in efd1eb2

	// Enable check once the detail page issue is resolved https://github.com/rancher/dashboard/issues/17556
	// repositoriesPage.list().details(this.repoName, 2).click();

[github-actions]

🎯 Agentic Issue Triage

Summary: A TypeError crashes the repository detail page (Apps > Repositories) when a user navigates to it while the repository's status object is not yet populated (i.e., download still in progress). Two distinct access-on-undefined paths cause a blank page render.

---

📋 Root Cause Analysis

Two places unconditionally access status without null-guarding:

1. shell/models/catalog.cattle.io.clusterrepo.js ~line 229

   // get details()
   content: this.status.downloadTime,  // ❌ status is undefined during download

2. shell/detail/catalog.cattle.io.clusterrepo.vue ~line 32

   <span>{{ value.status.commit }}</span>  <!-- ❌ status is undefined during download -->

When the repo is in a transitioning/downloading state, the status subobject may not yet exist on the resource, causing both TypeError: Cannot read properties of undefined crashes that blank out the entire detail view.

🔧 Suggested Fix

Apply optional chaining / null-safe access:

shell/models/catalog.cattle.io.clusterrepo.js

// Before
content: this.status.downloadTime,
// After
content: this.status?.downloadTime,

shell/detail/catalog.cattle.io.clusterrepo.vue

<!-- Before -->
<span>{{ value.status.commit }}</span>
<!-- After -->
<span>{{ value.status?.commit }}</span>

Additionally, consider showing a loading/skeleton state or a friendly "Repository is still downloading..." message in the detail template when value.status is falsy, rather than rendering nothing.

🔁 Reproduction Steps

1. Navigate to Apps > Repositories.
2. Click Add Repository and submit a new (git-backed) repository.
3. Before the repo finishes downloading, click its name to open the detail page.
4. Observe blank page + console errors:
   • TypeError: Cannot read properties of undefined (reading 'downloadTime')
   • TypeError: Cannot read properties of undefined (reading 'commit')

🐛 Debugging Strategy

• Add a console log or breakpoint in get details() of the model and in the detail component's template render to confirm this.status / value.status is undefined at the time of navigation.
• Check whether the Steve store watcher updates the resource in place when status eventually arrives, or whether a manual refresh is required — if it does update reactively, the fix is straightforward optional chaining; if not, a watcher/polling mechanism may be needed.
• Verify the stateObj getter (also in the model) handles missing status — it already guards this.metadata?.state, so that path looks safe.

✅ Sub-tasks Checklist

• Add optional chaining in shell/models/catalog.cattle.io.clusterrepo.js → this.status?.downloadTime
• Add optional chaining / null guard in shell/detail/catalog.cattle.io.clusterrepo.vue → value.status?.commit
• Consider adding a loading/empty state in the detail template when status is absent
• Add or update unit tests for the get details() getter to cover the case where status is undefined
• Manually verify the detail page renders gracefully in the downloading state after the fix

📚 Relevant Resources

• Source: shell/models/catalog.cattle.io.clusterrepo.js
• Source: shell/detail/catalog.cattle.io.clusterrepo.vue
• [Vue.js conditional rendering — v-if for safe template guards]((vuejs.org/redacted)
• [MDN: Optional chaining (?.)]((developer.mozilla.org/redacted)

Note

🔒 Integrity filter blocked 1 item

The following item were blocked because they don't meet the GitHub integrity level.

• #17556 issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by Agentic Triage for issue #17556 · ● 341.2K · ◷