README
¶
Fix submission
The controller consumes a FixRequest containing a queue name and build ID. It pages through a build's durable issue records and skips submission when any record has a fix ID, including recovered issues. Otherwise, it selects one currently open issue whose first-seen build matches this build and calls RepairExecutor.Submit.
A returned fix ID is associated with the issue through BuildIssueStore.Update, using the version read during selection. A concurrent association is preserved. A submission error without an ID leaves the issue eligible for normal queue retries; an ID returned alongside an error is retained.
Issue tracking calls fixrequest.Publish after persisting both the build observation and open issue. Publications for the same build share a message identity and partition.
The one-per-build limit is controller policy. Submission precedes persistence, so overlapping deliveries, crashes, and failed writes can still produce duplicate executor calls. Issue recovery remains separate from repair association.
Documentation
¶
Overview ¶
Package fix submits build-scoped repair work.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type Controller ¶
type Controller struct {
// contains filtered or unexported fields
}
func NewController ¶
func (*Controller) ConsumerGroup ¶
func (c *Controller) ConsumerGroup() string
func (*Controller) Name ¶
func (c *Controller) Name() string
func (*Controller) TopicKey ¶
func (c *Controller) TopicKey() consumer.TopicKey
Source Files