Skip to content

[Bug]: per-login batch jobs are poison-pill-prone (no per-item isolation) (P1) #787

Description

@JSONbored

Problem

src/queue/processors.ts:295 (buildContributorDecisionPacks) and :385 (buildContributorEvidence, up to 500 logins) loop for (login) await ... with no per-login try/catch. One throwing login fails the whole job → retry re-runs from #1; a persistent failure becomes a poison pill starving everyone after it. The repo-snapshot path is already fanned out one-job-per-repo and isolated.

Fix

Per-login try/catch (log+continue) or fan out one job per login.

Acceptance

  • One failing login does not block the rest; failures logged, job completes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    gittensor:bugGittensor-scored bug fix — scores a 0.05x multiplier.roadmapOn the Wave-2 agent-layer roadmap board (project 9)

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions