Skip to content

Repository navigation

🐛🧑‍💻 - Dogfooding recover bounded Project item visibility after linking a PR #486

New issue
New issue
Closed
Bug
#487
Closed
🐛🧑‍💻 - Dogfooding recover bounded Project item visibility after linking a PR#486
Bug
#487
Assignees
efraespada
Labels
100%Progress: 100%branchedIndicates that a branch has been created for this issue.bugSomething isn't workingbugfixSomething isn't workingpriority: highCritical issue, needs immediate attention.size: XLIndicates that the issue or task is extra large in scope and complexity.

Description

@efraespada
efraespada
opened on Oct 13, 2026

Description

Live PR #485 was successfully added to the configured Project and its status initialized, but the immediate priority operation failed because the new item was absent from the subsequent paginated list. The concurrent commit job failed on the same PR size lookup. Both exact workflow replays succeeded once the item was visible. The current Action surfaces this transient state as provider.unavailable and requires a manual retry.

Expected: bounded recovery for an absent newly linked item, with fresh validated provider evidence, while retaining truthful failure for persistent absence, permission errors, malformed data and unsafe identity. Keep existing Project status on replay. No unbounded retries, permission expansion or unrelated platform changes.

Reproducing the issue

  1. Open a real Action-managed PR linked to its issue and configured Project.
  2. Observe LinkPullRequestProjectUseCase return an item ID and initialize its status.
  3. Priority/size lookup reads a Project item listing that temporarily omits the just-added PR.
  4. Workflows 38402185354 and 38402175824 failed on attempt 1 with: Issue or pull request [#484] 🐛 - Dogfooding runtime doctor labels issue and PR links as repository revisions #485 is not in project PVT_kwDOA8wRO84Ajh7B.
  5. Attempt 2 of the same workflows succeeded. Preserve this evidence, add regression coverage for recovery and exhausted/error paths, and document the bounded provider behavior.

copilot Version

3.3.1; master c7cfec8.

Activity

  1. efraespada
    added
    bugSomething isn't working
    bugfixSomething isn't working
    priority: highCritical issue, needs immediate attention.
    on Oct 13, 2026
  2. vypbot
    added
    state:ai-processing
    on Oct 13, 2026
  3. vypbot
    assigned
    efraespada
    on Oct 13, 2026
  4. vypbot
    added the
    Bug
    issue type on Oct 13, 2026
  5. vypbot
    added this to vypdevon Oct 13, 2026
  6. vypbot
    moved this to Todo in vypdevon Oct 13, 2026
  7. vypbot
    changed the title [-]Dogfooding: recover bounded Project item visibility after linking a PR[/-] [+]🐛 - Dogfooding recover bounded Project item visibility after linking a PR[/+] on Oct 13, 2026
  8. vypbot
    added
    state:blocked
    state:awaiting-maintainer
    and removed
    state:ai-processing
    on Oct 13, 2026

  9. vypbot commented on Oct 13, 2026

    @vypbot
    vypbot
    on Oct 13, 2026
    Contributor

    Hi! I’m @vypbot, the Copilot assistant for this repository.

    I can answer questions, explain the codebase, propose implementation and test plans, review issues and pull requests for potential bugs or security problems, and help authorized maintainers apply changes.

    Try /copilot help to see the available commands, or mention @vypbot with your question.

  10. efraespada
    added
    in-progressStart work on an admitted issue.
    on Oct 13, 2026
  11. vypbot
    added
    branchedIndicates that a branch has been created for this issue.
    on Oct 13, 2026

  12. 5 remaining items

  13. vypbot
    added
    state:ai-processing
    size: XLIndicates that the issue or task is extra large in scope and complexity.
    on Oct 13, 2026
  14. efraespada
    linked a pull request that will close this issue[#486] 🐛 - Dogfooding recover bounded Project item visibility after linking a PR #487on Oct 13, 2026
  15. vypbot
    added
    90%Progress: 90%
    and removed
    state:ai-processing
    on Oct 13, 2026

  16. vypbot commented on Oct 13, 2026

    @vypbot
    vypbot
    on Oct 13, 2026
    Contributor

    Issue closed — historical progress

    Current status: closed as completed.

    The last estimate is retained below as history. Closure does not certify a new percentage, tests, or branch alignment.

    Action required: none for this closed issue. If work continues, reopen the issue; a fresh assessment can update this same card.

    Last assessment before closure (historical)

    Progress: 90% — in progress

    > Current status: The bounded membership and direct field recovery are implemented, with identity and evidence checks, replay preservation, regression cases, and documentation. The supplied comparison supports source changes but does not establish that tests or live acceptance checks passed.

    Next: Run the regression and required project gates, then confirm live acceptance: verify Project, priority, and size behavior and replay without duplicate membership or resetting Status.

  17. vypbot commented on Oct 13, 2026

    @vypbot
    vypbot
    on Oct 13, 2026
    Contributor

    Issue closed: synchronization recommendation retired

    No branch synchronization is required for this closed issue.

    The previous recommendation is historical. Issue closure does not certify that the branches are synchronized.

  18. efraespada
    added a commit that references this issue on Oct 13, 2026

    Merge pull request #487 from vypdev/bugfix/486-dogfooding-recover-bou…

    b7b1616

  19. vypbot commented on Oct 13, 2026

    @vypbot
    vypbot
    on Oct 13, 2026
    Contributor

    Branch synchronization needs attention. Open the current status.

  20. vypbot
    closed this as completedon Oct 13, 2026
  21. vypbot
    removed
    90%Progress: 90%
    on Oct 13, 2026
  22. github-project-automation
    moved this from Todo to Done in vypdevon Oct 13, 2026
  23. vypbot
    added
    100%Progress: 100%
    and removed
    in-progressStart work on an admitted issue.
    state:workingWork can proceed on the verified branch or without a branch.
    on Oct 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

100%Progress: 100%branchedIndicates that a branch has been created for this issue.bugSomething isn't workingbugfixSomething isn't workingpriority: highCritical issue, needs immediate attention.size: XLIndicates that the issue or task is extra large in scope and complexity.

Type

Bug

Projects

  • vypdev
    Status
    Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions