All uploads for a public repo stuck in "error" state with 0 sessions since 2026-07-05 (processing fails silently)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- github-actions, kotlin
- Domain
- ci-cd, testing-qa
Research direction
Start with Codecov processing logs for agnaldo4j/kanban-vision-api-kt from 2026-07-05 15:38 UTC, using upload 346cca8668739bf7db5286a47bce4a2e076a3a8f as the entry point. Compare it with commit 3529ad1e and inspect the v2 uploads endpoint, codecov.yml validation, and JaCoCo report details. Done means identifying why processing fails silently and restoring successful coverage processing.
Written by the indexing model from the issue text.
Description
Repo: agnaldo4j/kanban-vision-api-kt (public)
Summary: Every coverage upload since 2026-07-05 ~15:38 UTC ends in state: "error" with totals.coverage: 0.0 and sessions: 0. Uploads themselves succeed (CLI logs Upload queued for processing complete, HTTP 200, reports reach storage) — processing then fails silently (errors: null on the v2 API uploads endpoint).
Timeline:
- Last successfully processed commit:
3529ad1e— 2026-07-02 22:05 UTC (upload statemerged). - First failing commit:
4a074f66— 2026-07-05 15:38 UTC. This commit was a docs-only change (one markdown file), so the uploaded reports are structurally identical to the last good ones. - Every commit since fails identically (20+ uploads, including a re-run of the same commit ~30 min later:
346cca82has 2 uploads, botherror).
Client side unchanged in the window: codecov/codecov-action@v7 (last release Jun 7), wrapper v0.2.9, CLI 11.2.8 (Apr), CODECOV_TOKEN secret unchanged since Mar 18, codecov.yml unchanged for months (validates OK against /validate). JaCoCo XML reports (4 modules) generate fine and parse locally.
Ask: could you check the processing logs for this repo from 2026-07-05 15:38 UTC onward? Example failing commit with 2 uploads: 346cca8668739bf7db5286a47bce4a2e076a3a8f. Happy to provide anything else.
- Dominant language
- No language data
- Stars
- 52
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from codecov/feedback
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Bundle analysis: `normalizePath` replaces everything after the first `-` in a file name, so different assets collidePossibly taken @ChiptenIsCool claimed this 16 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Docs Waiting for: Product Owner
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Difficulty 4/5 1-2 days Newbie friendliness 42/100
All issues in codecov/feedback
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nutmos/expensetrackr#157 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
janitor-team/janitor#2613 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
keyxmakerx/Chronicle#2550 ·
Maintainers usually reply within 1 day
-
ci/cd javascript medium sdk
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
bug good first issue help wanted rust type:infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Open-Glassbeetle/glassbeetle#374 ·
Maintainers usually reply within 1 day