mirror of
https://github.com/agentscope-ai/ReMe.git
synced 2026-11-06 07:51:11 +00:00
TypertRemoteService registers itself under the constructor key, so `super(ctx, remeEnv)` collided with the already-provided `remeEnv` manager: the gateway plugin failed activation (its async rejection was logged only), leaving every /api/remeEnv/* call with HTTP 404. Register the service as `remeEnvGateway` and keep the wire namespace `remeEnv`, which is what the client calls. Add a real-cordis regression test that mounts the gateway inside the same isolated realm and asserts the binding, the namespace, and the SRC-parsed `input` parameter. Also show the interpreter hint on detection failure so an empty list never leaves the tab without guidance. |
||
|---|---|---|
| .. | ||
| bundle.test.mjs | ||
| client-settings.test.mjs | ||
| client.test.mjs | ||
| config.test.mjs | ||
| dsh-index.test.mjs | ||
| dsh-tools.test.mjs | ||
| env-detect.test.mjs | ||
| env-gateway.test.mjs | ||
| env-reme.test.mjs | ||
| env-service.test.mjs | ||
| env-workspace.test.mjs | ||
| frontmatter.test.mjs | ||
| messages.test.mjs | ||
| outbox.test.mjs | ||
| runtime.test.mjs | ||
| scheduler.test.mjs | ||