[
https://issues.apache.org/jira/browse/CASSANDRA-16474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17296139#comment-17296139
]
Sam Tunnicliffe commented on CASSANDRA-16474:
---------------------------------------------
Hey Ekaterina, sorry about that.
I updated the template and regenerated the specific yaml files as per the
readme (I'm not sure if that's outdated now though). I looks like the
{{utests_system_keyspace_directory}} job was added directly to the
{{config.yml.XYZ}} files, so it got lost by my doing that. I completely
overlooked the {{MIDRES}} file sorry. I'll take care offiling a radar and
restoring things to how they were previously.
> 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-beta5, 4.0
>
>
> 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]
