Skip to content

feat: support dynamic plugin discovery via plugins.toml#290

Open
afourniernv wants to merge 1 commit into
NVIDIA:mainfrom
afourniernv:afournier/relay-309-support-rust-plugin-discovery-through-pluginstoml
Open

feat: support dynamic plugin discovery via plugins.toml#290
afourniernv wants to merge 1 commit into
NVIDIA:mainfrom
afourniernv:afournier/relay-309-support-rust-plugin-discovery-through-pluginstoml

Conversation

@afourniernv

@afourniernv afourniernv commented Jun 23, 2026

Copy link
Copy Markdown
Collaborator

Overview

Support manifest-backed dynamic plugin discovery through plugins.toml without turning plugins.toml into a second plugin contract.

  • I confirm this contribution is my own work, or I have the right to submit it under this project's license.
  • I searched existing issues and open pull requests, and this does not duplicate existing work.

Details

  • add [[plugins.dynamic]] parsing to the CLI config loader
  • require manifest and derive canonical plugin.id from relay-plugin.toml
  • allow optional host-owned [plugins.dynamic.config] while rejecting plugin-owned and lifecycle fields in plugins.toml
  • normalize file and directory manifest references and reject duplicate canonical plugin IDs across merged plugins.toml sources
  • keep dynamic plugin discovery separate from the generic runtime PluginConfig path so existing components behavior is preserved
  • expose resolved dynamic plugin discovery state through ResolvedConfig and nemo-relay doctor human/JSON reporting
  • centralize stripped plugins.toml merge semantics in core so the CLI does not duplicate merge logic
  • add focused CLI coverage for discovery parsing, duplicate detection, doctor reporting, and existing launcher/config fallout

Validation run:

  • just test-rust
  • cargo clippy --workspace --all-targets -- -D warnings
  • cargo test -p nemo-relay-cli config::tests -- --nocapture
  • cargo test -p nemo-relay-cli doctor::tests::format_human_reports_discovered_dynamic_plugins_in_configuration -- --nocapture
  • cargo test -p nemo-relay-cli doctor::tests::format_json_is_stable_and_versioned -- --nocapture
  • cargo test -p nemo-relay-cli doctor::tests::format_json_reports_discovered_dynamic_plugin_fields -- --nocapture
  • uv run pre-commit run --files crates/cli/src/config.rs crates/cli/src/doctor.rs crates/cli/tests/coverage/config_tests.rs crates/cli/tests/coverage/doctor_tests.rs crates/cli/tests/coverage/launcher_tests.rs crates/core/src/plugin.rs

Where should the reviewer start?

Start in crates/cli/src/config.rs, then review crates/cli/src/doctor.rs for the reporting surface and crates/cli/tests/coverage/config_tests.rs for the new plugins.dynamic contract coverage.

Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

  • Relates to RELAY-309

Summary by CodeRabbit

  • New Features

    • Added support for dynamic plugins defined in plugins.toml with manifest references, including resolution and configuration tracking.
    • Enhanced doctor command to report dynamic plugin status and configuration details.
  • Chores

    • Extended test coverage for dynamic plugin configuration, resolution, and reporting functionality.

Signed-off-by: Alex Fournier <afournier@nvidia.com>
@afourniernv afourniernv requested a review from a team as a code owner June 23, 2026 04:59
@copy-pr-bot

copy-pr-bot Bot commented Jun 23, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@github-actions github-actions Bot added size:L PR is large Feature a new feature lang:rust PR changes/introduces Rust code labels Jun 23, 2026
@coderabbitai

coderabbitai Bot commented Jun 23, 2026

Copy link
Copy Markdown

Review Change Stack

Walkthrough

Adds first-class dynamic plugin support to plugins.toml loading. A new merge_plugin_config_documents helper is extracted in crates/core. ResolvedConfig gains a dynamic_plugins field backed by new types/enums. The config loader resolves [plugins.dynamic] manifest references, enforces plugin ID uniqueness, and the doctor report surfaces dynamic plugin status. All affected tests are updated.

Changes

Dynamic Plugin Loading and Reporting

Layer / File(s) Summary
Extract merge_plugin_config_documents helper
crates/core/src/plugin.rs
load_plugin_config_files now collects parsed TOML documents into an intermediate vector and delegates merging to a new public merge_plugin_config_documents function, making it importable by the CLI config loader.
ResolvedConfig and dynamic plugin data types
crates/cli/src/config.rs
Adds dynamic_plugins field to ResolvedConfig, introduces ResolvedDynamicPluginConfig struct with reference_status/host_config_status accessor methods, adds DynamicPluginReferenceResolutionStatus and DynamicPluginHostConfigStatus enums, and expands PluginTomlConfig with FileDynamicPluginConfig/PluginTomlPluginsSection parsing types.
Dynamic plugin loading and reference resolution
crates/cli/src/config.rs
Rewrites load_plugin_toml_config_from_paths to parse each plugin TOML, resolve [plugins.dynamic] entries by loading manifests and enforcing unique plugin_id values via a HashSet, strip the dynamic section from the runtime document, and merge remaining docs. Adds manifest-path, empty-table, and cleanup helpers.
Apply config wiring
crates/cli/src/config.rs
Updates apply_plugin_toml_config to accept &mut ResolvedConfig, adds conflict detection for plugins.config defined in multiple sources, assigns resolved.dynamic_plugins, and updates the call site accordingly.
Doctor report dynamic plugin surface
crates/cli/src/doctor.rs
Extends ConfigurationInfo with dynamic_plugins: Vec<DynamicPluginReferenceInfo>, adds the DynamicPluginReferenceInfo struct, wires resolved.dynamic_plugins through collect_reportcollect_configuration, adds Check builders for reference and host-config status, and extends format_human to render a Dynamic plugin subsection.
Config loading tests for dynamic plugins
crates/cli/tests/coverage/config_tests.rs
Adds write_dynamic_manifest test helper, updates existing assertion wrappers to match new Some(Some(...)) resolver output shape, and adds tests for successful manifest resolution, duplicate plugin ID rejection, and invalid lifecycle field rejection.
Doctor and launcher test updates
crates/cli/tests/coverage/doctor_tests.rs, crates/cli/tests/coverage/launcher_tests.rs
Initializes configuration.dynamic_plugins: vec![] in empty_report(), adds JSON and human-format tests for dynamic plugin report output, updates two collect_configuration call sites to pass &[], and adds ..ResolvedConfig::default() to all launcher test struct literals.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~60 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed Title follows Conventional Commits format with 'feat' type, concise imperative summary, under 72 characters, and directly describes the main changeset for dynamic plugin discovery.
Description check ✅ Passed Description includes all required template sections: overview with confirmation checkboxes, detailed implementation points, reviewer guidance, and related issue reference with action keyword.
Docstring Coverage ✅ Passed Docstring coverage is 87.50% which is sufficient. The required threshold is 80.00%.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@crates/cli/src/config.rs`:
- Around line 1022-1032: The unconditional assignment on line 1031 of
plugin_toml.value to resolved.gateway.plugin_config causes a plugins.toml file
with only dynamic plugins (where plugin_toml.value is None) to erase any plugin
config previously loaded from config.toml. Guard the assignment so that
resolved.gateway.plugin_config is only updated when plugin_toml.value is Some,
preventing None values from overwriting existing configuration. The conflict
check already ensures both sources don't define config simultaneously, so this
guard will preserve config from config.toml when plugins.toml contains only
dynamic plugins.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: 5663ca62-17de-47b7-abfe-4da8a74d1364

📥 Commits

Reviewing files that changed from the base of the PR and between 6a93612 and fbf9a05.

📒 Files selected for processing (6)
  • crates/cli/src/config.rs
  • crates/cli/src/doctor.rs
  • crates/cli/tests/coverage/config_tests.rs
  • crates/cli/tests/coverage/doctor_tests.rs
  • crates/cli/tests/coverage/launcher_tests.rs
  • crates/core/src/plugin.rs
📜 Review details
🧰 Additional context used
📓 Path-based instructions (15)
**/*.rs

📄 CodeRabbit inference engine (.agents/skills/add-binding-feature/SKILL.md)

Use snake_case naming convention for Rust identifiers (e.g., nemo_relay_tool_call)

**/*.rs: Any Rust change must run just test-rust
Any Rust change must run cargo fmt --all
Any Rust change must run cargo clippy --workspace --all-targets -- -D warnings

**/*.rs: Run cargo fmt --all for all FFI work since it is Rust work
Run just test-rust to validate FFI changes
Run cargo clippy --workspace --all-targets -- -D warnings to enforce strict linting on FFI work

When Rust files changed as part of Go work, also run cargo fmt --all, just test-rust, and cargo clippy --workspace --all-targets -- -D warnings

**/*.rs: Run cargo fmt --all when Rust files are changed as part of Node work
Run cargo clippy --workspace --all-targets -- -D warnings when Rust files are changed as part of Node work
Run just test-rust when Rust files are changed as part of Node work

**/*.rs: Run cargo fmt --all to format all Rust code
Run cargo clippy --workspace --all-targets -- -D warnings to enforce all clippy lints as errors

**/*.rs: Run cargo fmt --all when Rust files changed as part of WebAssembly work
Run cargo clippy --workspace --all-targets -- -D warnings when Rust files changed as part of WebAssembly work

**/*.rs: If any Rust code changed, always run just test-rust
If any Rust code changed, also run cargo fmt --all
If any Rust code changed, also run cargo clippy --workspace --all-targets -- -D warnings
Run Rust formatting with cargo fmt --all
Run Rust linting with cargo clippy --workspace --all-targets -- -D warnings

**/*.rs: Use cargo fmt for Rust code formatting
Run cargo clippy -- -D warnings to lint Rust code and treat all warnings as errors
Use Rust snake_case naming convention for Rust identifiers
Include SPDX license header in all Rust source files using double-slash comment syntax
Validate Rust code with uv run pre-commit run --all-files to enforce cargo fmt formatting check, cargo clippy lints, and cargo deny aud...

Files:

  • crates/cli/tests/coverage/launcher_tests.rs
  • crates/cli/tests/coverage/config_tests.rs
  • crates/cli/tests/coverage/doctor_tests.rs
  • crates/cli/src/doctor.rs
  • crates/core/src/plugin.rs
  • crates/cli/src/config.rs
{crates/adaptive/**/*.rs,**/*test*.{rs,py,go,ts,js},**/*adaptive*test*.{rs,py,go,ts,js},docs/plugins/adaptive/**}

📄 CodeRabbit inference engine (.agents/skills/maintain-optimizer/SKILL.md)

Maintain documented and tested validation and report behavior for adaptive surfaces

Files:

  • crates/cli/tests/coverage/launcher_tests.rs
  • crates/cli/tests/coverage/config_tests.rs
  • crates/cli/tests/coverage/doctor_tests.rs
**/{Cargo.toml,**/*.rs}

📄 CodeRabbit inference engine (.agents/skills/maintain-packaging/SKILL.md)

Maintain consistency between Rust package names in Cargo.toml and their actual usage across the codebase

Files:

  • crates/cli/tests/coverage/launcher_tests.rs
  • crates/cli/tests/coverage/config_tests.rs
  • crates/cli/tests/coverage/doctor_tests.rs
  • crates/cli/src/doctor.rs
  • crates/core/src/plugin.rs
  • crates/cli/src/config.rs
**/*.{h,hpp,c,cpp,rs}

📄 CodeRabbit inference engine (.agents/skills/maintain-packaging/SKILL.md)

Ensure FFI header and library naming follows consistent conventions across platform-specific builds

Files:

  • crates/cli/tests/coverage/launcher_tests.rs
  • crates/cli/tests/coverage/config_tests.rs
  • crates/cli/tests/coverage/doctor_tests.rs
  • crates/cli/src/doctor.rs
  • crates/core/src/plugin.rs
  • crates/cli/src/config.rs
**/*.{rs,toml}

📄 CodeRabbit inference engine (.agents/skills/rename-surfaces/SKILL.md)

Update Rust crate names and module prefixes during coordinated rename operations

Files:

  • crates/cli/tests/coverage/launcher_tests.rs
  • crates/cli/tests/coverage/config_tests.rs
  • crates/cli/tests/coverage/doctor_tests.rs
  • crates/cli/src/doctor.rs
  • crates/core/src/plugin.rs
  • crates/cli/src/config.rs
**/*.{rs,py,js,ts,tsx,jsx,go,sh,toml,yaml,yml,md}

📄 CodeRabbit inference engine (AGENTS.md)

Keep SPDX headers on source, docs, scripts, and configuration files. The project is Apache-2.0.

Files:

  • crates/cli/tests/coverage/launcher_tests.rs
  • crates/cli/tests/coverage/config_tests.rs
  • crates/cli/tests/coverage/doctor_tests.rs
  • crates/cli/src/doctor.rs
  • crates/core/src/plugin.rs
  • crates/cli/src/config.rs
**/*.{rs,py,go,js,ts,tsx}

📄 CodeRabbit inference engine (AGENTS.md)

Follow binding naming conventions: Rust and Python use snake_case, C FFI exports prefixed nemo_relay_, Go uses PascalCase for public APIs, Node.js uses camelCase.

Files:

  • crates/cli/tests/coverage/launcher_tests.rs
  • crates/cli/tests/coverage/config_tests.rs
  • crates/cli/tests/coverage/doctor_tests.rs
  • crates/cli/src/doctor.rs
  • crates/core/src/plugin.rs
  • crates/cli/src/config.rs
crates/**/*.rs

📄 CodeRabbit inference engine (AGENTS.md)

crates/**/*.rs: Keep async behavior on the existing tokio-based model. Bindings should preserve callback and future lifetimes rather than blocking or hiding async work unexpectedly.
Use Json = serde_json::Value in Rust-facing runtime APIs for JSON payload handling.

Files:

  • crates/cli/tests/coverage/launcher_tests.rs
  • crates/cli/tests/coverage/config_tests.rs
  • crates/cli/tests/coverage/doctor_tests.rs
  • crates/cli/src/doctor.rs
  • crates/core/src/plugin.rs
  • crates/cli/src/config.rs
**

⚙️ CodeRabbit configuration file

**:

AGENTS.md

This file provides guidance to agents, including Claude Code and OpenAI Codex, when working in this repository.

Project Overview

NeMo Relay is a multi-language agent runtime framework for execution scopes, lifecycle events, middleware, plugins, and observability around tool and LLM calls. The core runtime is Rust. Primary supported bindings are Rust, Python, and Node.js. Go, WebAssembly, and the raw C FFI are experimental and source-first.

The shared runtime model is:

  1. Scope stacks decide where work belongs and which scope-local behavior is visible.
  2. Middleware registries decide what guardrails and intercepts run around managed calls.
  3. Plugins install reusable runtime behavior from configuration.
  4. Events record runtime behavior in ATOF form.
  5. Subscribers and exporters consume events in-process or export them to ATIF, OpenTelemetry, OpenInference, or other backends.

Repository Structure

The repository layout separates the Rust runtime, language bindings, documentation,
integration patches, and agent-facing skills.

crates/
  core/       # Rust core runtime crate, published as nemo-relay
  adaptive/   # Adaptive runtime primitives and plugin components
  python/     # PyO3 native extension for the Python package
  ffi/        # Raw C ABI layer used by downstream bindings such as Go
  node/       # NAPI Node.js binding and JavaScript/TypeScript entry points
  wasm/       # wasm-bindgen WebAssembly binding and JS wrappers
python/
  nemo_relay/  # Python wrapper package: scopes, tools, LLM, middleware, typed helpers, plugins, adaptive helpers
  tests/      # Python tests
go/
  nemo_relay/  # Experimental Go CGo binding and tests
fern/         # Fern documentation site
scripts/      # Stable wrappers and helper scripts; build/test/docs entry points live in justfile
third_party/  # P...

Files:

  • crates/cli/tests/coverage/launcher_tests.rs
  • crates/cli/tests/coverage/config_tests.rs
  • crates/cli/tests/coverage/doctor_tests.rs
  • crates/cli/src/doctor.rs
  • crates/core/src/plugin.rs
  • crates/cli/src/config.rs
{crates/**/tests/**,python/tests/**,go/nemo_relay/**/*_test.go}

⚙️ CodeRabbit configuration file

{crates/**/tests/**,python/tests/**,go/nemo_relay/**/*_test.go}: Tests should cover the behavior promised by the changed API surface, including error paths and cross-request isolation where relevant.
Prefer assertions on lifecycle events, scope stacks, middleware ordering, and binding parity over shallow smoke tests.

Files:

  • crates/cli/tests/coverage/launcher_tests.rs
  • crates/cli/tests/coverage/config_tests.rs
  • crates/cli/tests/coverage/doctor_tests.rs
**/*config*.{rs,ts,py,go,js,json,yaml,yml}

📄 CodeRabbit inference engine (.agents/skills/maintain-optimizer/SKILL.md)

Ensure dynamic config shape still matches the documented canonical model

Files:

  • crates/cli/tests/coverage/config_tests.rs
  • crates/cli/src/config.rs
{crates/core,crates/adaptive}/**/*

📄 CodeRabbit inference engine (.agents/skills/prepare-pr/SKILL.md)

Changes to crates/core or crates/adaptive must run the full language matrix

Files:

  • crates/core/src/plugin.rs
crates/core/**/*.rs

📄 CodeRabbit inference engine (.agents/skills/test-go-binding/SKILL.md)

If the change touched crates/core or shared runtime semantics, also use validate-change for broader validation

crates/core/**/*.rs: Use Json = serde_json::Value in Rust-facing runtime APIs where the existing code expects JSON payloads.
Use Result<T> with FlowError in core runtime paths. Keep errors explicit and binding-appropriate at the wrapper layer.

Files:

  • crates/core/src/plugin.rs
crates/{core,adaptive}/**

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

If crates/core or crates/adaptive changed, run the full matrix across Rust, Python, Go, Node.js, and WebAssembly

Files:

  • crates/core/src/plugin.rs
crates/{core,adaptive}/**/*.rs

⚙️ CodeRabbit configuration file

crates/{core,adaptive}/**/*.rs: Review the Rust runtime for async correctness, scope isolation, middleware ordering, and event lifecycle regressions.
Pay close attention to task-local/thread-local scope propagation, callback lifetimes, stream finalization, and root_uuid isolation.
Public API changes should preserve existing behavior unless tests and docs show the intended migration path.

Files:

  • crates/core/src/plugin.rs
🔇 Additional comments (7)
crates/cli/tests/coverage/config_tests.rs (1)

25-56: LGTM!

Also applies to: 409-442, 486-506, 557-576, 577-691

crates/cli/src/doctor.rs (2)

30-32: 📐 Maintainability & Code Quality

Confirm required Rust validation commands were run for this change.

Please provide confirmation/output for:

  • just test-rust
  • cargo fmt --all
  • cargo clippy --workspace --all-targets -- -D warnings

As per coding guidelines: “Any Rust change must run just test-rust”, “Any Rust change must run cargo fmt --all”, and “Any Rust change must run cargo clippy --workspace --all-targets -- -D warnings”.

Source: Coding guidelines


89-98: LGTM!

Also applies to: 159-159, 195-195, 217-260, 1407-1435

crates/cli/tests/coverage/doctor_tests.rs (1)

123-123: LGTM!

Also applies to: 305-330, 405-405, 590-590, 606-634

crates/cli/tests/coverage/launcher_tests.rs (1)

248-248: LGTM!

Also applies to: 325-325, 472-472, 498-498, 544-544, 577-577, 626-626, 702-702, 729-729, 772-772, 815-815, 851-851, 1046-1046, 1165-1165

crates/core/src/plugin.rs (1)

1124-1156: LGTM!

crates/cli/src/config.rs (1)

486-518: LGTM!

Comment thread crates/cli/src/config.rs
Comment on lines +1022 to +1032
if let Some(config_source) = config_toml_plugin_source
&& plugin_toml.value.is_some()
{
return Err(CliError::Config(format!(
"plugin config is defined in both {} and {}; choose one source",
config_source.display(),
format_paths(&plugin_toml.sources)
)));
}
gateway.plugin_config = Some(plugin_toml.value);
resolved.gateway.plugin_config = plugin_toml.value;
resolved.dynamic_plugins = plugin_toml.dynamic_plugins;

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
rg -nP --type=rust -C4 'fn apply_file_config' crates/cli/src/config.rs
rg -nP --type=rust -C2 'plugin_config\s*=' crates/cli/src/config.rs
rg -nP --type=rust -C3 'fn has_config_toml_plugin_config' crates/cli/src/config.rs

Repository: NVIDIA/NeMo-Relay

Length of output: 2007


🏁 Script executed:

sed -n '1015,1040p' crates/cli/src/config.rs | cat -n

Repository: NVIDIA/NeMo-Relay

Length of output: 1209


🏁 Script executed:

rg -nP --type=rust 'apply_file_config|apply_plugin_toml' crates/cli/src/config.rs | head -20

Repository: NVIDIA/NeMo-Relay

Length of output: 376


🏁 Script executed:

rg -nP --type=rust 'struct PluginTomlConfig' crates/cli/src/config.rs -A 5

Repository: NVIDIA/NeMo-Relay

Length of output: 316


Guard assignment so plugins.toml with only dynamic plugins doesn't erase plugin config from config.toml.

Line 1031 unconditionally assigns plugin_toml.value (which is Option<Value>) to resolved.gateway.plugin_config, but the conflict check at line 1021 only triggers when both config_toml_plugin_source and plugin_toml.value are Some. This means a plugins.toml containing only [[plugins.dynamic]] will silently overwrite any plugin config already set by config.toml with None.

Proposed fix
-    resolved.gateway.plugin_config = plugin_toml.value;
+    if plugin_toml.value.is_some() {
+        resolved.gateway.plugin_config = plugin_toml.value;
+    }
     resolved.dynamic_plugins = plugin_toml.dynamic_plugins;
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@crates/cli/src/config.rs` around lines 1022 - 1032, The unconditional
assignment on line 1031 of plugin_toml.value to resolved.gateway.plugin_config
causes a plugins.toml file with only dynamic plugins (where plugin_toml.value is
None) to erase any plugin config previously loaded from config.toml. Guard the
assignment so that resolved.gateway.plugin_config is only updated when
plugin_toml.value is Some, preventing None values from overwriting existing
configuration. The conflict check already ensures both sources don't define
config simultaneously, so this guard will preserve config from config.toml when
plugins.toml contains only dynamic plugins.

Comment thread crates/cli/src/config.rs
Comment on lines +494 to +498
#[derive(Debug, Clone, Copy, PartialEq, Eq, Serialize)]
#[serde(rename_all = "snake_case")]
pub(crate) enum DynamicPluginReferenceResolutionStatus {
Resolved,
}

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there any way this would be unresolved? Do we need this and

pub(crate) fn reference_status(&self) -> DynamicPluginReferenceResolutionStatus

below?

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

Labels

Feature a new feature lang:rust PR changes/introduces Rust code size:L PR is large

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants