Unhandled backend message was encountered: L -> 3318, C -> 57014,

[matthughes]

: ?  An unhandled backend message was encountered
: ?    at /home/runner/work/skunk/skunk/modules/core/shared/src/main/scala/net/protocol/Close.scala:41
: ?
: ?    Message: ErrorResponse(F -> postgres.c, M -> canceling statement due to
: ?             statement timeout, V -> ERROR, L -> 3318, C -> 57014, R ->
: ?             ProcessInterrupts, S -> ERROR
: ?
: ?  This is an implementation error in Skunk.
: ?  Please report a bug with the full contents of this error message.

: skunk.exception.ProtocolError: ErrorResponse(F -> postgres.c, M -> canceling statement due to statement timeout, V -> ERROR, L -> 3318, C -> 57014, R>

[matthughes]

      def close(message: CloseMessage): F[Unit] =
        for {
          _ <- send(message)
          _ <- send(Flush)
          _ <- expect { case CloseComplete => }
        } yield ()

So Skunk went to close the connection but instead of getting a CloseComplete, it got a ErrorResponse?

[nigredo-tori]

Here:

The Close message closes an existing prepared statement or portal and releases resources. It is not an error to issue Close against a nonexistent statement or portal name. The response is normally CloseComplete, but could be ErrorResponse if some difficulty is encountered while releasing resources. Note that closing a prepared statement implicitly closes any open portals that were constructed from that statement.