review openrpc interface #1

New issue

Closed

opened 2026-03-19 06:09:39 +00:00 by despiegk · 7 comments

despiegk commented 2026-03-19 06:09:39 +00:00

Owner

Copy link

check all content in /Volumes/T7/code0/hero_proc/docs
make sure its all up to date

then lets review

make sure there is one interface where we can do

quick_service_set
quick_service_list
quick_service_delete
quick_service_get
quick_service_start
quick_service_stop
quick_service_status

which is combination of actions & service definition

set:

• name
• cmd
• ...

everything needed to run 1 service with 1 action
simple dependency is good

the action gets this quick_service name as prepend so we can easily delete corresponding actions

then we can run it

its an easy way how to deal with simple services who have one action

quick_service_spec.md

should be the spec

check all content in /Volumes/T7/code0/hero_proc/docs make sure its all up to date then lets review make sure there is one interface where we can do quick_service_set quick_service_list quick_service_delete quick_service_get quick_service_start quick_service_stop quick_service_status which is combination of actions & service definition set: - name - cmd - ... everything needed to run 1 service with 1 action simple dependency is good the action gets this quick_service name as prepend so we can easily delete corresponding actions then we can run it its an easy way how to deal with simple services who have one action quick_service_spec.md should be the spec

despiegk commented 2026-03-19 06:13:15 +00:00

Author

Owner

Copy link

Implementation Spec for Issue #1: Quick Service OpenRPC Interface

Objective

Add a quick_service RPC namespace that provides a simplified interface for managing single-action services. A quick_service bundles a service definition and its single action into one atomic operation: quick_service.set creates both the action (named {name}_action) and the service (referencing that action) in a single call.

Requirements

• Add 7 new RPC methods under the quick_service namespace:
  • quick_service.set — create/update a quick service (creates both action + service atomically)
  • quick_service.list — list all quick services
  • quick_service.delete — delete a quick service and its associated action
  • quick_service.get — get a quick service definition
  • quick_service.start — start a quick service
  • quick_service.stop — stop a quick service
  • quick_service.status — get quick service status
• quick_service.set takes: name, cmd, plus optional fields (interpreter, env, dir, timeout_ms, etc.)
• Action naming convention: {name}_action for easy cleanup
• quick_service.delete removes both the service and its prefixed action
• All methods appear in openrpc.json, docs, and auto-generated SDK client
• A docs/quick_service_spec.md specification document is created
• No new DB tables — reuses existing actions and services tables

Files to Modify/Create

File	Action	Description
crates/hero_proc_server/src/rpc/quick_service.rs	Create	RPC handler module for all 7 methods
crates/hero_proc_server/src/rpc/mod.rs	Modify	Register module and add dispatch arms
crates/hero_proc_server/openrpc.json	Modify	Add 7 method definitions
docs/hero_proc_openrpc/openrpc.md	Modify	Add Quick Service section
docs/quick_service_spec.md	Create	Specification document
crates/hero_proc_integration_test/src/tests/quick_services.rs	Create	Integration tests
crates/hero_proc_integration_test/src/tests/mod.rs	Modify	Register test module

Implementation Plan

1. Create Quick Service RPC Handler — new quick_service.rs with all 7 handlers
2. Register in RPC Dispatcher — add module + 7 match arms to mod.rs
3. Update OpenRPC JSON Spec — add method definitions to openrpc.json
4. Update Human-Readable Docs — add Quick Service section to openrpc.md
5. Create Quick Service Spec Doc — docs/quick_service_spec.md
6. Add Integration Tests — test all 7 methods
7. Build & Verify — cargo build + cargo test

Acceptance Criteria

• quick_service.set creates both action ({name}_action) and service in one call
• quick_service.get returns quick service definition
• quick_service.list returns only quick services
• quick_service.delete removes both service and action
• quick_service.start/stop/status work correctly
• All 7 methods in openrpc.json
• Docs updated with new methods
• docs/quick_service_spec.md exists
• SDK auto-generates client methods
• cargo build --workspace and cargo test --workspace succeed

## Implementation Spec for Issue #1: Quick Service OpenRPC Interface ### Objective Add a `quick_service` RPC namespace that provides a simplified interface for managing single-action services. A quick_service bundles a service definition and its single action into one atomic operation: `quick_service.set` creates both the action (named `{name}_action`) and the service (referencing that action) in a single call. ### Requirements - Add 7 new RPC methods under the `quick_service` namespace: - `quick_service.set` — create/update a quick service (creates both action + service atomically) - `quick_service.list` — list all quick services - `quick_service.delete` — delete a quick service and its associated action - `quick_service.get` — get a quick service definition - `quick_service.start` — start a quick service - `quick_service.stop` — stop a quick service - `quick_service.status` — get quick service status - `quick_service.set` takes: `name`, `cmd`, plus optional fields (interpreter, env, dir, timeout_ms, etc.) - Action naming convention: `{name}_action` for easy cleanup - `quick_service.delete` removes both the service and its prefixed action - All methods appear in `openrpc.json`, docs, and auto-generated SDK client - A `docs/quick_service_spec.md` specification document is created - No new DB tables — reuses existing `actions` and `services` tables ### Files to Modify/Create | File | Action | Description | |------|--------|-------------| | `crates/hero_proc_server/src/rpc/quick_service.rs` | **Create** | RPC handler module for all 7 methods | | `crates/hero_proc_server/src/rpc/mod.rs` | **Modify** | Register module and add dispatch arms | | `crates/hero_proc_server/openrpc.json` | **Modify** | Add 7 method definitions | | `docs/hero_proc_openrpc/openrpc.md` | **Modify** | Add Quick Service section | | `docs/quick_service_spec.md` | **Create** | Specification document | | `crates/hero_proc_integration_test/src/tests/quick_services.rs` | **Create** | Integration tests | | `crates/hero_proc_integration_test/src/tests/mod.rs` | **Modify** | Register test module | ### Implementation Plan 1. **Create Quick Service RPC Handler** — new `quick_service.rs` with all 7 handlers 2. **Register in RPC Dispatcher** — add module + 7 match arms to `mod.rs` 3. **Update OpenRPC JSON Spec** — add method definitions to `openrpc.json` 4. **Update Human-Readable Docs** — add Quick Service section to `openrpc.md` 5. **Create Quick Service Spec Doc** — `docs/quick_service_spec.md` 6. **Add Integration Tests** — test all 7 methods 7. **Build & Verify** — `cargo build` + `cargo test` ### Acceptance Criteria - [ ] `quick_service.set` creates both action (`{name}_action`) and service in one call - [ ] `quick_service.get` returns quick service definition - [ ] `quick_service.list` returns only quick services - [ ] `quick_service.delete` removes both service and action - [ ] `quick_service.start/stop/status` work correctly - [ ] All 7 methods in `openrpc.json` - [ ] Docs updated with new methods - [ ] `docs/quick_service_spec.md` exists - [ ] SDK auto-generates client methods - [ ] `cargo build --workspace` and `cargo test --workspace` succeed

despiegk commented 2026-03-19 06:15:39 +00:00

Author

Owner

Copy link

Updated Spec: Quick Service RPC Schemas (In/Out)

New Schema: QuickServiceParams

{
  "QuickServiceParams": {
    "type": "object",
    "required": ["name", "cmd"],
    "properties": {
      "name":            { "type": "string", "description": "Quick service name (also becomes the service name)" },
      "cmd":             { "type": "string", "description": "Script/command to execute (becomes action.script)" },
      "interpreter":     { "type": "string", "enum": ["bash","sh","rhai","python3","bun","node","exec"], "default": "bash" },
      "dir":             { "type": "string", "description": "Working directory" },
      "env":             { "type": "object", "additionalProperties": { "type": "string" }, "description": "Environment variables" },
      "timeout_ms":      { "type": "integer", "default": 0, "description": "Execution timeout (0 = none)" },
      "stop_signal":     { "type": "string", "default": "SIGTERM" },
      "stop_timeout_ms": { "type": "integer", "default": 10000 },
      "description":     { "type": "string", "description": "Human-readable description" },
      "context":         { "type": "string", "default": "core" }
    }
  }
}

Internal mapping: quick_service.set(params) creates:

• Action: name = "{params.name}_action", script = params.cmd, plus interpreter/dir/env/timeout/stop fields
• Service: name = params.name, actions = ["{params.name}_action"], status = "start"

---

Method Schemas

quick_service.set — Create or update a quick service

Params (in):

Name	Type	Required	Default	Description
name	string	yes	—	Quick service name
cmd	string	yes	—	Script/command to execute
interpreter	string	no	"bash"	bash|sh|rhai|python3|bun|node|exec
dir	string	no	—	Working directory
env	object	no	—	Environment variables {key: value}
timeout_ms	int	no	0	Execution timeout in ms (0 = none)
stop_signal	string	no	"SIGTERM"	Signal to send on stop
stop_timeout_ms	int	no	10000	Grace period before SIGKILL
description	string	no	—	Human-readable description
context	string	no	"core"	Context namespace

Result (out): OkResponse

{ "ok": true }

---

quick_service.get — Get a quick service definition

Params (in):

Name	Type	Required	Default
name	string	yes	—
context	string	no	"core"

Result (out): QuickServiceInfo

{
  "name": "myservice",
  "cmd": "echo hello",
  "interpreter": "bash",
  "dir": "",
  "env": {},
  "timeout_ms": 0,
  "stop_signal": "SIGTERM",
  "stop_timeout_ms": 10000,
  "description": "",
  "context": "core",
  "action_name": "myservice_action"
}

---

quick_service.list — List all quick services

Params (in):

Name	Type	Required	Default
context	string	no	—

Result (out):

{
  "value": [
    {
      "name": "myservice",
      "cmd": "echo hello",
      "interpreter": "bash",
      "description": "",
      "context": "core",
      "action_name": "myservice_action"
    }
  ]
}

---

quick_service.delete — Delete a quick service and its action

Params (in):

Name	Type	Required	Default
name	string	yes	—
context	string	no	"core"

Result (out): OkResponse

{ "ok": true }

Deletes both the service (name) and its action ({name}_action).

---

quick_service.start — Start a quick service

Params (in):

Name	Type	Required	Default
name	string	yes	—
context	string	no	"core"

Result (out): OkResponse

{ "ok": true }

Delegates to service.start internally.

---

quick_service.stop — Stop a quick service

Params (in):

Name	Type	Required	Default
name	string	yes	—
context	string	no	"core"

Result (out): OkResponse

{ "ok": true }

Delegates to service.stop internally.

---

quick_service.status — Get quick service status

Params (in):

Name	Type	Required	Default
name	string	yes	—
context	string	no	"core"

Result (out): ServiceStatus

{
  "name": "myservice",
  "state": "running",
  "pid": 12345,
  "restarts": 0
}

States: inactive | blocked | starting | running | stopping | success | exited | failed

Delegates to service.status internally.

## Updated Spec: Quick Service RPC Schemas (In/Out) ### New Schema: `QuickServiceParams` ```json { "QuickServiceParams": { "type": "object", "required": ["name", "cmd"], "properties": { "name": { "type": "string", "description": "Quick service name (also becomes the service name)" }, "cmd": { "type": "string", "description": "Script/command to execute (becomes action.script)" }, "interpreter": { "type": "string", "enum": ["bash","sh","rhai","python3","bun","node","exec"], "default": "bash" }, "dir": { "type": "string", "description": "Working directory" }, "env": { "type": "object", "additionalProperties": { "type": "string" }, "description": "Environment variables" }, "timeout_ms": { "type": "integer", "default": 0, "description": "Execution timeout (0 = none)" }, "stop_signal": { "type": "string", "default": "SIGTERM" }, "stop_timeout_ms": { "type": "integer", "default": 10000 }, "description": { "type": "string", "description": "Human-readable description" }, "context": { "type": "string", "default": "core" } } } } ``` **Internal mapping**: `quick_service.set(params)` creates: - Action: `name = "{params.name}_action"`, `script = params.cmd`, plus interpreter/dir/env/timeout/stop fields - Service: `name = params.name`, `actions = ["{params.name}_action"]`, `status = "start"` --- ### Method Schemas #### `quick_service.set` — Create or update a quick service **Params (in)**: | Name | Type | Required | Default | Description | |------|------|----------|---------|-------------| | `name` | string | yes | — | Quick service name | | `cmd` | string | yes | — | Script/command to execute | | `interpreter` | string | no | `"bash"` | `bash\|sh\|rhai\|python3\|bun\|node\|exec` | | `dir` | string | no | — | Working directory | | `env` | object | no | — | Environment variables `{key: value}` | | `timeout_ms` | int | no | `0` | Execution timeout in ms (0 = none) | | `stop_signal` | string | no | `"SIGTERM"` | Signal to send on stop | | `stop_timeout_ms` | int | no | `10000` | Grace period before SIGKILL | | `description` | string | no | — | Human-readable description | | `context` | string | no | `"core"` | Context namespace | **Result (out)**: `OkResponse` ```json { "ok": true } ``` --- #### `quick_service.get` — Get a quick service definition **Params (in)**: | Name | Type | Required | Default | |------|------|----------|--------| | `name` | string | yes | — | | `context` | string | no | `"core"` | **Result (out)**: `QuickServiceInfo` ```json { "name": "myservice", "cmd": "echo hello", "interpreter": "bash", "dir": "", "env": {}, "timeout_ms": 0, "stop_signal": "SIGTERM", "stop_timeout_ms": 10000, "description": "", "context": "core", "action_name": "myservice_action" } ``` --- #### `quick_service.list` — List all quick services **Params (in)**: | Name | Type | Required | Default | |------|------|----------|--------| | `context` | string | no | — | **Result (out)**: ```json { "value": [ { "name": "myservice", "cmd": "echo hello", "interpreter": "bash", "description": "", "context": "core", "action_name": "myservice_action" } ] } ``` --- #### `quick_service.delete` — Delete a quick service and its action **Params (in)**: | Name | Type | Required | Default | |------|------|----------|--------| | `name` | string | yes | — | | `context` | string | no | `"core"` | **Result (out)**: `OkResponse` ```json { "ok": true } ``` Deletes both the service (`name`) and its action (`{name}_action`). --- #### `quick_service.start` — Start a quick service **Params (in)**: | Name | Type | Required | Default | |------|------|----------|--------| | `name` | string | yes | — | | `context` | string | no | `"core"` | **Result (out)**: `OkResponse` ```json { "ok": true } ``` Delegates to `service.start` internally. --- #### `quick_service.stop` — Stop a quick service **Params (in)**: | Name | Type | Required | Default | |------|------|----------|--------| | `name` | string | yes | — | | `context` | string | no | `"core"` | **Result (out)**: `OkResponse` ```json { "ok": true } ``` Delegates to `service.stop` internally. --- #### `quick_service.status` — Get quick service status **Params (in)**: | Name | Type | Required | Default | |------|------|----------|--------| | `name` | string | yes | — | | `context` | string | no | `"core"` | **Result (out)**: `ServiceStatus` ```json { "name": "myservice", "state": "running", "pid": 12345, "restarts": 0 } ``` States: `inactive | blocked | starting | running | stopping | success | exited | failed` Delegates to `service.status` internally.

despiegk commented 2026-03-19 06:19:59 +00:00

Author

Owner

Copy link

Updated Spec v3: Schema Clarifications

1. env field — key/value map

env is a dictionary (map) of string keys to string values. In JSON:

{
  "env": {
    "DATABASE_URL": "postgres://localhost/mydb",
    "LOG_LEVEL": "debug",
    "PORT": "8080"
  }
}

OpenRPC schema:

"env": {
  "type": "object",
  "additionalProperties": { "type": "string" },
  "description": "Key/value map of environment variables. Keys and values are both strings."
}

2. Dependencies between quick services

Quick services support inter-service dependencies via the depends_on field. Since quick services are regular services under the hood, this maps directly to the existing DependencyDef system.

New field in quick_service.set params:

Name	Type	Required	Default	Description
depends_on	object	no	{}	Inter-service dependencies

depends_on structure:

{
  "depends_on": {
    "requires": ["database", "redis"],
    "after": ["logger"],
    "wants": ["metrics"],
    "conflicts": ["old-api"]
  }
}

Sub-field	Type	Description
requires	string[]	Hard dependency — only start if these services are running
after	string[]	Ordering — start after these services (regardless of outcome)
wants	string[]	Soft dependency — prefer these to be up, don't block if they fail
conflicts	string[]	Cannot run alongside these services

All sub-fields reference service names (including other quick service names).

---

Full Updated quick_service.set Params

Name	Type	Required	Default	Description
name	string	yes	—	Quick service name
cmd	string	yes	—	Script/command to execute
interpreter	string	no	"bash"	bash|sh|rhai|python3|bun|node|exec
dir	string	no	—	Working directory
env	map<string,string>	no	{}	Environment variables as key/value pairs
timeout_ms	int	no	0	Execution timeout in ms (0 = none)
stop_signal	string	no	"SIGTERM"	Signal to send on stop
stop_timeout_ms	int	no	10000	Grace period before SIGKILL (ms)
description	string	no	—	Human-readable description
context	string	no	"core"	Context namespace
depends_on	DependencyDef	no	{}	Inter-service dependencies (requires/after/wants/conflicts)

Example: quick_service.set with dependencies

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "quick_service.set",
  "params": {
    "name": "api-server",
    "cmd": "node server.js",
    "interpreter": "exec",
    "dir": "/opt/api",
    "env": {
      "DATABASE_URL": "postgres://localhost/mydb",
      "PORT": "3000"
    },
    "depends_on": {
      "requires": ["database"],
      "after": ["logger"]
    }
  }
}

Result:

{ "jsonrpc": "2.0", "id": 1, "result": { "ok": true } }

This creates:

• Action: api-server_action (script=node server.js, interpreter=exec, dir=/opt/api, env=...)
• Service: api-server (actions=[api-server_action], dependencies={requires:[database], after:[logger]})

## Updated Spec v3: Schema Clarifications ### 1. `env` field — key/value map `env` is a dictionary (map) of string keys to string values. In JSON: ```json { "env": { "DATABASE_URL": "postgres://localhost/mydb", "LOG_LEVEL": "debug", "PORT": "8080" } } ``` OpenRPC schema: ```json "env": { "type": "object", "additionalProperties": { "type": "string" }, "description": "Key/value map of environment variables. Keys and values are both strings." } ``` ### 2. Dependencies between quick services Quick services support inter-service dependencies via the `depends_on` field. Since quick services are regular services under the hood, this maps directly to the existing `DependencyDef` system. **New field in `quick_service.set` params:** | Name | Type | Required | Default | Description | |------|------|----------|---------|-------------| | `depends_on` | object | no | `{}` | Inter-service dependencies | `depends_on` structure: ```json { "depends_on": { "requires": ["database", "redis"], "after": ["logger"], "wants": ["metrics"], "conflicts": ["old-api"] } } ``` | Sub-field | Type | Description | |-----------|------|-------------| | `requires` | string[] | Hard dependency — only start if these services are running | | `after` | string[] | Ordering — start after these services (regardless of outcome) | | `wants` | string[] | Soft dependency — prefer these to be up, don't block if they fail | | `conflicts` | string[] | Cannot run alongside these services | All sub-fields reference service names (including other quick service names). --- ### Full Updated `quick_service.set` Params | Name | Type | Required | Default | Description | |------|------|----------|---------|-------------| | `name` | string | **yes** | — | Quick service name | | `cmd` | string | **yes** | — | Script/command to execute | | `interpreter` | string | no | `"bash"` | `bash\|sh\|rhai\|python3\|bun\|node\|exec` | | `dir` | string | no | — | Working directory | | `env` | map\<string,string\> | no | `{}` | Environment variables as key/value pairs | | `timeout_ms` | int | no | `0` | Execution timeout in ms (0 = none) | | `stop_signal` | string | no | `"SIGTERM"` | Signal to send on stop | | `stop_timeout_ms` | int | no | `10000` | Grace period before SIGKILL (ms) | | `description` | string | no | — | Human-readable description | | `context` | string | no | `"core"` | Context namespace | | `depends_on` | DependencyDef | no | `{}` | Inter-service dependencies (requires/after/wants/conflicts) | ### Example: quick_service.set with dependencies ```json { "jsonrpc": "2.0", "id": 1, "method": "quick_service.set", "params": { "name": "api-server", "cmd": "node server.js", "interpreter": "exec", "dir": "/opt/api", "env": { "DATABASE_URL": "postgres://localhost/mydb", "PORT": "3000" }, "depends_on": { "requires": ["database"], "after": ["logger"] } } } ``` **Result:** ```json { "jsonrpc": "2.0", "id": 1, "result": { "ok": true } } ``` This creates: - Action: `api-server_action` (script=`node server.js`, interpreter=exec, dir=/opt/api, env=...) - Service: `api-server` (actions=[`api-server_action`], dependencies={requires:[`database`], after:[`logger`]})

despiegk commented 2026-03-19 06:51:52 +00:00

Author

Owner

Copy link

Test Results

• cargo build --workspace: OK
• cargo test -p hero_proc_lib: 137 passed, 0 failed
• cargo test -p hero_proc_server: OK (0 unit tests, all compile-time checks pass)
• Pre-existing failures (unrelated to quick_service): 3 CLI help tests for unimplemented commands (config diff, config import, reload), 1 flaky transport test in integration examples

## Test Results - **cargo build --workspace**: OK - **cargo test -p hero_proc_lib**: 137 passed, 0 failed - **cargo test -p hero_proc_server**: OK (0 unit tests, all compile-time checks pass) - **Pre-existing failures** (unrelated to quick_service): 3 CLI help tests for unimplemented commands (config diff, config import, reload), 1 flaky transport test in integration examples

despiegk commented 2026-03-19 06:51:52 +00:00

Author

Owner

Copy link

Implementation Summary

Changes Made

New files:

• crates/hero_proc_server/src/rpc/quick_service.rs — 7 RPC handler functions for the quick_service namespace
• docs/quick_service_spec.md — Full specification document with API reference, examples, and dependency docs

Modified files:

• crates/hero_proc_server/src/rpc/mod.rs — Registered quick_service module + 7 dispatch arms
• crates/hero_proc_server/openrpc.json — Added 7 method definitions + QuickServiceInfo schema
• docs/hero_proc_openrpc/openrpc.md — Added Quick Service section (7 methods), QuickServiceInfo schema, updated method count from 67 to 74

Features

• quick_service.set atomically creates both action ({name}_action) and service in one call
• Full env support as key/value map (map<string,string>)
• Inter-service dependencies via depends_on (requires/after/wants/conflicts)
• quick_service.list filters to only quick services using naming convention
• quick_service.delete removes both action and service atomically
• start/stop/status delegate to existing service handlers

## Implementation Summary ### Changes Made **New files:** - `crates/hero_proc_server/src/rpc/quick_service.rs` — 7 RPC handler functions for the `quick_service` namespace - `docs/quick_service_spec.md` — Full specification document with API reference, examples, and dependency docs **Modified files:** - `crates/hero_proc_server/src/rpc/mod.rs` — Registered `quick_service` module + 7 dispatch arms - `crates/hero_proc_server/openrpc.json` — Added 7 method definitions + `QuickServiceInfo` schema - `docs/hero_proc_openrpc/openrpc.md` — Added Quick Service section (7 methods), `QuickServiceInfo` schema, updated method count from 67 to 74 ### Features - `quick_service.set` atomically creates both action (`{name}_action`) and service in one call - Full `env` support as key/value map (`map<string,string>`) - Inter-service dependencies via `depends_on` (requires/after/wants/conflicts) - `quick_service.list` filters to only quick services using naming convention - `quick_service.delete` removes both action and service atomically - `start/stop/status` delegate to existing service handlers

despiegk commented 2026-03-19 06:59:10 +00:00

Author

Owner

Copy link

Implementation committed: 9817253

Browse: 9817253

Implementation committed: `9817253` Browse: https://forge.ourworld.tf/lhumina_code/hero_proc/commit/9817253

despiegk commented 2026-03-19 07:06:42 +00:00

Author

Owner

Copy link

Integration Test Results

Overall: 148 passed, 14 failed, 162 total

Quick Service Tests: 17/17 PASS

Test	Status
set_creates_quick_service	PASS
get_returns_all_fields	PASS
get_nonexistent_returns_error	PASS
set_with_env_vars	PASS
set_with_dependencies	PASS
list_includes_quick_services	PASS
list_excludes_regular_services	PASS
set_updates_existing_quick_service	PASS
delete_removes_service_and_action	PASS
delete_nonexistent_returns_error	PASS
underlying_action_accessible_via_action_get	PASS
underlying_service_accessible_via_service_get	PASS
status_of_idle_quick_service	PASS
start_and_stop_quick_service	PASS
context_isolation	PASS
set_missing_name_returns_error	PASS
set_missing_cmd_returns_error	PASS

Pre-existing failures (14, unrelated to quick_service)

• services (3): SDK Vec<String> deserialization issue with service.list wrapper
• jobs (4): SDK deserialization issue with log endpoints returning wrapped arrays
• schedule (7): Timing-sensitive cron/interval tests that timeout in CI

All quick_service functionality verified: CRUD, env vars, dependencies, lifecycle (start/stop/status), context isolation, param validation, and underlying action/service accessibility.

Commit: 9fe0b69

## Integration Test Results **Overall: 148 passed, 14 failed, 162 total** ### Quick Service Tests: 17/17 PASS | Test | Status | |------|--------| | `set_creates_quick_service` | PASS | | `get_returns_all_fields` | PASS | | `get_nonexistent_returns_error` | PASS | | `set_with_env_vars` | PASS | | `set_with_dependencies` | PASS | | `list_includes_quick_services` | PASS | | `list_excludes_regular_services` | PASS | | `set_updates_existing_quick_service` | PASS | | `delete_removes_service_and_action` | PASS | | `delete_nonexistent_returns_error` | PASS | | `underlying_action_accessible_via_action_get` | PASS | | `underlying_service_accessible_via_service_get` | PASS | | `status_of_idle_quick_service` | PASS | | `start_and_stop_quick_service` | PASS | | `context_isolation` | PASS | | `set_missing_name_returns_error` | PASS | | `set_missing_cmd_returns_error` | PASS | ### Pre-existing failures (14, unrelated to quick_service) - **services** (3): SDK `Vec<String>` deserialization issue with `service.list` wrapper - **jobs** (4): SDK deserialization issue with log endpoints returning wrapped arrays - **schedule** (7): Timing-sensitive cron/interval tests that timeout in CI All quick_service functionality verified: CRUD, env vars, dependencies, lifecycle (start/stop/status), context isolation, param validation, and underlying action/service accessibility. Commit: `9fe0b69`

despiegk closed this issue 2026-03-19 07:16:45 +00:00

despiegk referenced this issue from a commit 2026-03-19 09:47:13 +00:00

feat(rpc): add quick_service namespace with 7 RPC methods

despiegk referenced this issue from a commit 2026-03-19 09:47:13 +00:00

test: add 16 integration tests for quick_service RPC namespace

despiegk referenced this issue 2026-04-28 05:34:44 +00:00

services not shown properly #57

despiegk referenced this issue 2026-04-28 06:02:03 +00:00

services not shown properly #57

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

development

development_refactor

development_16

development_mik2

main

v0.4.4

v0.4.1

v0.1.1

Labels

Clear labels   

prio_critical

  

prio_low

  

type_bug

  

type_contact

  

type_issue

  

type_lead

  

type_question

  

type_story

  

type_task

No labels

prio_critical

prio_low

type_bug

type_contact

type_issue

type_lead

type_question

type_story

type_task

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

lhumina_code/hero_proc#1

No description provided.