Skip to content

feat(stovepipe): expose List RPC - #795

Merged
mnoah1 merged 1 commit into
mnoah1/stovepipe-list-query-readabilityfrom
mnoah1/stovepipe-list-rpc
Oct 6, 2026
Merged

mnoah1 merged 1 commit into
mnoah1/stovepipe-list-query-readabilityfrom
mnoah1/stovepipe-list-rpc

Conversation

@mnoah1

@mnoah1 mnoah1 commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Add List handler to route to the new List controller. Wire this into the existing OSS service.

Test Plan

All 22 Stovepipe and service unit targets pass. make fmt gazelle lint check-tidy check-gazelle passes.

Revert Plan

Revert this commit to leave List unimplemented again; existing RPCs and storage are unchanged.

API Changes

Expose the existing List RPC. No protobuf or schema changes.

@mnoah1
mnoah1 marked this pull request as ready for review October 6, 2026 21:59
@mnoah1
mnoah1 requested review from a team, behinddwalls and sbalabanov as code owners October 6, 2026 21:59
@mnoah1
mnoah1 added this pull request to stack #783 October 6, 2026 21:59
Summary:
Wire the approved List RPC to the controller in #785. Preserve optional time-bound presence, map current request summaries to protobuf, and use the same configured queues as Ingest. Add mapper and handler coverage; end-to-end coverage remains a follow-up.

Test Plan:
All 22 Stovepipe and service unit targets pass. make fmt gazelle lint check-tidy check-gazelle passes.

Revert Plan:
Revert this commit to leave List unimplemented again; existing RPCs and storage are unchanged.

API Changes:
Expose the existing List RPC. No protobuf or schema changes.
@mnoah1
mnoah1 force-pushed the mnoah1/stovepipe-list-rpc branch from c1d49e7 to 4ab1fe0 Compare October 6, 2026 21:59
@mnoah1
mnoah1 added this pull request to the merge queue Oct 6, 2026
Merged via the queue into main with commit 7740efe Oct 6, 2026
16 checks passed
@behinddwalls
behinddwalls deleted the mnoah1/stovepipe-list-rpc branch October 6, 2026 22:18
DivyanshGarg380 pushed a commit to DivyanshGarg380/submitqueue that referenced this pull request Oct 7, 2026
## Why?

Verify the List RPC added in uber#795 against the real gRPC service and
MySQL, while keeping read-contract tests independent of asynchronous
ingestion workflows.

## What?

### Added

- List coverage for pagination and timestamp ties, time-window defaults
and boundaries, queue isolation, unknown acceptance times, and invalid
requests/tokens.
- Assertions in existing ingest workflows that List exposes lifecycle
summaries, deduplication preserves acceptance time, and acceptance time
matches request history.
- RFC update marking E2E coverage complete.

### Refactored

- Move ingest scenarios from `suite_test.go` into `ingest_test.go`; keep
setup/teardown and health checks in the suite, List scenarios in
`list_test.go`, and reusable helpers in `harness_test.go`. This keeps
infrastructure separate from behavior and makes each group easier to
review.
- Seed List fixtures through storage interfaces on dedicated queues.
This makes edge cases deterministic and lets List tests run without
relying on ingest tests or pipeline timing.
- Remove transient queue-message-count assertions and use durable
acknowledged offsets to verify processing. A consumer can acknowledge
and garbage-collect a message before a test counts it.

No production behavior, API, or schema changes.

## Test Plan

- Full Stovepipe E2E suite passed.
- List-only scenarios passed twice without running ingest tests.
- Stovepipe/service unit tests and repository formatting, lint, tidy,
and Gazelle checks passed.
- Internal validator lint/coverage checks could not complete in this OSS
workspace; coverage requires a missing `.arcconfig`.

## Revert Plan

Revert this test and documentation change; runtime behavior is
unchanged.

This branch was previously deployed

1 inactive deployment
stack-rebase — 4ab1fe0e Deployed Oct 6, 2026 by mnoah1 via Rebase Stack #569
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.

2 participants