Skip to content

fix disconnect typo in connection return tuple#267

Open
malcolmsgc wants to merge 4 commits into
geldata:masterfrom
malcolmsgc:master
Open

fix disconnect typo in connection return tuple#267
malcolmsgc wants to merge 4 commits into
geldata:masterfrom
malcolmsgc:master

Conversation

@malcolmsgc
Copy link
Copy Markdown

typo in return tuple was causing clause match error.

malcolmsgc and others added 4 commits December 5, 2025 13:18
Connections are now created eagerly during pool init instead of lazily on
first checkout, eliminating cold-start timeouts. Defaults to 1 connection,
clamped to max_concurrency when set. Also fixes the max_allowed_connections
calculation to explicitly handle nil concurrency values.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The server can send LogMessage notifications (e.g. "requested to stop;
disconnecting now") during ping. Previously this crashed the connection
because handle_ping_message had no LogMessage clause, causing a cascade:
the disconnect callback tried to send Terminate on a closing socket,
returned a non-:ok value, and DBConnection's :ok = apply() crashed with
MatchError.

Fix both issues: consume LogMessages during ping (matching the pattern
used by receive_message elsewhere), and ensure all disconnect clauses
explicitly return :ok as DBConnection requires.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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