Skip to content

Fix lifecycle teardown, config drift and unbounded atom creation - #20

Merged
benoitc merged 2 commits into
mainfrom
fix/phase-0-lifecycle-config
Sep 21, 2026
Merged

benoitc merged 2 commits into
mainfrom
fix/phase-0-lifecycle-config

Conversation

@benoitc

@benoitc benoitc commented Sep 21, 2026 •

Copy link
Copy Markdown
Owner

Groundwork before the durable execution work.

Restarting hornbeam in one VM did not work, presence from Python did nothing at all, and two inputs reachable from Python were unbounded. Config had drifted across three default maps.

  • stop/0 releases what start/2 set up
  • register the three Python-called functions that were missing
  • presence keeps and releases its monitor refs
  • dist requires existing atoms, caps node names
  • defaults/0 is the single config source; four dead options removed
  • default port 8642, since 8000 collides with most dev servers

Two judgment calls worth a look: this deletes two unreferenced runner modules, and leaves the Python shims unpackaged, since their module names are the public API.

- stop/0 releases what start/2 set up, so restart in one VM works
- register hornbeam_presence, _channel and _channel_registry for Python
- keep and release presence monitor refs
- dist requires existing atoms for module/function, caps node names
- one config defaults map instead of three, drop four dead options
- default port 8000 to 8642
@benoitc
benoitc merged commit 19f8993 into main Sep 21, 2026
14 checks passed
@benoitc
benoitc deleted the fix/phase-0-lifecycle-config branch September 21, 2026 17:06
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