Repository navigation
fix(usage): report current collector probe status - #341
Conversation
No-Test: text-only receipt reasons remain covered by existing tests Co-Authored-By: Codex GPT-5 <47299143+Cuarroc@users.noreply.github.com>
No-Test: activity journal entry only Co-Authored-By: Codex GPT-5 <47299143+Cuarroc@users.noreply.github.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7c73702cd4
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "opencode" => "no recorded OpenCode status-line bytes exist to parse; \ | ||
| a PTY trace probe is missing" | ||
| .into(), | ||
| "kimi" => "Kimi per-run usage was not probed because the subscription expired".into(), |
There was a problem hiding this comment.
When any exited Kimi run is viewed, including runs completed before the subscription expired, this generates a current account-status explanation even though the stored launch contains no subscription observation. It can therefore misstate why that run lacks usage and becomes false again if the subscription is renewed; retain the transport-specific limitation (the PTY exposes context-window occupancy rather than billed usage) and report the expired probe separately in documentation.
AGENTS.md reference: AGENTS.md:L40-L43
Useful? React with 👍 / 👎.
|
Queued — the merge queue status continues in this comment ↓. |
|
@Mergifyio queue |
Merge Queue Status
This pull request spent 7 minutes 5 seconds in the queue, with no time running CI. ReasonThe pull request conflicts with the base branch HintYou should update or rebase your pull request. If you want to requeue this pull request, you can post a Requeued — the merge queue status continues in this comment ↓. |
No-Test: generated docs/dev-hq snapshots; no runtime behavior changed
No-Test: activity handover documentation only
|
@Mergifyio queue |
Merge Queue Status
This pull request spent 25 minutes 18 seconds in the queue, with no time running CI. ReasonThe pull request conflicts with the base branch The pull request was held in the queue, conflicting with 1 pull request ahead of it. The conflict became a base branch one after #340 merged. HintYou should update or rebase your pull request. If you want to requeue this pull request, you can post a Requeued — the merge queue status continues in this comment ↓. |
No-Test: generated HQ snapshot refresh only Conflict-Resolution: merged origin/main into the PR branch and regenerated the derived HQ snapshot.
|
@Mergifyio queue |
No-Test: activity handoff documentation only
Merge Queue Status
This pull request spent 37 minutes 27 seconds in the queue, with no time running CI. ReasonThe pull request conflicts with the base branch The pull request was held in the queue, conflicting with at least one of 2 pull requests ahead of it. The conflict became a base branch one after #342 merged. HintYou should update or rebase your pull request. If you want to requeue this pull request, you can post a Requeued — the merge queue status continues in this comment ↓. |
No-Test: generated HQ snapshot refresh only
|
@Mergifyio queue |
Merge Queue Status
This pull request spent 12 minutes 57 seconds in the queue, including 12 minutes 11 seconds running CI. Required conditions to merge
|
Der Merge-Konflikt mit
mainist durch einen normalen Merge gelöst.Die erzeugten HQ-Snapshots wurden auf dem gemeinsamen Stand neu erstellt.
Der vollständige Linux-Prepush ist grün; der Windows-Lauf bleibt der Merge-Queue vorbehalten.
Report
What changed
origin/mainwithgit merge origin/main; the merge completed without manual conflict hunks.docs/dev-hq/data.jsanddocs/dev-hq/data.jsonafter the merge and committed the generated refresh asd28dd71.a3b5be1; generated HQ snapshot files were then refreshed and committed.Evidence
npm run dev:start-check— Exit 0; 12.9 GB RAM free and at most one Cargo build observed.bash scripts/ci/secret-scan.sh— Exit 0.bash scripts/ci/gates.sh lane precommit— Exit 0.CARGO_TARGET_DIR=/home/pa/targets/slot3 CARGO_BUILD_JOBS=1 bash scripts/ci/gates.sh lane prepush— Exit 0; 480 frontend tests, 516 HQ tests, and 1,764 Rust tests passed; 7 Rust tests skipped; clippy and architecture drift passed.bash scripts/ci/red-first.sh --plan— Exit 0; zero new test specifications for this documentation-only refresh.git push -u origin codex/hq2-05b-p4-docs-r— Exit 0 after the pre-push hook;git ls-remote origin refs/heads/codex/hq2-05b-p4-docs-r— Exit 0; remote SHAd28dd7138f767f465d6ff235b1d4a53b2e908374.NICHT ABGEDECKT
#[cfg(windows)]tests, Windows clippy arms, ConPTY paths, or DPAPI paths. The Windows lane remains for the merge queue.Review
Review: pending (coordinator), Tier B.