Skip to content

feat(plugins): apply plugin task bindings and lifecycle changes live - #3611

Open
Quick104 wants to merge 4 commits into
mainfrom
feat/plugin-task-live-apply
Open

Quick104 wants to merge 4 commits into
mainfrom
feat/plugin-task-live-apply

Conversation

@Quick104

@Quick104 Quick104 commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

Problem

Related issue: #3551
Validation tasks: changes #1224 C1

Plugin tasks register only when an API server starts. Turning a plugin task on or off, changing
its binding trigger, and installing, enabling, disabling, updating or removing a plugin all wait
for every API server to restart, and each binding write answers restart_required: true. An
administrator who installs a plugin with a scheduled task doesn't see the task until a restart.

This change applies those changes on every API server within seconds, without a restart.

Approach

  • plugins.TaskRegistry.Sync compares the database with the task manager: it registers new
    tasks, unregisters disabled or removed ones, updates names and default schedules in place, and
    reloads schedules. It never writes a schedule; the "saved schedule, else binding trigger, else
    manifest default, else startup" rule from feat(plugins): run plugin tasks on their manifest default schedule #3551 is unchanged.
  • Each API server syncs before a lifecycle change or binding write it handles returns, on every
    plugins_changed or new plugin_tasks_changed event, and every minute as a backstop (10 seconds
    after a failed sync). Binding writes publish only plugin_tasks_changed, so proxy nodes and
    event dispatchers don't rebuild on them.
  • The task manager can register after Start and unregister. Unregistering retires the worker:
    its triggers stop, a run in progress is canceled, and a firing or manual run that found the
    worker before it was retired is refused. ReloadSchedule installs a task's schedule when it
    differs from the one it runs.
  • Reload compares triggers by the fields each type reads. task_schedules keeps day_of_week
    only on weekly triggers, so before this a daily trigger carrying a weekday looked changed on
    every reload and restarted its timer.
  • Both binding PUTs (v2 and frozen v1) share the apply path and answer restart_required: false;
    it is true only on a server with no task manager. The plugin page says on/off applies right
    away.

Validation

  • Touched Go packages (internal/plugins, internal/taskmanager/..., internal/apiv2 plugin and task routes, internal/api/handlers plugin and task routes), with the race detector on the registry and task manager: pass.
  • make lint-changed, the OpenAPI, contract, web types, route inventory, migration ledger and local-path checks: pass.
  • Web: prettier and the plugin helper and plugin admin component tests: pass.
  • A trial merge with the stacked single-run branch builds and passes the same Go tests after two small conflicts in the trigger loop and the architecture doc.
  • Shared dev, on a build that combines this branch with the single-run change and the other plugin
    notification changes, using a QA plugin with two 1-minute default tasks: both appeared on the
    Tasks page right after install, with no restart, and ran every minute. Changing one to every 2
    minutes on the task page applied at once. The plugin page's switch stopped and restarted a task
    live, and its binding kept an empty trigger. Upgrading the plugin to a 3-minute default moved
    the task still on the default and left the other on its 2-minute admin schedule.

Evidence

Evidence: https://evidence.siloserver.org/r/silo-server/pr-3611/

The page shows a plugin task applied live on shared dev: it appears after install without a restart,
a task-page schedule change and the plugin-page switch take effect at once, and an upgrade moves a
task still on the default to the new default while an admin schedule stays.

Risks

  • Task registration changes at runtime on every API server; a bug here could leave a task
    unscheduled until the next one-minute sync.
  • A task installed or enabled at runtime whose schedule is "at startup" runs once a few seconds
    after it registers, as at a server start. With the single-run pull request, that run happens
    on one server.
  • Core tasks still pick up a schedule edited on another server only after a restart; plugin tasks
    pick it up within a minute.
  • After merge, re-check Plugin management / marketplace — Server #1224 C1: installing or updating a plugin now runs a task sync. A sync
    failure doesn't fail the install.
  • Pins silo-plugin-sdk to the same pre-release as feat(plugins): run plugin tasks on their manifest default schedule #3551.

Checklist

  • I read and can explain the complete diff.
  • This pull request addresses one concern.
  • Each test this pull request adds meets "Decide what to test" in CONTRIBUTING.md.
  • The Evidence section shows every change a user can see, or says there is none.

AI Disclosure

  • Harness: Claude Code, run from T3 Code
  • Tool(s): Claude Code (implementation); Codex CLI (independent review of the earlier combined revision in feat(plugins): run plugin tasks on their manifest default schedule #3551)
  • Model(s): claude-opus-5-5 (implementation); gpt-6.1-sol (review)
  • Involvement: Fully AI-generated, human verified
  • Adversarial review: Codex (gpt-6.1-sol) reviewed the multi-server sync, restart durability and
    run cancellation when this code was part of feat(plugins): run plugin tasks on their manifest default schedule #3551; a retired worker that could still run a
    firing it had taken and tasks registering on the wrong schedule were fixed then. A later
    four-agent Claude review found the day_of_week reload mismatch, fixed here.

🤖 Generated with Claude Code

Note

Apply plugin task bindings and lifecycle changes live via task registry sync

  • Adds a TaskRegistry sync loop that reconciles plugin scheduled tasks with enabled installations and bindings: registers new tasks, reloads schedules on trigger changes, and removes disabled or deleted tasks. Servers sync at startup, after local binding or plugin lifecycle changes, on plugin_tasks_changed events from other API servers, and periodically with retries.
  • Extends taskmanager.TaskManager with RegisterLive, Unregister, and ReloadSchedule so tasks can be managed after Start. Tasks implementing the new DefaultFollowingTask interface run their current default triggers without persisting them until an admin saves a schedule.
  • Trigger selection now prefers a valid binding trigger, then the manifest default, then startup. Invalid or unsupported binding triggers are ignored instead of forced to startup. The admin API reports default_schedule on scheduled-task capabilities, and task-binding responses report an accurate restart_required.
  • Adds a migration that removes stored startup-only binding triggers and schedules for plugin tasks so they follow binding or manifest defaults. See 20261106015045_plugin_tasks_follow_manifest_default.sql.
  • Risk: SetAdminPluginTaskBinding now returns (bool, error) instead of error — check implementations of the AdminPluginConfigurationService interface. The triggerLoop rework fixes a bug where a trigger update alone started a run; check worker.go generation handling for regressions.

Macroscope summarized 89edbb1.

@silo-triage silo-triage Bot added the size/XL 500–999 added + deleted lines (all files); change volume, not priority. label Nov 6, 2026
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 6, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-18T17:17:38.354328Z 89edbb1 New commits
🔒 Security Review ✅ Completed 2026-11-18T17:20:04.717204Z 89edbb1 New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@coderabbitai

coderabbitai Bot commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

Explain Change →

Warning

Review limit reached

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

  • Ask an admin to enable usage-based reviews

Open in CodeRabbit

Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing.

Next included review available in 5 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 4 included reviews currently available.

Learn how review limits work.

Review configuration:

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 4831cf17-825d-438e-aad7-e18d3c4f0cab
Commits

Reviewing files that changed from the base of the PR and between 22efdd2 and 89edbb1.

Files ignored due to path filters: 1

  • go.sum is excluded by !**/*.sum
Files selected for processing: 27

  • cmd/silo/main.go
  • contracts/api/v2/openapi.json
  • docs/admin-api.md
  • docs/admin-tasks-api.md
  • docs/architecture/plugin-scheduled-tasks.md
  • go.mod
  • internal/api/handlers/plugins.go
  • internal/api/router.go
  • internal/apiv2/admin_plugin_configuration.go
  • internal/apiv2/admin_plugin_installations.go
  • internal/apiv2/admin_tasks.go
  • internal/apiv2/admin_tasks_test.go
  • internal/cache/redis.go
  • internal/plugins/task_registry.go
  • internal/plugins/task_registry_test.go
  • internal/taskmanager/manager.go
  • internal/taskmanager/manager_persistence_test.go
  • internal/taskmanager/manager_test.go
  • internal/taskmanager/task.go
  • internal/taskmanager/trigger.go
  • internal/taskmanager/worker.go
  • migrations/sql/20261106015045_plugin_tasks_follow_manifest_default.sql
  • web/src/api/types.ts
  • web/src/api/v2/schema.ts
  • web/src/components/admin/plugins/PluginDetailSections.tsx
  • web/src/lib/pluginHelpers.test.ts
  • web/src/lib/taskTrigger.ts

No actionable comments were generated in the recent review.

Walkthrough

Plugin tasks now synchronize with installation and binding changes while API servers are running. The task manager supports live registration, schedule reloads, and worker retirement. Task-binding responses report whether a restart is required.

Changes: Live Plugin Task Synchronization

Layer / File(s) Summary
Dynamic task worker lifecycle
internal/taskmanager/manager.go, internal/taskmanager/worker.go, internal/taskmanager/manager_test.go
The task manager can register, replace, unregister, and reload tasks after startup. Retired workers stop triggers and cancel active runs. Tests cover live registration, unregistering, saved schedules, and schedule reloads.
Registry reconciliation and sync wiring
internal/plugins/task_registry.go, internal/plugins/task_registry_test.go, cmd/silo/main.go, internal/cache/redis.go, docs/architecture/plugin-scheduled-tasks.md, docs/admin-tasks-api.md
The registry reconciles eligible plugin tasks and schedules with installations and bindings. Startup, local changes, cache events, and periodic runs trigger syncs; failed syncs are retried. Tests cover binding changes, saved schedules, read failures, and retry timing.
Task-binding API and response behavior
internal/api/handlers/plugins.go, internal/api/router.go, internal/apiv2/admin_plugin_configuration.go, contracts/api/v2/openapi.json, docs/admin-api.md, web/src/api/v2/schema.ts
Task-binding writes invoke the configured synchronization callback. The API returns whether a restart is required, and API descriptions document when bindings apply without a restart.

Estimated code review effort: 4 (Complex) | ~45 minutes

Change: Feature

Sequence Diagram(s)

sequenceDiagram
  participant AdminClient
  participant PluginHandler
  participant BindingStore
  participant TaskRegistry
  participant TaskManager
  participant ChannelAdmin
  participant ReplicaTaskRegistry
  participant ReplicaTaskManager
  AdminClient->>PluginHandler: submit task-binding change
  PluginHandler->>BindingStore: store binding
  PluginHandler->>TaskRegistry: invoke sync callback
  TaskRegistry->>TaskManager: apply task and schedule changes
  PluginHandler->>ChannelAdmin: publish plugin_tasks_changed
  ChannelAdmin->>ReplicaTaskRegistry: deliver plugin_tasks_changed
  ReplicaTaskRegistry->>ReplicaTaskManager: apply task and schedule changes
Loading

Possibly related issues

  • Silo-Server/silo-server#4073 — The issue describes a saved schedule that does not run on its first firing. This change updates schedule reload and trigger-generation handling, but the issue notes that confirmation after merge is still needed.

Possibly related PRs

  • Silo-Server/silo-server#3551 — This PR establishes task schedule precedence that the live registry must preserve when it applies binding and manifest schedule changes.

Suggested reviewers: zzebrahz, coffeeknyte, rhainland

Merge Risk: Minimal · previous review 22efd

Plugin task bindings and lifecycle changes now apply to running API servers, with retries after failed syncs and conditional restart reporting. No unresolved merge-blocking issue was found in the reviewed changes.

Security architecture risk: Low · up to 22efd

Administrator access controls remain in place. However, disabling and quickly re-enabling a task can admit another run before the previous execution finishes cancelling, weakening local execution ownership. No new privilege escalation or cross-tenant access was established.

Retained concerns

  • Medium · reliability · inferred: Rapid disable/re-enable can release a task key before its previous execution terminates. Unregister deletes the mapped worker and only signals cancellation; RegisterLive creates a fresh worker whose reservation state does not include the retiring execution. A new manual or scheduled run can therefore overlap a slow-to-unwind execution, while cancellation by key addresses only the replacement. This weakens process-local execution containment and ownership; it is not a claim that tasks previously had cluster-wide exclusivity.
Security review details

Security Blast Radius

  • inferred — An authorized binding change affects the selected installation and capability on every participating API server after successful reconciliation. The retained ownership concern is process-local and task-key-specific; no expansion to other tenants, environments, credentials, or infrastructure authority was established.

Trust Boundaries and Controls

  • observed — Administrator-controlled binding data is persisted before live effects occur. Peer events are reconciliation hints rather than authority-bearing commands, and the scan independently restricts registrations to eligible installation capabilities.

Resilience and Maintainability Implications

  • observed — Retirement stops triggers and makes stale worker reservations fail. These controls prevent new reservations on the retired object, but do not retain task-key ownership until its active execution finishes; a replacement has independent state.

Hardening Proposals

  • proposed — Retain a task-key-level execution reservation across worker generations until the retiring execution completes, or defer replacement execution until draining finishes. This would preserve local ownership without requiring a cluster-wide singleton scheduler.
Pre-merge checks: Passed 4

Check name Status Explanation
Title check Passed The title "feat(plugins): apply plugin task bindings and lifecycle changes live" matches the main change in the changeset. The raw summary shows a live TaskRegistry sync, task-manager registration aft…
Description check Passed The description states the problem (plugin tasks register only at API server startup and binding writes return restart_required true) and the approach (TaskRegistry.Sync, per-server syncs, plugin_task…
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.
Full details: Title check

Explanation

The title "feat(plugins): apply plugin task bindings and lifecycle changes live" matches the main change in the changeset. The raw summary shows a live TaskRegistry sync, task-manager registration after Start, binding-change callbacks, and restart_required now false when a task manager is present. The title is specific and uses a conventional commit prefix.

Full details: Description check

Explanation

The description states the problem (plugin tasks register only at API server startup and binding writes return restart_required true) and the approach (TaskRegistry.Sync, per-server syncs, plugin_tasks_changed event, task manager retirement and reload). It also lists validation, risks, and evidence. It matches the changeset closely.

Finishing Touches

Generate unit tests (beta)

  • Commit to this branch
  • Create a new PR
Fix failing CI checks

  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Recent review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: af00aafa-c0bf-4f47-b54e-287a588c63d1
Commits

Reviewing files that changed from the base of the PR and between f2c7731 and 22efdd2.

Files selected for processing: 15

  • cmd/silo/main.go
  • contracts/api/v2/openapi.json
  • docs/admin-api.md
  • docs/admin-tasks-api.md
  • docs/architecture/plugin-scheduled-tasks.md
  • internal/api/handlers/plugins.go
  • internal/api/router.go
  • internal/apiv2/admin_plugin_configuration.go
  • internal/cache/redis.go
  • internal/plugins/task_registry.go
  • internal/plugins/task_registry_test.go
  • internal/taskmanager/manager.go
  • internal/taskmanager/manager_test.go
  • internal/taskmanager/worker.go
  • web/src/api/v2/schema.ts
Files skipped from review as they are similar to previous changes: 1

  • docs/admin-tasks-api.md

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 0 remain after this review.

@silo-triage silo-triage Bot added enhancement New feature or request priority: P2 Limited scope, workaround exists, or polish stacked Base is another open PR; merge in stack order named in the body labels Nov 6, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 5

Review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 3e807b59-a7b1-4e3c-a450-3aac7be34857
Commits

Reviewing files that changed from the base of the PR and between 8e19480 and f759db7.

Files selected for processing: 18

  • cmd/silo/main.go
  • contracts/api/v2/openapi.json
  • docs/admin-api.md
  • docs/admin-tasks-api.md
  • docs/architecture/plugin-scheduled-tasks.md
  • internal/api/handlers/plugins.go
  • internal/api/router.go
  • internal/apiv2/admin_plugin_configuration.go
  • internal/apiv2/admin_plugin_configuration_test.go
  • internal/cache/redis.go
  • internal/plugins/task_registry.go
  • internal/plugins/task_registry_test.go
  • internal/taskmanager/manager.go
  • internal/taskmanager/manager_test.go
  • internal/taskmanager/worker.go
  • internal/taskmanager/worker_test.go
  • web/src/api/v2/schema.ts
  • web/src/components/admin/plugins/PluginDetailSections.tsx

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 0 remain after this review.

Comment thread contracts/api/v2/openapi.json Resolved
Comment thread contracts/api/v2/openapi.json Resolved
Comment thread docs/admin-api.md Resolved
Comment thread docs/admin-tasks-api.md Resolved

@chatgpt-codex-connector chatgpt-codex-connector 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 101e626a1f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +194 to +195
if !w.runsSchedule(configs) {
w.setTriggers(configs, m.triggerFactory, nil, true)

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Clear the change flag when reloading an unscheduled task

When a plugin task has an explicitly empty schedule on this replica and another server saves a nonempty schedule, this reload calls setTriggers with notify=true. The waiting triggerLoop consumes triggerUpdate in its zero-trigger branch without clearing triggerChanged; consequently, the first real firing only clears that flag and skips execution. The production triggers are one-shot until rearmed, so the task then remains unscheduled indefinitely, and subsequent registry syncs cannot recover it because runsSchedule already reports a match. Clear the change flag when consuming the update in the zero-trigger branch so remotely re-enabled schedules actually run.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Fixed in 54d188c, with a synctest regression test (TestReloadScheduleRunsTaskThatHadNoTriggers) that fails without the fix. While testing I found the reverse case: two quick updates made the loop treat the second update signal as a firing and run the task unscheduled. 3b38461 replaces the change flag with a trigger generation count. An update now only wakes the loop, and a firing runs the task only if it came from the triggers the loop is waiting on.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

Review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 3fdf944f-9b47-45e6-a2df-78ae3ade2d78
Commits

Reviewing files that changed from the base of the PR and between f759db7 and 101e626.

Files selected for processing: 7

  • contracts/api/v2/openapi.json
  • docs/admin-api.md
  • docs/admin-tasks-api.md
  • docs/architecture/plugin-scheduled-tasks.md
  • internal/apiv2/admin_plugin_configuration.go
  • web/src/api/v2/schema.ts
  • web/src/components/admin/plugins/PluginDetailSections.tsx
Files skipped from review as they are similar to previous changes: 1

  • web/src/components/admin/plugins/PluginDetailSections.tsx

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 1 remain after this review.

@silo-triage silo-triage Bot added size/XXL 1000–2999 added + deleted lines (all files); change volume, not priority. and removed size/XL 500–999 added + deleted lines (all files); change volume, not priority. labels Nov 6, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

Review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 3a1f3fa3-91a0-491b-8833-e59f3d9fd260
Commits

Reviewing files that changed from the base of the PR and between 101e626 and f2c7731.

Files selected for processing: 7

  • docs/architecture/plugin-scheduled-tasks.md
  • internal/plugins/task_registry.go
  • internal/plugins/task_registry_test.go
  • internal/taskmanager/manager.go
  • internal/taskmanager/manager_test.go
  • internal/taskmanager/worker.go
  • internal/taskmanager/worker_test.go

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 0 remain after this review.

Comment thread internal/plugins/task_registry.go Resolved
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@Quick104
Quick104 force-pushed the feat/plugin-task-default-schedule branch from cebebb3 to 68e9e30 Compare November 18, 2026 16:38
@Quick104
Quick104 force-pushed the feat/plugin-task-live-apply branch from 40c0624 to 2ece1fe Compare November 18, 2026 16:38
…long for a timer

The schedule cleanup deleted any plugin task schedule holding one startup
trigger, including one an administrator saved after the seed. A seed
leaves revision 2 at most, so higher revisions now stay.

An interval above what a time.Duration holds overflowed into a timer
that fired at once; such a trigger is no longer runnable.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@Quick104 Quick104 closed this Nov 18, 2026
@Quick104
Quick104 force-pushed the feat/plugin-task-live-apply branch from 2ece1fe to 7269acb Compare November 18, 2026 16:49
@Quick104 Quick104 reopened this Nov 18, 2026
Quick104 and others added 2 commits November 18, 2026 17:10
…le fixes

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@Quick104
Quick104 force-pushed the feat/plugin-task-live-apply branch from 22efdd2 to 89edbb1 Compare November 18, 2026 17:15
Base automatically changed from feat/plugin-task-default-schedule to main November 18, 2026 19:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request priority: P2 Limited scope, workaround exists, or polish size/XXL 1000–2999 added + deleted lines (all files); change volume, not priority. stacked Base is another open PR; merge in stack order named in the body

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant