fix: bind hero_db sockets under hero_db/ subdir (0.3.3 backport) #35

Closed

zaelgohary wants to merge 2 commits from development_fix_socket_layout into development

zaelgohary commented

2026-05-20 11:01:48 +00:00

Member

Summary

hero_db_server now writes its sockets directly at hero_db/rpc.sock and hero_db/resp.sock, matching hero_proc 0.4.4+ and hero_slides 0.6.0 expectations. No more deploy-time symlink to bridge layouts.

Closes #34 (server side). Symptom #1 in the issue (CLI hitting hero_proc_server.sock) is owned by hero_proc_sdk; deploy keeps that symlink until upstream lands.

Changes

Moved server socket to hero_db/rpc.sock
Moved RESP socket to hero_db/resp.sock
Bumped to 0.3.3

Test Results

Deployed to slides VM; gateway + /rpc both HTTP 200, hero_db_server v0.3.3 healthy.

## Summary hero_db_server now writes its sockets directly at `hero_db/rpc.sock` and `hero_db/resp.sock`, matching hero_proc 0.4.4+ and hero_slides 0.6.0 expectations. No more deploy-time symlink to bridge layouts. ## Related Issue Closes #34 (server side). Symptom #1 in the issue (CLI hitting `hero_proc_server.sock`) is owned by hero_proc_sdk; deploy keeps that symlink until upstream lands. ## Changes - Moved server socket to hero_db/rpc.sock - Moved RESP socket to hero_db/resp.sock - Bumped to 0.3.3 ## Test Results Deployed to slides VM; gateway + /rpc both HTTP 200, hero_db_server v0.3.3 healthy.

zaelgohary added 1 commit

2026-05-20 11:01:49 +00:00

fix(server): bind sockets under hero_db/ subdir to match current layout

CI / cargo test (pull_request) Failing after 3s

Details

CI / cargo check + clippy (pull_request) Successful in 1m23s

Details

Build and Test / build (pull_request) Successful in 3m58s

Details

697705ed87

Backport for 0.3.3: hero_db_server now writes hero_db/rpc.sock and hero_db/resp.sock directly. Downstreams (hero_proc 0.4.4+, hero_slides 0.6.0) no longer need symlink workarounds.

zaelgohary added 1 commit

2026-05-20 12:05:50 +00:00

ci: retrigger after flaky checkout step

CI / cargo check + clippy (pull_request) Successful in 1m25s

Details

CI / cargo test (pull_request) Successful in 1m45s

Details

Build and Test / build (pull_request) Successful in 3m30s

Details

bd90e08d6f