fix(observability): expose GitHub question receipt and rejection counters - #483
Merged
Conversation
…nters Session-Id: 01a077a1-b1e7-7442-a74b-1a7e2adaeab2
Contributor
|
@coderabbitai review Requested for exact head |
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
GitHub question counters were available only in the running Factory object, so the heartbeat reader could not distinguish an unseen question from one rejected before parking. Add an optional six-field
questionCountersheartbeat block and incrementgithubAgentQuestionsReceivedat handler entry, before any early return. The block carries received, detected, and the four existing rejection counts; only the authoritative daemon supplies zero defaults. ExistingstartedAtdates the daemon lifetime. Public health and parking/trust behavior are unchanged.These are process-wide diagnostic totals, not per-issue receipts or an exhaustive partition: detected increments after parking; deduplication and reservation refusal have separate behavior. Companion https://github.com/AgentWorkforce/factory-cloud/pull/125 projects the block through authenticated
/evidence. Availability in production requires a normal reviewed release and subsequent cloud version pin; this PR does not publish or deploy.Validation:
AssertionError: expected undefined to deeply equal { …(6) }. Each of the five real handler outcomes failed withAssertionError: expected undefined to be 1for Received.AssertionError: expected true to be falseon the block's own-property check. Mutation restored.AssertionError [ERR_ASSERTION]: 6 producer/consumer roundtrips failed.556f97e4f744416ef24e71ef58785646fe1a7129.keeps the live heartbeat fresh while draining a blocking live event burstfails locally (expected 800 to be less than 500). Re-running that test with the base production module at9934a1acalso fails its stale-heartbeat assertion (expected true to be false); head fails the age assertion again. Both base and head exhibit this local timing failure; the full local run is not green.556f97e4f744416ef24e71ef58785646fe1a7129, confirmed withgh run list --branch fix/question-counter-heartbeat-0906. All four E2E jobs and the package job passed, including its full suite and packed lifecycle verification on CI Node 22. The local timing failure above remains disclosed. No independent review signoff is claimed.