You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the requestTLS call fails, the returned future will be failed. This will send us down an error path, meaning the PostgresConnection will never make it to user code. However, the PostgresConnection is not closed on that path: nothing in here closes the connection. This triggers the assert in deinit:
A client requesting TLS will hit this branch of code:
postgres-nio/Sources/PostgresNIO/Connection/PostgresConnection+Connect.swift
Lines 23 to 33 in 2334eab
If the
requestTLS
call fails, the returned future will be failed. This will send us down an error path, meaning thePostgresConnection
will never make it to user code. However, thePostgresConnection
is not closed on that path: nothing in here closes the connection. This triggers theassert
indeinit
:postgres-nio/Sources/PostgresNIO/Connection/PostgresConnection.swift
Lines 33 to 35 in 2334eab
This should be handled more gracefully, by closing the connection on error.
The text was updated successfully, but these errors were encountered: