Repository navigation
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (5)
💤 Files with no reviewable changes (3)
Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe ChangesServer release records
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Other Suggested reviewers: Merge Risk: ⚪ Minimal · up to This publishes the server’s 0.11.0 release with all three changesets reflected in its changelog; no other package release record is affected. No actionable merge risk remains. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Package Changes Through 0bc7386No changes. Add a change file through the GitHub UI by following this link. Read about change files or the docs at github.com/jbolda/covector |
Version Updates
Merging this PR will release new versions of the following packages based on your change files.
@simulacrum/server
[0.11.0]
Enhancements
@simulacrum/serverprocess reaper #381 by @jbolda) AddlaunchGraphoption insimulationCLIto allow a user to "wrap" the service graph process. For example, a team using only linux could opt to wrap the graph inunsharefor more direct kernel protections from zombie processes.@simulacrum/serverprocess reaper #381 by @jbolda) Add a new reaper process. We hand it the pids of processes when they start and when they shutdown. If the main service graph gets hard killed and the reaper see it lost the parent, the reaper will kill all (now) zombied processes and shut itself down. This is primarily in place to prevent bad shutdown sequences leaving zombie processes.Bug Fixes
@simulacrum/serverprocess reaper #381 by @jbolda) Allow the /stop endpoint even if the service graph is not backgrounded. Allows one terminal to start but another to stop (or to use the idea of backgrounding through another function such as in tmux, etc.).Summary by CodeRabbit
/stopendpoint now works when the service graph runs in the foreground.@simulacrum/serverto version 0.11.0.