Skip to content

refactor(stovepipe): Extract fact persistence - #1057

Open
prathshenoy wants to merge 2 commits into
mainfrom
prath.shenoy/refactor/stovepipe-validation-facts
Open

prathshenoy wants to merge 2 commits into
mainfrom
prath.shenoy/refactor/stovepipe-validation-facts

Conversation

@prathshenoy

@prathshenoy prathshenoy commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Summary

What:

  • Extract shared validation-fact persistence without changing recording behavior.

Why:

  • Allow repository-wide and project results to retain the same retry and ownership checks when their processing moves into separate stages. The existing recording stage owns this shared behavior, preventing another stage from reusing it directly.

Test Plan

  • Add unit tests.

Revert Plan

  • Revert this PR. It reorganizes existing code without changing schemas or stored data.

Issue Links

Stack

  1. refactor(stovepipe): Extract fact persistence #1057
  2. feat(stovepipe): Define project analysis stage #1066
  3. feat(stovepipe): Implement project processing #1058
  4. feat(stovepipe): Recover project analysis failures #1062
  5. feat(stovepipe): Wire the project analysis stage #1065

prathshenoy and others added 2 commits November 10, 2026 10:42
## Summary
**What**:
- Expose both request-scoped attribution lookups through the service
API.

**Why**:
- Let clients query the issues affecting a project and the projects
affected by an issue. The read controller provides this behavior, but
service bindings and wiring are needed to make it available through the
API.

## Test Plan
- [x] Add unit tests.

## Revert Plan
- Revert this PR. It adds read-only APIs without changing schemas or
stored data.

## Issue Links
- [CODEM-632](https://linear.app/uber/issue/CODEM-632/projects-issues)

## Stack
1. #1046
1. #1047
1. #1048
1. #1049
1. #1053
1. #1054
1. #1051
## Summary
**What**:
- Extract shared validation-fact persistence without changing recording behavior.

**Why**:
- Allow repository-wide and project results to retain the same retry and ownership checks when their processing moves into separate stages. The existing recording stage owns this shared behavior, preventing another stage from reusing it directly.

## Test Plan
- [x] Add unit tests.

## Revert Plan
- Revert this PR. It reorganizes existing code without changing schemas or stored data.

## Issue Links
- [CODEM-632](https://linear.app/uber/issue/CODEM-632/projects-issues)
@prathshenoy
prathshenoy force-pushed the prath.shenoy/refactor/stovepipe-validation-facts branch from 160f64a to 0e595b8 Compare November 10, 2026 15:42
@prathshenoy
prathshenoy marked this pull request as ready for review November 10, 2026 16:03
@prathshenoy
prathshenoy marked this pull request as draft November 10, 2026 16:03
@prathshenoy
prathshenoy marked this pull request as ready for review November 10, 2026 16:03
@prathshenoy
prathshenoy removed this pull request from stack #1059 November 10, 2026 16:28
@prathshenoy
prathshenoy added this pull request to stack #1067 November 10, 2026 16:44
@prathshenoy
prathshenoy removed this pull request from stack #1067 November 10, 2026 23:23
prathshenoy added a commit that referenced this pull request Nov 10, 2026
## Summary
**What**:
- Run project analysis after terminal build analysis and before repository recording.
- Mark project analysis finished after project statuses and issue attribution are recorded, or processing is abandoned.

**Why**:
- Ensure attribution uses final build issues and repository recording receives the project results needed to distinguish partial failures from repository-wide failures.
- Keep request summaries from reporting completion while project analysis is still running, and repair incomplete summary updates before handing off to repository recording.

## Test Plan
- [x] Add unit tests.

## Revert Plan
- Revert this PR after pausing intake and draining or reconciling pending project-analysis work, because the revert removes its consumers.

## Issue Links
- [CODEM-632](https://linear.app/uber/issue/CODEM-632/projects-issues)

## Stack
1. #1057
1. #1066
1. #1058
1. #1062
1. #1065
@prathshenoy
prathshenoy added this pull request to stack #1071 November 10, 2026 23:24
prathshenoy added a commit that referenced this pull request Nov 10, 2026
## Summary
**What**:
- Run project analysis after terminal build analysis and before repository recording.
- Mark project analysis finished after project statuses and issue attribution are recorded, or processing is abandoned.

**Why**:
- Ensure attribution uses final build issues and repository recording receives the project results needed to distinguish partial failures from repository-wide failures.
- Keep request summaries from reporting completion while project analysis is still running, and repair incomplete summary updates before handing off to repository recording.

## Test Plan
- [x] Add unit tests.

## Revert Plan
- Revert this PR after pausing intake and draining or reconciling pending project-analysis work, because the revert removes its consumers.

## Issue Links
- [CODEM-632](https://linear.app/uber/issue/CODEM-632/projects-issues)

## Stack
1. #1057
1. #1066
1. #1058
1. #1062
1. #1065

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant