WIP: fix: use std::sync::RwLock in UnifiedServerBuilder to avoid panic #19
No reviewers
Labels
No labels
prio_critical
prio_low
type_bug
type_contact
type_issue
type_lead
type_question
type_story
type_task
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/hero_rpc!19
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "development_13"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
tokio::sync::RwLockwithstd::sync::RwLockforUnifiedServerBuilder.entriesblocking_write()panics when called inside a tokio runtime;write().unwrap()on std RwLock works correctlyserve()now acceptsArc<AsyncRwLock<ContextRegistry>>(aliased to avoid ambiguity)Test plan
cargo build -p hero_rpc_servercompiles cleanmake example(recipe_server) no longer panics on startup- Fix discovery manifest field name: socket_type → socket (per hero_sockets spec) - Add .interpreter("exec") to lifecycle action builder (per hero_proc_sdk spec) - Update recipe_server examples to use OServer::run_cli() with HeroLifecycle for hero_proc integration (start/stop/status/logs/serve subcommands) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>Merged via git push to development branch. Closing PR.
Pull request closed