Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Consolidate discovery module ownership and split JSONRPC orchestration responsibilities

Ouverte
  • Quelque chose ne va pas ?
#538 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Refactorisation
Clarté
Plutôt claire
Activité
Active
Stack technique
rust
Domaine
backend, cli

Piste de recherche

Start with the binary module declarations in crates/pet/src/main.rs, the public modules in crates/pet/src/lib.rs, and the orchestration in crates/pet/src/jsonrpc.rs. Review the landing order in #528 and dependencies #536, #539, and #540 before separating responsibilities. Done means behavior, ordering, state-sync semantics, coverage, documentation, formatting, tests, and warnings-as-errors checks remain intact.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

debt

Tracking plan: #528
Priority: P3. Evidence: source-confirmed maintainability and duplicate-compilation concern; no runtime speedup is assumed.

Problem

The JSONRPC orchestration module combines handlers, configuration publication/rollback, refresh coordination, locator state transfer, and telemetry follow-up. The binary also declares find/locators modules that are already public modules in the library, creating parallel module instances instead of using one implementation boundary.

Sources: binary module declarations, library modules, JSONRPC orchestration.

Scope

Use the library discovery/locator implementation from both CLI and server entry points. Extract configuration publication and refresh coordination into independently testable components, leaving RPC handlers as thin adapters. Keep locator crates and priority ordering; avoid a workspace-wide crate merger or async rewrite.

Separate behavior changes from code movement so reviewers can verify this is behavior-preserving. Update architecture/state documentation to the final ownership model, including actual transient-versus-persistent cache lifetimes and all current locators such as Hatch. Move tests with their responsibilities without losing coverage or weakening assertions.

Acceptance criteria

  • Binary and library no longer compile separate find/locators module instances; public interfaces remain deliberate and minimal.
  • Configuration publication, refresh coordination, and handler adaptation have distinct, directly testable responsibilities.
  • Existing CLI/JSONRPC output, error behavior, locator order, coalescing, generation checks, and state-sync semantics remain unchanged.
  • Full default-feature tests, relevant feature/platform jobs, formatting, and warnings-as-errors lint pass.
  • #531/#533 performance and #534 production coverage do not regress; no unmeasured runtime-speedup claim is used to justify the refactor.
  • Documentation reflects the implementation and the change does not introduce generic abstractions used only once.

Dependencies

Perform after #536, bounded scheduling #539, and output ownership #540 stabilize; the complete landing order is in #528. Use #534 coverage and #531/#533 measurements as guardrails. Smaller purely mechanical library-module reuse can be split out earlier if isolated and separately reviewed.

Langage dominant
Rust
Étoiles
207
Forks
45
Merge moyen
2 j 14 h
PR mergées (30 j)
15

Préparer son environnement

Nous n'avons pas encore vérifié les fichiers d'installation de ce projet. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de microsoft/python-environment-tools

Toutes les issues de microsoft/python-environment-tools

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.