Skip to content

Keep the DRb connection pool alive after socket errors - #57

Closed
OskarEichler wants to merge 1 commit into
ruby:masterfrom
OskarEichler:codex/connection-pool-errors
Closed

Keep the DRb connection pool alive after socket errors#57
OskarEichler wants to merge 1 commit into
ruby:masterfrom
OskarEichler:codex/connection-pool-errors

Conversation

@OskarEichler

Copy link
Copy Markdown

Contains stale-connection liveness and eviction-close errors inside the pool worker, closing broken entries when possible so later callers do not deadlock behind a dead worker.

Verified with the full 122-test / 547-assertion suite and focused stale/eviction error models.

@kou

kou commented Aug 30, 2026

Copy link
Copy Markdown
Member

Could you also share your real world problems instead of just opening auto generated PRs to many repositories?

@OskarEichler

Copy link
Copy Markdown
Author

This was generated from a broad dependency audit, not from a specific Songstats production incident. I can explain the hypothetical dead-worker path, but I cannot honestly provide a real-world failure that motivated it. That context is not strong enough for this change, so I am closing the PR.

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.

2 participants