Skip to content

fix: avoid IPC mode when isolation is none#9

Merged
Lojhan merged 2 commits intomainfrom
fix/isolation-none-execution-mode
Apr 2, 2026
Merged

fix: avoid IPC mode when isolation is none#9
Lojhan merged 2 commits intomainfrom
fix/isolation-none-execution-mode

Conversation

@Lojhan
Copy link
Copy Markdown
Collaborator

@Lojhan Lojhan commented Apr 2, 2026

Summary

  • derive shared resource execution mode from PluginContext.configs.isolation
  • run shared resources in-process for isolation: none and keep IPC behavior for process isolation
  • reset shared resource runtime during teardown so repeated poku(...) invocations do not leak state
  • add focused coverage for execution mode behavior and the isolation none integration path

What changed

  • wire sharedResources() setup to switch between process and in-process modes automatically
  • guard IPC setup and IPC-only request paths when running in-process
  • preserve method-call parity in in-process mode by returning async bound method wrappers
  • keep the newer codec/config support from main while layering the isolation-aware execution-mode fix on top
  • add test/unit/execution-mode.test.ts and extend the integration suite with an isolation none case

Validation

  • npm test

@Lojhan Lojhan merged commit a185f7d into main Apr 2, 2026
12 checks passed
@Lojhan Lojhan deleted the fix/isolation-none-execution-mode branch April 2, 2026 11:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant