[ENH]: Add frontend logic for indexing status

[tanujnay112]

Description of changes

Implemented frontend node logic for the proposed indexing_status endpoint. This endpoint is per collection and returns a tuple of

(percentage_ops_that_are_indexed, num_unindexed_ops, num_indexed_ops, total_ops_in_collection)

TODO after this change:

• authorization for this new endpoint

• client additions to hit this endpoint

• end to end automated testing

• Improvements & Bug fixes

  • ^^^

• New functionality

  • The described indexing_status GET endpoint.

Test plan

How are these changes tested?

• Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Migration plan

Are there any migrations, or any forwards/backwards compatibility changes needed in order to make sure this change deploys reliably?

Observability plan

What is the plan to instrument and monitor this change?

Documentation Changes

Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the _docs section?_

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[tanujnay112]

• [ENH]: Add frontend logic for indexing status #6127 : 2 dependent PRs (#6128 , #6130 ) 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[propel-code-bot]

It also wires the indexing status flow through the Rust frontend route, updates the associated metrics and OpenAPI documentation, and adds integration coverage to exercise the new endpoint.

Affected Areas

• rust/frontend/src/impls/service_based_frontend.rs
• rust/frontend/src/server.rs
• rust/types/src/api_types.rs
• rust/frontend/src/tests (integration test module)

This summary was automatically generated by @propel-code-bot

[propel-code-bot]

[Documentation] There is a stale TODO here. The authorization logic is implemented immediately below.

Suggested change

	// TODO(tanujnay112): Add authorization for indexing status
	// TODO(tanujnay112): Add authorization for indexing status

(Remove the line or update it)

Context for Agents

There is a stale TODO here. The authorization logic is implemented immediately below.

```suggestion
    // TODO(tanujnay112): Add authorization for indexing status
```
(Remove the line or update it)

File: rust/frontend/src/server.rs
Line: 1818

[rescrv]

Should probably have some tests, right?

[rescrv]

This returns error. Let's use that to not silently zero things.

[rescrv]

Let's put this above the auth check as it's 100% derivable from URL?

[propel-code-bot]

[Reliability] Other frontend methods (like get, query, add) implement a retry pattern (e.g., retryable_get + get with a retry loop) to handle transient failures. Since indexing_status makes a network call to the log service (scout_logs), consider wrapping this in a similar retry mechanism to ensure system reliability.

Context for Agents

Other frontend methods (like `get`, `query`, `add`) implement a retry pattern (e.g., `retryable_get` + `get` with a retry loop) to handle transient failures. Since `indexing_status` makes a network call to the log service (`scout_logs`), consider wrapping this in a similar retry mechanism to ensure system reliability.

File: rust/frontend/src/impls/service_based_frontend.rs
Line: 1419

[rescrv]

Good recommendation.