Skip to content

Issues board lists issues with unloaded dependencies as Blocked, with a green Open icon #266

Closed

Description

@tannerpolley

Problem

On the Issues roadmap for tannerpolley/ePC-SAFT, pingdotgg#948, pingdotgg#868 and pingdotgg#860 sit under Blocked with "Dependencies unavailable" and a green Open circle. GitHub says none is blocked (checked 2026-10-31 with GraphQL blockedBy): pingdotgg#948 has no blockers, pingdotgg#868's only blocker pingdotgg#855 is closed, and pingdotgg#860's five blockers (pingdotgg#861–pingdotgg#864, pingdotgg#869) are all closed.

Two defects:

  1. Data: the relationship read fails or comes back partial for this repository, so relationshipsComplete === false or blockedBy === undefined. Find out why (server side: apps/server/src/issues/IssueProjects.ts and IssueGitHubHost.ts, plus the server trace for issue list reads of ePC-SAFT) and fix the cause.
  2. Display: issueRoadmap.logic.ts files unknown dependencies under Blocked, but issueProgress in IssueStateIcon.tsx returns open for them, so a row under Blocked shows the Open icon. An issue whose dependencies are unknown must not show as Open under Blocked: its icon and section have to agree, and the row should say the dependencies are unknown rather than look blocked.

Done when

Activity

  1. tannerpolley commented on Oct 31, 2026

    @tannerpolley
    OwnerAuthor

    T3 Code status: Unavailable

    Issue: #266 Issues board lists issues with unloaded dependencies as Blocked, with a green Open icon

    Thread: thread:delegated-task:command%3Amcp%3A66d39c35-d3cf-4d02-bb35-a21c95b55dac%3Adelegate-task%3Aissue-266-impl

    Model: gpt-6.1-sol

    Branch: issue-266-issues-board-lists-issues-with-unloaded

    Updated: 2026-11-13T05:10:21.548Z

  2. tannerpolley commented on Oct 31, 2026

    @tannerpolley
    OwnerAuthor

    T3 Code closeout: done

    Issue: #266 Issues board lists issues with unloaded dependencies as Blocked, with a green Open icon
    Thread: thread:delegated-task:command%3Amcp%3A66d39c35-d3cf-4d02-bb35-a21c95b55dac%3Adelegate-task%3Aissue-266-impl
    Model: gpt-6.1-sol
    Branch: issue-266-issues-board-lists-issues-with-unloaded
    Completed: 2026-10-31T21:04:08.741Z

    Committed the #266 fix as 6a29ab6213 on issue-266-issues-board-lists-issues-with-unloaded. Working tree is clean; nothing was pushed.

    The data cause was a missing read:project token scope. GitHub rejected the combined Project-and-relationships query before reading dependencies, and the optional-metadata fallback discarded everything. The reader now retries without Project fields after that scope error and preserves relationship pagination.

    A read-only run of the updated reader against ePC-SAFT returned complete relationships:

    Unavailable dependencies now use a neutral question-mark icon and a Dependencies unknown section instead of appearing under Blocked with a green Open icon.

    Validation:

    • Both new regression tests failed against unchanged main (da7da71eff0c) before implementation.
    • 81 tests passed in the changed-file check; the additional live-work logic tests also passed.
    • Affected-package typechecks, formatting, lint, GraphQL generation, and React compiler checks passed.
    • The commit hook failed only on the known 74 unused exports from Commit hook fails on every TypeScript change: 74 unused exports on main #256; committed with the authorized --no-verify exception.

    Remaining integration gate: the parent’s real-client UI pass and review. Mobile was out of scope; no live database was opened or copied.

  3. tannerpolley commented on Oct 31, 2026

    @tannerpolley
    OwnerAuthor

    T3 Code closeout: cancelled

    Issue: #266 Issues board lists issues with unloaded dependencies as Blocked, with a green Open icon
    Thread: thread:delegated-task:command%3Amcp%3A66d39c35-d3cf-4d02-bb35-a21c95b55dac%3Adelegate-task%3Aissue-266-impl
    Model: gpt-6.1-sol
    Branch: issue-266-issues-board-lists-issues-with-unloaded
    Completed: 2026-10-31T21:21:08.192Z

    Both regression cases failed before the correction. The fix is in place, and the roadmap test now also checks that missing blockedBy stays Ready unless metadata is explicitly incomplete. Tests and package typechecks are running, but the shared machine is taking much longer to return results.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions