Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Scheduling client is absent from the unified Rust, Node.js, and Python facades

Open
  • Is something wrong?
#1,241 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
76/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
node.js, python, rust
Domain
api, backend, developer-experience

Research direction

Start with crates/registry-stack-client/Cargo.toml and crates/registry-stack-client/src/lib.rs, comparing the sibling client modules, then inspect the Node.js and Python facade directories for their binding patterns. Add the scheduling surface across all three facades, run the facade tests and type checks, and run release/scripts/sync-registry-client-node.py --check plus the AGENTS.md dependency-direction gate.

Written by the indexing model from the issue text.

Description

criticality:p3 triage:needs-implementation

What

registry-scheduling-client is a maintained product client, but none of the
three unified facades expose it:

  • crates/registry-stack-client/Cargo.toml depends on the breg, casework,
    discovery, evidence, and relay clients only, and
    crates/registry-stack-client/src/lib.rs has modules for each of those with
    no scheduling module beside them.
  • crates/registry-stack-client-node and crates/registry-stack-client-py
    mention scheduling nowhere.

An adopter who takes the unified client today cannot reach Scheduling through
it and has to depend on the product crate directly, which is the coupling the
facade exists to avoid.

Why it is filed rather than fixed

Purely additive and non-breaking, and #1092 is already large. Nothing in the
MVP is wrong without it; the facade is just incomplete.

Done when

  • registry-stack-client gains a scheduling module re-exporting the client's
    public surface, matching how the sibling modules are written.
  • The Node.js and Python facades carry the binding, with
    release/scripts/sync-registry-client-node.py --check passing.
  • The facade's own tests and type checks cover the new surface.

Note

Adding the binding must not weaken the MVP dependency rule in AGENTS.md: no
scheduling crate may reach a BReg, Casework, or Evidence crate in either
direction. A facade that re-exports several products side by side does not
create such an edge, but the dependency-direction gate should be re-run to
confirm it.

Dominant language
Rust
Stars
2
Forks
0
Avg merge
8h 25m
Merged PRs (30d)
266

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from registrystack/registry-stack

All issues in registrystack/registry-stack

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.