[
https://issues.apache.org/jira/browse/CASSANDRA-16474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17295265#comment-17295265
]
Sam Tunnicliffe commented on CASSANDRA-16474:
---------------------------------------------
New docker images have been published, so I've updated the circle config files.
*Patches*
* [2.2|https://github.com/beobal/cassandra/tree/16474-2.2]
* [3.0|https://github.com/beobal/cassandra/tree/16474-3.0]
* [3.11|https://github.com/beobal/cassandra/tree/16474-3.11]
* [trunk|https://github.com/beobal/cassandra/tree/16474-trunk] (also includes
driver update)
I've also opened CASSANDRA-16483 for the python upgrade test failure, along
with a couple of python cql tests with the same proximate cause.
> Multiple python dtest failures after promoting protocol v5 from beta
> --------------------------------------------------------------------
>
> Key: CASSANDRA-16474
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16474
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Client
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Normal
> Labels: protocolv5
> Fix For: 4.0-beta
>
>
> After making v5 the default for connections where a preferred protocol
> version is not specified, a number of python dtests are failing in CI
> environments.
> The issue appears to be with how the driver handles cases where the bytes
> read from the client socket doesn't constitute a complete frame (or to be
> more specific, the read buffer is exhausted whilst in the middle of reading a
> frame).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
