[jira] [Updated] (CASSANDRA-15750) Upgrade Cassandra Java Driver to 4.6
[ https://issues.apache.org/jira/browse/CASSANDRA-15750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-15750: Resolution: Fixed Status: Resolved (was: Open) > Upgrade Cassandra Java Driver to 4.6 > > > Key: CASSANDRA-15750 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15750 > Project: Cassandra > Issue Type: Improvement > Components: Dependencies >Reporter: Eduard Tudenhoefner >Assignee: Eduard Tudenhoefner >Priority: Normal > Fix For: 5.x > > > After releasing C* 4.0 I think it would be a good idea to upgrade to the > latest Cassandra Java Driver that is being used internally. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16006) Parallelise Jenkins dtests
[ https://issues.apache.org/jira/browse/CASSANDRA-16006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-16006: Status: Ready to Commit (was: Review In Progress) > Parallelise Jenkins dtests > -- > > Key: CASSANDRA-16006 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16006 > Project: Cassandra > Issue Type: Improvement > Components: CI >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 4.0-rc > > > Currently dtests in Jenkins take ~10 hours. > Using the Jenkins Matrix plugin these jobs can be split into smaller lists of > dtests and run in parallel. This is the approach CircleCI takes. > This approach was > [trialed|https://github.com/apache/cassandra-builds/pull/29] with the > dtest-upgrade jobs (which are not yet part of the branch pipelines, and > haven't previously worked at all due to their duration). > In addition to the Matrix plugin, the Priority-Sorter and Matrix Reloaded > plugins also needed to be added. > The splits will occupy all executors, and multiple builds will lead to a long > build queue. More important builds (artifacts and unit tests) need a way to > be prioritised in such saturated situations. > Splits can fail for silly reasons (false-positive), like > [full|https://issues.apache.org/jira/browse/INFRA-19793] /tmp disks, or > [connectivity issues|https://issues.apache.org/jira/browse/INFRA-20107] > between the donated agent servers. The Matrix Reloaded plugin makes it easy > to rebuilt just those failed splits. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16006) Parallelise Jenkins dtests
[ https://issues.apache.org/jira/browse/CASSANDRA-16006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-16006: Reviewers: Eduard Tudenhoefner, Eduard Tudenhoefner (was: Eduard Tudenhoefner) Eduard Tudenhoefner, Eduard Tudenhoefner Status: Review In Progress (was: Patch Available) changes LGTM > Parallelise Jenkins dtests > -- > > Key: CASSANDRA-16006 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16006 > Project: Cassandra > Issue Type: Improvement > Components: CI >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 4.0-rc > > > Currently dtests in Jenkins take ~10 hours. > Using the Jenkins Matrix plugin these jobs can be split into smaller lists of > dtests and run in parallel. This is the approach CircleCI takes. > This approach was > [trialed|https://github.com/apache/cassandra-builds/pull/29] with the > dtest-upgrade jobs (which are not yet part of the branch pipelines, and > haven't previously worked at all due to their duration). > In addition to the Matrix plugin, the Priority-Sorter and Matrix Reloaded > plugins also needed to be added. > The splits will occupy all executors, and multiple builds will lead to a long > build queue. More important builds (artifacts and unit tests) need a way to > be prioritised in such saturated situations. > Splits can fail for silly reasons (false-positive), like > [full|https://issues.apache.org/jira/browse/INFRA-19793] /tmp disks, or > [connectivity issues|https://issues.apache.org/jira/browse/INFRA-20107] > between the donated agent servers. The Matrix Reloaded plugin makes it easy > to rebuilt just those failed splits. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15835) Upgrade-dtests on trunk not working in CircleCI
[
https://issues.apache.org/jira/browse/CASSANDRA-15835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17124754#comment-17124754
]
Eduard Tudenhoefner commented on CASSANDRA-15835:
-
reviewed all of the above PRs and changes LGTM. Waiting on final CI results now.
> Upgrade-dtests on trunk not working in CircleCI
> ---
>
> Key: CASSANDRA-15835
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15835
> Project: Cassandra
> Issue Type: Bug
> Components: CI, Test/dtest
>Reporter: Robert Stupp
>Assignee: Robert Stupp
>Priority: Normal
> Fix For: 4.0-alpha
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> ~3600 Upgrade-dtests are failing in CircleCI for trunk due to the missing
> {{JAVA8_HOME}} environment variable.
> Patching the Docker image is rather simple by creating a new image:
> {code}
> FROM nastra/cassandra-testing-ubuntu1910-java11-w-dependencies:20200406
> ENV JAVA8_HOME=/usr/lib/jvm/java-8-openjdk-amd64
> {code}
> Pushed the above to Docker hub as
> [snazy/cassandra-testing-ubuntu1910-java11-w-dependencies:202005261540|https://hub.docker.com/layers/snazy/cassandra-testing-ubuntu1910-java11-w-dependencies/202005261540/images/sha256-ac8a713be58694f095c491921e006c2d1a7823a3c23299e477198e2c93a6bbd7?context=explore]
> The size of the whole Docker image is a little concerning though (1.85G
> compressed), but that's out of the scope of this ticket.
> I'll prepare a patch soon-ish.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15835) Upgrade-dtests on trunk not working in CircleCI
[
https://issues.apache.org/jira/browse/CASSANDRA-15835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15835:
Reviewers: Eduard Tudenhoefner, Eduard Tudenhoefner (was: Eduard
Tudenhoefner)
Eduard Tudenhoefner, Eduard Tudenhoefner (was: Eduard
Tudenhoefner)
Status: Review In Progress (was: Patch Available)
> Upgrade-dtests on trunk not working in CircleCI
> ---
>
> Key: CASSANDRA-15835
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15835
> Project: Cassandra
> Issue Type: Bug
> Components: CI, Test/dtest
>Reporter: Robert Stupp
>Assignee: Robert Stupp
>Priority: Normal
> Fix For: 4.0-alpha
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> ~3600 Upgrade-dtests are failing in CircleCI for trunk due to the missing
> {{JAVA8_HOME}} environment variable.
> Patching the Docker image is rather simple by creating a new image:
> {code}
> FROM nastra/cassandra-testing-ubuntu1910-java11-w-dependencies:20200406
> ENV JAVA8_HOME=/usr/lib/jvm/java-8-openjdk-amd64
> {code}
> Pushed the above to Docker hub as
> [snazy/cassandra-testing-ubuntu1910-java11-w-dependencies:202005261540|https://hub.docker.com/layers/snazy/cassandra-testing-ubuntu1910-java11-w-dependencies/202005261540/images/sha256-ac8a713be58694f095c491921e006c2d1a7823a3c23299e477198e2c93a6bbd7?context=explore]
> The size of the whole Docker image is a little concerning though (1.85G
> compressed), but that's out of the scope of this ticket.
> I'll prepare a patch soon-ish.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15820) tools/bin/fqltool doesn't work on all distributions
[
https://issues.apache.org/jira/browse/CASSANDRA-15820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17110956#comment-17110956
]
Eduard Tudenhoefner commented on CASSANDRA-15820:
-
+1
> tools/bin/fqltool doesn't work on all distributions
> ---
>
> Key: CASSANDRA-15820
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15820
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/fql
>Reporter: Robert Stupp
>Assignee: Robert Stupp
>Priority: Normal
> Fix For: 4.0-alpha
>
>
> The line
> {code}
> if [ ! $1 ]; then break; fi
> {code}
> doesn't work on all OSes/Linux distributions (e.g. a bare Ubuntu 18.04) with
> {{#!/bin/sh}} causing {{fqltool}} to fail. The fix is quite simple
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15776) python dtest regression caused by CASSANDRA-15637
[ https://issues.apache.org/jira/browse/CASSANDRA-15776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17106061#comment-17106061 ] Eduard Tudenhoefner commented on CASSANDRA-15776: - sorry, wasn't aware you're waiting for my review because I assumed that 2 reviews would be enough. Changes LGTM > python dtest regression caused by CASSANDRA-15637 > - > > Key: CASSANDRA-15776 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15776 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 4.0-alpha > > Time Spent: 1h 40m > Remaining Estimate: 0h > > CASSANDRA-15637 deprecated size_estimates in favor of table_estimates to > allow for local primary range estimates (needed for MapReduce). This appears > to have caused a regression in the python dtest nodetool_test.TestNodetool. > test_refresh_size_estimates_clears_invalid_entries (as seen by [Circle > CI|https://app.circleci.com/pipelines/github/dcapwell/cassandra/255/workflows/21907001-93ed-4963-9314-6a0ac6ea0f1d/jobs/1246/tests] > and > [Jenkins|https://ci-cassandra.apache.org/job/Cassandra-trunk-dtest/56/]). -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15729) Jenkins Test Results Report in plaintext for ASF ML
[ https://issues.apache.org/jira/browse/CASSANDRA-15729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17100631#comment-17100631 ] Eduard Tudenhoefner commented on CASSANDRA-15729: - [~mck] changes LGTM > Jenkins Test Results Report in plaintext for ASF ML > --- > > Key: CASSANDRA-15729 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15729 > Project: Cassandra > Issue Type: Task > Components: Build, CI >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Labels: Jenkins > Fix For: 4.0-beta > > Attachments: .Screenshot 2020-05-01 at 01.12.28.png > > > The Jenkins pipeline builds now aggregate all test reports. > For example: > - https://ci-cassandra.apache.org/job/Cassandra-trunk/68/testReport/ > - > https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-trunk/detail/Cassandra-trunk/68/tests > But Jenkins can only keep a limited amount of build history, so those links > are not permanent, can't be used as references, and don't help for bisecting > and blame on regressions (and flakey tests) over a longer period of time. > The builds@ ML can provide a permanent record of test results. > This was first brought up in these two threads: > - > https://lists.apache.org/thread.html/re8122e4fdd8629e7fbca2abf27d72054b3bc0e3690ece8b8e66f618b%40%3Cdev.cassandra.apache.org%3E > - > https://lists.apache.org/thread.html/ra5f6aeea89546825fe7ccc4a80898c62f8ed57decabf709d81d9c720%40%3Cdev.cassandra.apache.org%3E > An example plaintext report, to demonstrate feasibility, is available here: > https://lists.apache.org/thread.html/r80d13f7af706bf8dfbf2387fab46004c1fbd3917b7bc339c49e69aa8%40%3Cbuilds.cassandra.apache.org%3E > Hurdles: > - the ASF mailing lists won't accept html, attachments, or any message body > over 1MB. > - packages are used as a differentiator in the final aggregated report. The > cqlsh and dtests currently don't specify it. It needs to be added as a > "dot-separated" prefix to the testsuite and testcase name. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15768) Tarball contains duplicate entries
[
https://issues.apache.org/jira/browse/CASSANDRA-15768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15768:
Reviewers: Eduard Tudenhoefner, Eduard Tudenhoefner (was: Eduard
Tudenhoefner)
Eduard Tudenhoefner, Eduard Tudenhoefner
Status: Review In Progress (was: Patch Available)
> Tarball contains duplicate entries
> --
>
> Key: CASSANDRA-15768
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15768
> Project: Cassandra
> Issue Type: Bug
> Components: Build
>Reporter: Matthias Pfau
>Assignee: Matthias Pfau
>Priority: Normal
> Fix For: 4.0-rc
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The tarball contains a lot of duplicate entries. One example is
> cassandra-stress.bat:
> {code:sh}
> tar -tvf /home/map/Downloads/apache-cassandra-3.11.6-bin.tar.gz |grep
> "cassandra-stress.bat"
> -rw-r--r-- 0/01097 2020-02-10 23:57
> apache-cassandra-3.11.6/tools/bin/cassandra-stress.bat
> -rwxr-xr-x 0/01097 2020-02-10 23:57
> apache-cassandra-3.11.6/tools/bin/cassandra-stress.bat
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15768) Tarball contains duplicate entries
[
https://issues.apache.org/jira/browse/CASSANDRA-15768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17100544#comment-17100544
]
Eduard Tudenhoefner commented on CASSANDRA-15768:
-
changes LGTM
> Tarball contains duplicate entries
> --
>
> Key: CASSANDRA-15768
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15768
> Project: Cassandra
> Issue Type: Bug
> Components: Build
>Reporter: Matthias Pfau
>Assignee: Matthias Pfau
>Priority: Normal
> Fix For: 4.0-rc
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The tarball contains a lot of duplicate entries. One example is
> cassandra-stress.bat:
> {code:sh}
> tar -tvf /home/map/Downloads/apache-cassandra-3.11.6-bin.tar.gz |grep
> "cassandra-stress.bat"
> -rw-r--r-- 0/01097 2020-02-10 23:57
> apache-cassandra-3.11.6/tools/bin/cassandra-stress.bat
> -rwxr-xr-x 0/01097 2020-02-10 23:57
> apache-cassandra-3.11.6/tools/bin/cassandra-stress.bat
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-15768) Tarball contains duplicate entries
[
https://issues.apache.org/jira/browse/CASSANDRA-15768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner reassigned CASSANDRA-15768:
---
Assignee: Matthias Pfau
> Tarball contains duplicate entries
> --
>
> Key: CASSANDRA-15768
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15768
> Project: Cassandra
> Issue Type: Bug
> Components: Build
>Reporter: Matthias Pfau
>Assignee: Matthias Pfau
>Priority: Normal
> Fix For: 4.0-rc
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The tarball contains a lot of duplicate entries. One example is
> cassandra-stress.bat:
> {code:sh}
> tar -tvf /home/map/Downloads/apache-cassandra-3.11.6-bin.tar.gz |grep
> "cassandra-stress.bat"
> -rw-r--r-- 0/01097 2020-02-10 23:57
> apache-cassandra-3.11.6/tools/bin/cassandra-stress.bat
> -rwxr-xr-x 0/01097 2020-02-10 23:57
> apache-cassandra-3.11.6/tools/bin/cassandra-stress.bat
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15768) Tarball contains duplicate entries
[
https://issues.apache.org/jira/browse/CASSANDRA-15768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15768:
Test and Documentation Plan: see description
Status: Patch Available (was: Open)
> Tarball contains duplicate entries
> --
>
> Key: CASSANDRA-15768
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15768
> Project: Cassandra
> Issue Type: Bug
> Components: Build
>Reporter: Matthias Pfau
>Assignee: Matthias Pfau
>Priority: Normal
> Fix For: 4.0-rc
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The tarball contains a lot of duplicate entries. One example is
> cassandra-stress.bat:
> {code:sh}
> tar -tvf /home/map/Downloads/apache-cassandra-3.11.6-bin.tar.gz |grep
> "cassandra-stress.bat"
> -rw-r--r-- 0/01097 2020-02-10 23:57
> apache-cassandra-3.11.6/tools/bin/cassandra-stress.bat
> -rwxr-xr-x 0/01097 2020-02-10 23:57
> apache-cassandra-3.11.6/tools/bin/cassandra-stress.bat
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15749) Make clear in the documentation that stress is not a secured tool
[ https://issues.apache.org/jira/browse/CASSANDRA-15749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-15749: Status: Ready to Commit (was: Review In Progress) > Make clear in the documentation that stress is not a secured tool > - > > Key: CASSANDRA-15749 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15749 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Benjamin Lerer >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0, 2.2.x, 3.0.x, 3.11.x > > Time Spent: 10m > Remaining Estimate: 0h > > It has been reported that the serialization used by the stress server was > unsafe. > As Stress has never intended to be a secure application, the problem should > not be fixed but the documentation should be updated to reflect that fact. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15749) Make clear in the documentation that stress is not a secured tool
[ https://issues.apache.org/jira/browse/CASSANDRA-15749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17100522#comment-17100522 ] Eduard Tudenhoefner commented on CASSANDRA-15749: - [~Bereng] changes LGTM > Make clear in the documentation that stress is not a secured tool > - > > Key: CASSANDRA-15749 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15749 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Benjamin Lerer >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0, 2.2.x, 3.0.x, 3.11.x > > Time Spent: 10m > Remaining Estimate: 0h > > It has been reported that the serialization used by the stress server was > unsafe. > As Stress has never intended to be a secure application, the problem should > not be fixed but the documentation should be updated to reflect that fact. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15749) Make clear in the documentation that stress is not a secured tool
[ https://issues.apache.org/jira/browse/CASSANDRA-15749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-15749: Reviewers: Eduard Tudenhoefner, Eduard Tudenhoefner (was: Eduard Tudenhoefner) Eduard Tudenhoefner, Eduard Tudenhoefner Status: Review In Progress (was: Patch Available) > Make clear in the documentation that stress is not a secured tool > - > > Key: CASSANDRA-15749 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15749 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Benjamin Lerer >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0, 2.2.x, 3.0.x, 3.11.x > > Time Spent: 10m > Remaining Estimate: 0h > > It has been reported that the serialization used by the stress server was > unsafe. > As Stress has never intended to be a secure application, the problem should > not be fixed but the documentation should be updated to reflect that fact. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15776) python dtest regression caused by CASSANDRA-15637
[ https://issues.apache.org/jira/browse/CASSANDRA-15776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17100518#comment-17100518 ] Eduard Tudenhoefner commented on CASSANDRA-15776: - changes mostly LGTM. I added a few comments/questions on the PR > python dtest regression caused by CASSANDRA-15637 > - > > Key: CASSANDRA-15776 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15776 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 4.0-alpha > > Time Spent: 0.5h > Remaining Estimate: 0h > > CASSANDRA-15637 deprecated size_estimates in favor of table_estimates to > allow for local primary range estimates (needed for MapReduce). This appears > to have caused a regression in the python dtest nodetool_test.TestNodetool. > test_refresh_size_estimates_clears_invalid_entries (as seen by [Circle > CI|https://app.circleci.com/pipelines/github/dcapwell/cassandra/255/workflows/21907001-93ed-4963-9314-6a0ac6ea0f1d/jobs/1246/tests] > and > [Jenkins|https://ci-cassandra.apache.org/job/Cassandra-trunk-dtest/56/]). -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15781) Fix flakiness of DecayingEstimatedHistogramReservoirTest#testStriping and apply the same "fix" to other tests
[
https://issues.apache.org/jira/browse/CASSANDRA-15781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17098809#comment-17098809
]
Eduard Tudenhoefner commented on CASSANDRA-15781:
-
changes LGTM
> Fix flakiness of DecayingEstimatedHistogramReservoirTest#testStriping and
> apply the same "fix" to other tests
> -
>
> Key: CASSANDRA-15781
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15781
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/unit
>Reporter: Robert Stupp
>Assignee: Robert Stupp
>Priority: Normal
> Fix For: 4.0
>
>
> The unit test {{DecayingEstimatedHistogramReservoirTest#testStriping}} is
> flaky, especially when many tests are running concurrently, because the used
> thread-pool can still be running when the assertions are tested (i.e. the
> {{ExecutorService.awaitTermination()}} returned false).
> The "fix" is rather a band aid: extend the wait-period to 1 minute, check the
> return value of {{awaitTermination}} and apply the same change to some other
> tests that _might_ be affected as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15780) Less test stderr spam when running tests w/ java 11
[
https://issues.apache.org/jira/browse/CASSANDRA-15780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17098808#comment-17098808
]
Eduard Tudenhoefner commented on CASSANDRA-15780:
-
changes LGTM. Can you please link a test run?
> Less test stderr spam when running tests w/ java 11
> ---
>
> Key: CASSANDRA-15780
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15780
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/unit
>Reporter: Robert Stupp
>Assignee: Robert Stupp
>Priority: Normal
> Fix For: 4.0
>
>
> There are a bunch of tests that, when run with Java 11, emit the boilerplate
> {{WARNING: An illegal reflective access operation has occurred}} messages.
> The proposed change just adds more invocations to
> {{org.apache.cassandra.utils.FBUtilities#preventIllegalAccessWarnings}} to
> get rid of many of those.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15750) Upgrade Cassandra Java Driver to 4.6
[ https://issues.apache.org/jira/browse/CASSANDRA-15750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-15750: Description: After releasing C* 4.0 I think it would be a good idea to upgrade to the latest Cassandra Java Driver that is being used internally. (was: Before releasing C* 4.0 I think it would be a good idea to upgrade to the latest Cassandra Java Driver that is being used internally.) > Upgrade Cassandra Java Driver to 4.6 > > > Key: CASSANDRA-15750 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15750 > Project: Cassandra > Issue Type: Improvement > Components: Dependencies >Reporter: Eduard Tudenhoefner >Assignee: Eduard Tudenhoefner >Priority: Normal > Fix For: 4.x > > > After releasing C* 4.0 I think it would be a good idea to upgrade to the > latest Cassandra Java Driver that is being used internally. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15750) Upgrade Cassandra Java Driver to 4.6
[ https://issues.apache.org/jira/browse/CASSANDRA-15750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17093148#comment-17093148 ] Eduard Tudenhoefner commented on CASSANDRA-15750: - Makes sense to not update to 4.6 now. Fwiw, C* is already using latest 3.6.0 Driver (there's however 3.8.0 available). I'll leave the ticket open and we can upgrade to 4.6/in-tree driver at a later point. > Upgrade Cassandra Java Driver to 4.6 > > > Key: CASSANDRA-15750 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15750 > Project: Cassandra > Issue Type: Improvement > Components: Dependencies >Reporter: Eduard Tudenhoefner >Assignee: Eduard Tudenhoefner >Priority: Normal > Fix For: 4.x > > > Before releasing C* 4.0 I think it would be a good idea to upgrade to the > latest Cassandra Java Driver that is being used internally. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15750) Upgrade Cassandra Java Driver to 4.6
[ https://issues.apache.org/jira/browse/CASSANDRA-15750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-15750: Fix Version/s: (was: 4.0-rc) (was: 4.0-beta) 4.x > Upgrade Cassandra Java Driver to 4.6 > > > Key: CASSANDRA-15750 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15750 > Project: Cassandra > Issue Type: Improvement > Components: Dependencies >Reporter: Eduard Tudenhoefner >Assignee: Eduard Tudenhoefner >Priority: Normal > Fix For: 4.x > > > Before releasing C* 4.0 I think it would be a good idea to upgrade to the > latest Cassandra Java Driver that is being used internally. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15750) Upgrade Cassandra Java Driver to 4.6
Eduard Tudenhoefner created CASSANDRA-15750: --- Summary: Upgrade Cassandra Java Driver to 4.6 Key: CASSANDRA-15750 URL: https://issues.apache.org/jira/browse/CASSANDRA-15750 Project: Cassandra Issue Type: Improvement Components: Dependencies Reporter: Eduard Tudenhoefner Assignee: Eduard Tudenhoefner Before releasing C* 4.0 I think it would be a good idea to upgrade to the latest Cassandra Java Driver that is being used internally. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15750) Upgrade Cassandra Java Driver to 4.6
[ https://issues.apache.org/jira/browse/CASSANDRA-15750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-15750: Fix Version/s: 4.0-rc 4.0-beta > Upgrade Cassandra Java Driver to 4.6 > > > Key: CASSANDRA-15750 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15750 > Project: Cassandra > Issue Type: Improvement > Components: Dependencies >Reporter: Eduard Tudenhoefner >Assignee: Eduard Tudenhoefner >Priority: Normal > Fix For: 4.0-beta, 4.0-rc > > > Before releasing C* 4.0 I think it would be a good idea to upgrade to the > latest Cassandra Java Driver that is being used internally. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15744) FBUtilitities.testWaitFirstFuture is flaky
[
https://issues.apache.org/jira/browse/CASSANDRA-15744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088707#comment-17088707
]
Eduard Tudenhoefner commented on CASSANDRA-15744:
-
changes LGTM
> FBUtilitities.testWaitFirstFuture is flaky
> --
>
> Key: CASSANDRA-15744
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15744
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Robert Stupp
>Assignee: Robert Stupp
>Priority: Normal
> Fix For: 4.0, 3.0.x, 3.11.x
>
>
> The unit test FBUtilitities.testWaitFirstFuture
> Example failure message: {{junit.framework.AssertionFailedError:
> expected:<40> but was:<10>}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14973) Bring v5 driver out of beta, introduce v6 before 4.0 release is cut
[ https://issues.apache.org/jira/browse/CASSANDRA-14973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088541#comment-17088541 ] Eduard Tudenhoefner commented on CASSANDRA-14973: - [JAVA-2704|https://datastax-oss.atlassian.net/browse/JAVA-2704] is the related ticket on the Java Driver side > Bring v5 driver out of beta, introduce v6 before 4.0 release is cut > --- > > Key: CASSANDRA-14973 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14973 > Project: Cassandra > Issue Type: Task >Reporter: Alex Petrov >Assignee: Alex Petrov >Priority: Urgent > Labels: protocolv5 > Fix For: 4.0, 4.0-rc > > > In http://issues.apache.org/jira/browse/CASSANDRA-12142, we’ve introduced > Beta flag for v5 protocol. However, up till now, v5 is in beta both in > [Cassandra|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/transport/ProtocolVersion.java#L46] > and in > [java-driver|https://github.com/datastax/java-driver/blob/3.x/driver-core/src/main/java/com/datastax/driver/core/ProtocolVersion.java#L35]. > > Before the final 4.0 release is cut, we need to bring v5 out of beta and > finalise native protocol spec, and start bringing all new changes to v6 > protocol, which will be in beta. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15730) Batch statement preparation fails if multiple tables and parameters are used
[
https://issues.apache.org/jira/browse/CASSANDRA-15730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088446#comment-17088446
]
Eduard Tudenhoefner commented on CASSANDRA-15730:
-
changes LGTM
> Batch statement preparation fails if multiple tables and parameters are used
>
>
> Key: CASSANDRA-15730
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15730
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Batch Log
>Reporter: Bryn Cooke
>Assignee: Bryn Cooke
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Batch statement preparation fails with an assertion error if multiple tables
> and parameters are used.
> {{BEGIN BATCH }}
> {{ UPDATE tbl1 SET v1 = 1 WHERE k1 = ?}}
> {{ UPDATE tbl2 SET v2 = 2 WHERE k2 = ?}}
> {{APPLY BATCH}}
> The logic for affectsMultipleTables
> [here|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/cql3/statements/BatchStatement.java#L144]
> looks inverted
> This later causes an assertion failure
> [here|https://github.com/apache/cassandra/blob/24c8a21c1c131abd89c6b646343ff098d1b3263b/src/java/org/apache/cassandra/cql3/VariableSpecifications.java#L75]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15730) Batch statement preparation fails if multiple tables and parameters are used
[
https://issues.apache.org/jira/browse/CASSANDRA-15730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15730:
Reviewers: Eduard Tudenhoefner, Robert Stupp, Eduard Tudenhoefner (was:
Eduard Tudenhoefner, Robert Stupp)
Eduard Tudenhoefner, Robert Stupp, Eduard Tudenhoefner
Status: Review In Progress (was: Patch Available)
> Batch statement preparation fails if multiple tables and parameters are used
>
>
> Key: CASSANDRA-15730
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15730
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Batch Log
>Reporter: Bryn Cooke
>Assignee: Bryn Cooke
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Batch statement preparation fails with an assertion error if multiple tables
> and parameters are used.
> {{BEGIN BATCH }}
> {{ UPDATE tbl1 SET v1 = 1 WHERE k1 = ?}}
> {{ UPDATE tbl2 SET v2 = 2 WHERE k2 = ?}}
> {{APPLY BATCH}}
> The logic for affectsMultipleTables
> [here|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/cql3/statements/BatchStatement.java#L144]
> looks inverted
> This later causes an assertion failure
> [here|https://github.com/apache/cassandra/blob/24c8a21c1c131abd89c6b646343ff098d1b3263b/src/java/org/apache/cassandra/cql3/VariableSpecifications.java#L75]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15730) Batch statement preparation fails if multiple tables and parameters are used
[
https://issues.apache.org/jira/browse/CASSANDRA-15730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15730:
Test and Documentation Plan: see PR
Status: Patch Available (was: In Progress)
> Batch statement preparation fails if multiple tables and parameters are used
>
>
> Key: CASSANDRA-15730
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15730
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Batch Log
>Reporter: Bryn Cooke
>Assignee: Bryn Cooke
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Batch statement preparation fails with an assertion error if multiple tables
> and parameters are used.
> {{BEGIN BATCH }}
> {{ UPDATE tbl1 SET v1 = 1 WHERE k1 = ?}}
> {{ UPDATE tbl2 SET v2 = 2 WHERE k2 = ?}}
> {{APPLY BATCH}}
> The logic for affectsMultipleTables
> [here|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/cql3/statements/BatchStatement.java#L144]
> looks inverted
> This later causes an assertion failure
> [here|https://github.com/apache/cassandra/blob/24c8a21c1c131abd89c6b646343ff098d1b3263b/src/java/org/apache/cassandra/cql3/VariableSpecifications.java#L75]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15730) Batch statement preparation fails if multiple tables and parameters are used
[
https://issues.apache.org/jira/browse/CASSANDRA-15730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15730:
Bug Category: Parent values: Correctness(12982)
Complexity: Low Hanging Fruit
Component/s: Consistency/Batch Log
Discovered By: User Report
Severity: Normal
Status: Open (was: Triage Needed)
> Batch statement preparation fails if multiple tables and parameters are used
>
>
> Key: CASSANDRA-15730
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15730
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Batch Log
>Reporter: Bryn Cooke
>Assignee: Bryn Cooke
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Batch statement preparation fails with an assertion error if multiple tables
> and parameters are used.
> {{BEGIN BATCH }}
> {{ UPDATE tbl1 SET v1 = 1 WHERE k1 = ?}}
> {{ UPDATE tbl2 SET v2 = 2 WHERE k2 = ?}}
> {{APPLY BATCH}}
> The logic for affectsMultipleTables
> [here|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/cql3/statements/BatchStatement.java#L144]
> looks inverted
> This later causes an assertion failure
> [here|https://github.com/apache/cassandra/blob/24c8a21c1c131abd89c6b646343ff098d1b3263b/src/java/org/apache/cassandra/cql3/VariableSpecifications.java#L75]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14973) Bring v5 driver out of beta, introduce v6 before 4.0 release is cut
[ https://issues.apache.org/jira/browse/CASSANDRA-14973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-14973: Reviewers: Eduard Tudenhoefner, Sam Tunnicliffe (was: Sam Tunnicliffe) > Bring v5 driver out of beta, introduce v6 before 4.0 release is cut > --- > > Key: CASSANDRA-14973 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14973 > Project: Cassandra > Issue Type: Task >Reporter: Alex Petrov >Assignee: Alex Petrov >Priority: Urgent > Labels: protocolv5 > Fix For: 4.0, 4.0-rc > > > In http://issues.apache.org/jira/browse/CASSANDRA-12142, we’ve introduced > Beta flag for v5 protocol. However, up till now, v5 is in beta both in > [Cassandra|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/transport/ProtocolVersion.java#L46] > and in > [java-driver|https://github.com/datastax/java-driver/blob/3.x/driver-core/src/main/java/com/datastax/driver/core/ProtocolVersion.java#L35]. > > Before the final 4.0 release is cut, we need to bring v5 out of beta and > finalise native protocol spec, and start bringing all new changes to v6 > protocol, which will be in beta. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-15730) Batch statement preparation fails if multiple tables and parameters are used
[
https://issues.apache.org/jira/browse/CASSANDRA-15730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner reassigned CASSANDRA-15730:
---
Assignee: Bryn Cooke
> Batch statement preparation fails if multiple tables and parameters are used
>
>
> Key: CASSANDRA-15730
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15730
> Project: Cassandra
> Issue Type: Bug
>Reporter: Bryn Cooke
>Assignee: Bryn Cooke
>Priority: Normal
> Labels: pull-request-available
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Batch statement preparation fails with an assertion error if multiple tables
> and parameters are used.
> {{BEGIN BATCH }}
> {{ UPDATE tbl1 SET v1 = 1 WHERE k1 = ?}}
> {{ UPDATE tbl2 SET v2 = 2 WHERE k2 = ?}}
> {{APPLY BATCH}}
> The logic for affectsMultipleTables
> [here|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/cql3/statements/BatchStatement.java#L144]
> looks inverted
> This later causes an assertion failure
> [here|https://github.com/apache/cassandra/blob/24c8a21c1c131abd89c6b646343ff098d1b3263b/src/java/org/apache/cassandra/cql3/VariableSpecifications.java#L75]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15736) Fix Python SyntaxWarning: "is not" with a literal. Did you mean "!="
[
https://issues.apache.org/jira/browse/CASSANDRA-15736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17085469#comment-17085469
]
Eduard Tudenhoefner commented on CASSANDRA-15736:
-
[Run with
SyntaxWarnings|https://ci-cassandra.apache.org/job/Cassandra-trunk-dtest/44/consoleText]
[Run without
SyntaxWarnings|https://ci-cassandra.apache.org/job/Cassandra-devbranch-dtest/68/consoleText]
> Fix Python SyntaxWarning: "is not" with a literal. Did you mean "!="
>
>
> Key: CASSANDRA-15736
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15736
> Project: Cassandra
> Issue Type: Task
> Components: Test/dtest
>Reporter: Eduard Tudenhoefner
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> With the upgrade to Python 3.8 there are SyntaxWarnings now showing up in the
> tests, which should be fixed.
> {code}
> /home/cassandra/cassandra/cassandra-dtest/conftest.py:207: SyntaxWarning: "is
> not" with a literal. Did you mean "!="?
> if len(errors) is not 0:
> /home/cassandra/cassandra/cassandra-dtest/conftest.py:240: SyntaxWarning: "is
> not" with a literal. Did you mean "!="?
> if len(logs) is not 0:
> /home/cassandra/cassandra/venv/src/ccm/ccmlib/repository.py:393:
> SyntaxWarning: "is not" with a literal. Did you mean "!="?
> while attempt < 3 and ret_val is not 0:
> /home/cassandra/cassandra/venv/src/ccm/ccmlib/repository.py:399:
> SyntaxWarning: "is not" with a literal. Did you mean "!="?
> if ret_val is not 0:
> /home/cassandra/cassandra/venv/src/ccm/ccmlib/repository.py:422:
> SyntaxWarning: "is not" with a literal. Did you mean "!="?
> if ret_val is not 0:
> /home/cassandra/cassandra/venv/src/ccm/ccmlib/repository.py:425:
> SyntaxWarning: "is not" with a literal. Did you mean "!="?
> if ret_val is not 0:
> /home/cassandra/cassandra/cassandra-dtest/dtest_setup.py:124: SyntaxWarning:
> "is not" with a literal. Did you mean "!="?
> if len(filtered_errors) is not 0:
> /home/cassandra/cassandra/cassandra-dtest/dtest_setup.py:152: SyntaxWarning:
> "is not" with a literal. Did you mean "!="?
> if len(logs) is not 0:
> /home/cassandra/cassandra/cassandra-dtest/dtest_setup.py:286: SyntaxWarning:
> "is not" with a literal. Did you mean "!="?
> if len(errors) is not 0:
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15728) Setting "cassandra_dir" in pytest.ini has no effect
[
https://issues.apache.org/jira/browse/CASSANDRA-15728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15728:
Reviewers: Benjamin Lerer, Berenguer Blasi (was: Berenguer Blasi)
> Setting "cassandra_dir" in pytest.ini has no effect
> ---
>
> Key: CASSANDRA-15728
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15728
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest
>Reporter: Eduard Tudenhoefner
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Setting *cassandra_dir* in *pytest.ini* should not require specifying
> *--cassandra-dir* on the command line:
> {code}
> $ pytest cql_tracing_test.py
>
> test session starts
> =
> platform linux -- Python 3.6.9, pytest-3.6.4, py-1.8.1, pluggy-0.7.1
> rootdir: /home/nastra/Development/pycharm-projects/cassandra-dtest, inifile:
> pytest.ini
> plugins: timeout-1.3.4, flaky-3.6.1
> timeout: 900.0s
> timeout method: signal
> timeout func_only: False
> collecting 4 items
>
>
>
> INTERNALERROR> Traceback (most recent call last):
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 178,
> in wrap_session
> INTERNALERROR> session.exitstatus = doit(config, session) or 0
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 214,
> in _main
> INTERNALERROR> config.hook.pytest_collection(session=session)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258,
> in __call__
> INTERNALERROR> return self._hookexec(self, self._nonwrappers +
> self._wrappers, kwargs)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67,
> in _hookexec
> INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61,
> in
> INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'),
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201,
> in _multicall
> INTERNALERROR> return outcome.get_result()
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76,
> in get_result
> INTERNALERROR> raise ex[1].with_traceback(ex[2])
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180,
> in _multicall
> INTERNALERROR> res = hook_impl.function(*args)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 224,
> in pytest_collection
> INTERNALERROR> return session.perform_collect()
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 429,
> in perform_collect
> INTERNALERROR> session=self, config=self.config, items=items
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258,
> in __call__
> INTERNALERROR> return self._hookexec(self, self._nonwrappers +
> self._wrappers, kwargs)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67,
> in _hookexec
> INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61,
> in
> INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'),
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201,
> in _multicall
> INTERNALERROR> return outcome.get_result()
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76,
> in get_result
> INTERNALERROR> raise ex[1].with_traceback(ex[2])
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180,
> in _multicall
> INTERNALERROR> res = hook_impl.function(*args)
> INTERNALERROR> File
> "/home/nastra/Development/pycharm-projects/cassandra-dtest/conftest.py", line
> 440, in pytest_collection_modifyitems
> INTERNALERROR> raise Exception("Required
[jira] [Updated] (CASSANDRA-15736) Fix Python SyntaxWarning: "is not" with a literal. Did you mean "!="
[
https://issues.apache.org/jira/browse/CASSANDRA-15736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15736:
Test and Documentation Plan: See syntaxwarnings
Status: Patch Available (was: Open)
> Fix Python SyntaxWarning: "is not" with a literal. Did you mean "!="
>
>
> Key: CASSANDRA-15736
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15736
> Project: Cassandra
> Issue Type: Task
> Components: Test/dtest
>Reporter: Eduard Tudenhoefner
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> With the upgrade to Python 3.8 there are SyntaxWarnings now showing up in the
> tests, which should be fixed.
> {code}
> /home/cassandra/cassandra/cassandra-dtest/conftest.py:207: SyntaxWarning: "is
> not" with a literal. Did you mean "!="?
> if len(errors) is not 0:
> /home/cassandra/cassandra/cassandra-dtest/conftest.py:240: SyntaxWarning: "is
> not" with a literal. Did you mean "!="?
> if len(logs) is not 0:
> /home/cassandra/cassandra/venv/src/ccm/ccmlib/repository.py:393:
> SyntaxWarning: "is not" with a literal. Did you mean "!="?
> while attempt < 3 and ret_val is not 0:
> /home/cassandra/cassandra/venv/src/ccm/ccmlib/repository.py:399:
> SyntaxWarning: "is not" with a literal. Did you mean "!="?
> if ret_val is not 0:
> /home/cassandra/cassandra/venv/src/ccm/ccmlib/repository.py:422:
> SyntaxWarning: "is not" with a literal. Did you mean "!="?
> if ret_val is not 0:
> /home/cassandra/cassandra/venv/src/ccm/ccmlib/repository.py:425:
> SyntaxWarning: "is not" with a literal. Did you mean "!="?
> if ret_val is not 0:
> /home/cassandra/cassandra/cassandra-dtest/dtest_setup.py:124: SyntaxWarning:
> "is not" with a literal. Did you mean "!="?
> if len(filtered_errors) is not 0:
> /home/cassandra/cassandra/cassandra-dtest/dtest_setup.py:152: SyntaxWarning:
> "is not" with a literal. Did you mean "!="?
> if len(logs) is not 0:
> /home/cassandra/cassandra/cassandra-dtest/dtest_setup.py:286: SyntaxWarning:
> "is not" with a literal. Did you mean "!="?
> if len(errors) is not 0:
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15736) Fix Python SyntaxWarning: "is not" with a literal. Did you mean "!="
[
https://issues.apache.org/jira/browse/CASSANDRA-15736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15736:
Change Category: Quality Assurance
Complexity: Low Hanging Fruit
Fix Version/s: 4.0-alpha
Status: Open (was: Triage Needed)
> Fix Python SyntaxWarning: "is not" with a literal. Did you mean "!="
>
>
> Key: CASSANDRA-15736
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15736
> Project: Cassandra
> Issue Type: Task
> Components: Test/dtest
>Reporter: Eduard Tudenhoefner
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> With the upgrade to Python 3.8 there are SyntaxWarnings now showing up in the
> tests, which should be fixed.
> {code}
> /home/cassandra/cassandra/cassandra-dtest/conftest.py:207: SyntaxWarning: "is
> not" with a literal. Did you mean "!="?
> if len(errors) is not 0:
> /home/cassandra/cassandra/cassandra-dtest/conftest.py:240: SyntaxWarning: "is
> not" with a literal. Did you mean "!="?
> if len(logs) is not 0:
> /home/cassandra/cassandra/venv/src/ccm/ccmlib/repository.py:393:
> SyntaxWarning: "is not" with a literal. Did you mean "!="?
> while attempt < 3 and ret_val is not 0:
> /home/cassandra/cassandra/venv/src/ccm/ccmlib/repository.py:399:
> SyntaxWarning: "is not" with a literal. Did you mean "!="?
> if ret_val is not 0:
> /home/cassandra/cassandra/venv/src/ccm/ccmlib/repository.py:422:
> SyntaxWarning: "is not" with a literal. Did you mean "!="?
> if ret_val is not 0:
> /home/cassandra/cassandra/venv/src/ccm/ccmlib/repository.py:425:
> SyntaxWarning: "is not" with a literal. Did you mean "!="?
> if ret_val is not 0:
> /home/cassandra/cassandra/cassandra-dtest/dtest_setup.py:124: SyntaxWarning:
> "is not" with a literal. Did you mean "!="?
> if len(filtered_errors) is not 0:
> /home/cassandra/cassandra/cassandra-dtest/dtest_setup.py:152: SyntaxWarning:
> "is not" with a literal. Did you mean "!="?
> if len(logs) is not 0:
> /home/cassandra/cassandra/cassandra-dtest/dtest_setup.py:286: SyntaxWarning:
> "is not" with a literal. Did you mean "!="?
> if len(errors) is not 0:
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15734) cqlsh_tests.test_cqlsh.TestCqlsh.test_pycodestyle_compliance fails on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-15734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-15734: Test and Documentation Plan: See PR Status: Patch Available (was: In Progress) > cqlsh_tests.test_cqlsh.TestCqlsh.test_pycodestyle_compliance fails on trunk > --- > > Key: CASSANDRA-15734 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15734 > Project: Cassandra > Issue Type: Task > Components: Test/dtest >Reporter: Eduard Tudenhoefner >Assignee: Eduard Tudenhoefner >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Time Spent: 10m > Remaining Estimate: 0h > > This recently started to fail with Python 3.8 as can be seen > [here|https://ci-cassandra.apache.org/job/Cassandra-trunk/73/testReport/junit/cqlsh_tests.test_cqlsh/TestCqlsh/test_pycodestyle_compliance/] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15734) cqlsh_tests.test_cqlsh.TestCqlsh.test_pycodestyle_compliance fails on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-15734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-15734: Change Category: Code Clarity Complexity: Low Hanging Fruit Status: Open (was: Triage Needed) > cqlsh_tests.test_cqlsh.TestCqlsh.test_pycodestyle_compliance fails on trunk > --- > > Key: CASSANDRA-15734 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15734 > Project: Cassandra > Issue Type: Task > Components: Test/dtest >Reporter: Eduard Tudenhoefner >Assignee: Eduard Tudenhoefner >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Time Spent: 10m > Remaining Estimate: 0h > > This recently started to fail with Python 3.8 as can be seen > [here|https://ci-cassandra.apache.org/job/Cassandra-trunk/73/testReport/junit/cqlsh_tests.test_cqlsh/TestCqlsh/test_pycodestyle_compliance/] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15734) cqlsh_tests.test_cqlsh.TestCqlsh.test_pycodestyle_compliance fails on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-15734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-15734: Workflow: Cassandra Default Workflow (was: Cassandra Bug Workflow) Issue Type: Task (was: Bug) > cqlsh_tests.test_cqlsh.TestCqlsh.test_pycodestyle_compliance fails on trunk > --- > > Key: CASSANDRA-15734 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15734 > Project: Cassandra > Issue Type: Task > Components: Test/dtest >Reporter: Eduard Tudenhoefner >Assignee: Eduard Tudenhoefner >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Time Spent: 10m > Remaining Estimate: 0h > > This recently started to fail with Python 3.8 as can be seen > [here|https://ci-cassandra.apache.org/job/Cassandra-trunk/73/testReport/junit/cqlsh_tests.test_cqlsh/TestCqlsh/test_pycodestyle_compliance/] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15736) Fix Python SyntaxWarning: "is not" with a literal. Did you mean "!="
Eduard Tudenhoefner created CASSANDRA-15736:
---
Summary: Fix Python SyntaxWarning: "is not" with a literal. Did
you mean "!="
Key: CASSANDRA-15736
URL: https://issues.apache.org/jira/browse/CASSANDRA-15736
Project: Cassandra
Issue Type: Task
Components: Test/dtest
Reporter: Eduard Tudenhoefner
Assignee: Eduard Tudenhoefner
With the upgrade to Python 3.8 there are SyntaxWarnings now showing up in the
tests, which should be fixed.
{code}
/home/cassandra/cassandra/cassandra-dtest/conftest.py:207: SyntaxWarning: "is
not" with a literal. Did you mean "!="?
if len(errors) is not 0:
/home/cassandra/cassandra/cassandra-dtest/conftest.py:240: SyntaxWarning: "is
not" with a literal. Did you mean "!="?
if len(logs) is not 0:
/home/cassandra/cassandra/venv/src/ccm/ccmlib/repository.py:393: SyntaxWarning:
"is not" with a literal. Did you mean "!="?
while attempt < 3 and ret_val is not 0:
/home/cassandra/cassandra/venv/src/ccm/ccmlib/repository.py:399: SyntaxWarning:
"is not" with a literal. Did you mean "!="?
if ret_val is not 0:
/home/cassandra/cassandra/venv/src/ccm/ccmlib/repository.py:422: SyntaxWarning:
"is not" with a literal. Did you mean "!="?
if ret_val is not 0:
/home/cassandra/cassandra/venv/src/ccm/ccmlib/repository.py:425: SyntaxWarning:
"is not" with a literal. Did you mean "!="?
if ret_val is not 0:
/home/cassandra/cassandra/cassandra-dtest/dtest_setup.py:124: SyntaxWarning:
"is not" with a literal. Did you mean "!="?
if len(filtered_errors) is not 0:
/home/cassandra/cassandra/cassandra-dtest/dtest_setup.py:152: SyntaxWarning:
"is not" with a literal. Did you mean "!="?
if len(logs) is not 0:
/home/cassandra/cassandra/cassandra-dtest/dtest_setup.py:286: SyntaxWarning:
"is not" with a literal. Did you mean "!="?
if len(errors) is not 0:
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15734) cqlsh_tests.test_cqlsh.TestCqlsh.test_pycodestyle_compliance fails on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-15734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-15734: Fix Version/s: 4.0-alpha > cqlsh_tests.test_cqlsh.TestCqlsh.test_pycodestyle_compliance fails on trunk > --- > > Key: CASSANDRA-15734 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15734 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest >Reporter: Eduard Tudenhoefner >Assignee: Eduard Tudenhoefner >Priority: Normal > Fix For: 4.0-alpha > > > This recently started to fail with Python 3.8 as can be seen > [here|https://ci-cassandra.apache.org/job/Cassandra-trunk/73/testReport/junit/cqlsh_tests.test_cqlsh/TestCqlsh/test_pycodestyle_compliance/] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15734) cqlsh_tests.test_cqlsh.TestCqlsh.test_pycodestyle_compliance fails on trunk
Eduard Tudenhoefner created CASSANDRA-15734: --- Summary: cqlsh_tests.test_cqlsh.TestCqlsh.test_pycodestyle_compliance fails on trunk Key: CASSANDRA-15734 URL: https://issues.apache.org/jira/browse/CASSANDRA-15734 Project: Cassandra Issue Type: Bug Components: Test/dtest Reporter: Eduard Tudenhoefner Assignee: Eduard Tudenhoefner -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15734) cqlsh_tests.test_cqlsh.TestCqlsh.test_pycodestyle_compliance fails on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-15734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-15734: Description: This recently started to fail with Python 3.8 as can be seen [here|https://ci-cassandra.apache.org/job/Cassandra-trunk/73/testReport/junit/cqlsh_tests.test_cqlsh/TestCqlsh/test_pycodestyle_compliance/] > cqlsh_tests.test_cqlsh.TestCqlsh.test_pycodestyle_compliance fails on trunk > --- > > Key: CASSANDRA-15734 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15734 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest >Reporter: Eduard Tudenhoefner >Assignee: Eduard Tudenhoefner >Priority: Normal > > This recently started to fail with Python 3.8 as can be seen > [here|https://ci-cassandra.apache.org/job/Cassandra-trunk/73/testReport/junit/cqlsh_tests.test_cqlsh/TestCqlsh/test_pycodestyle_compliance/] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15728) Setting "cassandra_dir" in pytest.ini has no effect
[
https://issues.apache.org/jira/browse/CASSANDRA-15728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15728:
Reviewers: Berenguer Blasi (was: Berenguer Blasi, Eduard Tudenhoefner)
> Setting "cassandra_dir" in pytest.ini has no effect
> ---
>
> Key: CASSANDRA-15728
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15728
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest
>Reporter: Eduard Tudenhoefner
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Setting *cassandra_dir* in *pytest.ini* should not require specifying
> *--cassandra-dir* on the command line:
> {code}
> $ pytest cql_tracing_test.py
>
> test session starts
> =
> platform linux -- Python 3.6.9, pytest-3.6.4, py-1.8.1, pluggy-0.7.1
> rootdir: /home/nastra/Development/pycharm-projects/cassandra-dtest, inifile:
> pytest.ini
> plugins: timeout-1.3.4, flaky-3.6.1
> timeout: 900.0s
> timeout method: signal
> timeout func_only: False
> collecting 4 items
>
>
>
> INTERNALERROR> Traceback (most recent call last):
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 178,
> in wrap_session
> INTERNALERROR> session.exitstatus = doit(config, session) or 0
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 214,
> in _main
> INTERNALERROR> config.hook.pytest_collection(session=session)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258,
> in __call__
> INTERNALERROR> return self._hookexec(self, self._nonwrappers +
> self._wrappers, kwargs)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67,
> in _hookexec
> INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61,
> in
> INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'),
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201,
> in _multicall
> INTERNALERROR> return outcome.get_result()
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76,
> in get_result
> INTERNALERROR> raise ex[1].with_traceback(ex[2])
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180,
> in _multicall
> INTERNALERROR> res = hook_impl.function(*args)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 224,
> in pytest_collection
> INTERNALERROR> return session.perform_collect()
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 429,
> in perform_collect
> INTERNALERROR> session=self, config=self.config, items=items
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258,
> in __call__
> INTERNALERROR> return self._hookexec(self, self._nonwrappers +
> self._wrappers, kwargs)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67,
> in _hookexec
> INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61,
> in
> INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'),
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201,
> in _multicall
> INTERNALERROR> return outcome.get_result()
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76,
> in get_result
> INTERNALERROR> raise ex[1].with_traceback(ex[2])
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180,
> in _multicall
> INTERNALERROR> res = hook_impl.function(*args)
> INTERNALERROR> File
> "/home/nastra/Development/pycharm-projects/cassandra-dtest/conftest.py", line
> 440, in pytest_collection_modifyitems
> INTERNALERROR> raise
[jira] [Updated] (CASSANDRA-15728) Setting "cassandra_dir" in pytest.ini has no effect
[
https://issues.apache.org/jira/browse/CASSANDRA-15728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15728:
Reviewers: Berenguer Blasi, Eduard Tudenhoefner (was: Berenguer Blasi)
Status: Review In Progress (was: Patch Available)
> Setting "cassandra_dir" in pytest.ini has no effect
> ---
>
> Key: CASSANDRA-15728
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15728
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest
>Reporter: Eduard Tudenhoefner
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Setting *cassandra_dir* in *pytest.ini* should not require specifying
> *--cassandra-dir* on the command line:
> {code}
> $ pytest cql_tracing_test.py
>
> test session starts
> =
> platform linux -- Python 3.6.9, pytest-3.6.4, py-1.8.1, pluggy-0.7.1
> rootdir: /home/nastra/Development/pycharm-projects/cassandra-dtest, inifile:
> pytest.ini
> plugins: timeout-1.3.4, flaky-3.6.1
> timeout: 900.0s
> timeout method: signal
> timeout func_only: False
> collecting 4 items
>
>
>
> INTERNALERROR> Traceback (most recent call last):
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 178,
> in wrap_session
> INTERNALERROR> session.exitstatus = doit(config, session) or 0
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 214,
> in _main
> INTERNALERROR> config.hook.pytest_collection(session=session)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258,
> in __call__
> INTERNALERROR> return self._hookexec(self, self._nonwrappers +
> self._wrappers, kwargs)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67,
> in _hookexec
> INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61,
> in
> INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'),
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201,
> in _multicall
> INTERNALERROR> return outcome.get_result()
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76,
> in get_result
> INTERNALERROR> raise ex[1].with_traceback(ex[2])
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180,
> in _multicall
> INTERNALERROR> res = hook_impl.function(*args)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 224,
> in pytest_collection
> INTERNALERROR> return session.perform_collect()
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 429,
> in perform_collect
> INTERNALERROR> session=self, config=self.config, items=items
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258,
> in __call__
> INTERNALERROR> return self._hookexec(self, self._nonwrappers +
> self._wrappers, kwargs)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67,
> in _hookexec
> INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61,
> in
> INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'),
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201,
> in _multicall
> INTERNALERROR> return outcome.get_result()
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76,
> in get_result
> INTERNALERROR> raise ex[1].with_traceback(ex[2])
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180,
> in _multicall
> INTERNALERROR> res = hook_impl.function(*args)
> INTERNALERROR> File
> "/home/nastra/Development/pycharm-projects/cassandra-dtest/conftest.py", line
> 440, in
[jira] [Updated] (CASSANDRA-15728) Setting "cassandra_dir" in pytest.ini has no effect
[
https://issues.apache.org/jira/browse/CASSANDRA-15728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15728:
Reviewers: Berenguer Blasi
> Setting "cassandra_dir" in pytest.ini has no effect
> ---
>
> Key: CASSANDRA-15728
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15728
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest
>Reporter: Eduard Tudenhoefner
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Setting *cassandra_dir* in *pytest.ini* should not require specifying
> *--cassandra-dir* on the command line:
> {code}
> $ pytest cql_tracing_test.py
>
> test session starts
> =
> platform linux -- Python 3.6.9, pytest-3.6.4, py-1.8.1, pluggy-0.7.1
> rootdir: /home/nastra/Development/pycharm-projects/cassandra-dtest, inifile:
> pytest.ini
> plugins: timeout-1.3.4, flaky-3.6.1
> timeout: 900.0s
> timeout method: signal
> timeout func_only: False
> collecting 4 items
>
>
>
> INTERNALERROR> Traceback (most recent call last):
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 178,
> in wrap_session
> INTERNALERROR> session.exitstatus = doit(config, session) or 0
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 214,
> in _main
> INTERNALERROR> config.hook.pytest_collection(session=session)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258,
> in __call__
> INTERNALERROR> return self._hookexec(self, self._nonwrappers +
> self._wrappers, kwargs)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67,
> in _hookexec
> INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61,
> in
> INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'),
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201,
> in _multicall
> INTERNALERROR> return outcome.get_result()
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76,
> in get_result
> INTERNALERROR> raise ex[1].with_traceback(ex[2])
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180,
> in _multicall
> INTERNALERROR> res = hook_impl.function(*args)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 224,
> in pytest_collection
> INTERNALERROR> return session.perform_collect()
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 429,
> in perform_collect
> INTERNALERROR> session=self, config=self.config, items=items
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258,
> in __call__
> INTERNALERROR> return self._hookexec(self, self._nonwrappers +
> self._wrappers, kwargs)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67,
> in _hookexec
> INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61,
> in
> INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'),
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201,
> in _multicall
> INTERNALERROR> return outcome.get_result()
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76,
> in get_result
> INTERNALERROR> raise ex[1].with_traceback(ex[2])
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180,
> in _multicall
> INTERNALERROR> res = hook_impl.function(*args)
> INTERNALERROR> File
> "/home/nastra/Development/pycharm-projects/cassandra-dtest/conftest.py", line
> 440, in pytest_collection_modifyitems
> INTERNALERROR> raise Exception("Required dtest arguments were missing!
> You must
[jira] [Updated] (CASSANDRA-15728) Setting "cassandra_dir" in pytest.ini has no effect
[
https://issues.apache.org/jira/browse/CASSANDRA-15728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15728:
Test and Documentation Plan: run *pytest sometest.py* with *cassandra_dir*
being set in *pytest.ini*
Status: Patch Available (was: In Progress)
> Setting "cassandra_dir" in pytest.ini has no effect
> ---
>
> Key: CASSANDRA-15728
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15728
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest
>Reporter: Eduard Tudenhoefner
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Setting *cassandra_dir* in *pytest.ini* should not require specifying
> *--cassandra-dir* on the command line:
> {code}
> $ pytest cql_tracing_test.py
>
> test session starts
> =
> platform linux -- Python 3.6.9, pytest-3.6.4, py-1.8.1, pluggy-0.7.1
> rootdir: /home/nastra/Development/pycharm-projects/cassandra-dtest, inifile:
> pytest.ini
> plugins: timeout-1.3.4, flaky-3.6.1
> timeout: 900.0s
> timeout method: signal
> timeout func_only: False
> collecting 4 items
>
>
>
> INTERNALERROR> Traceback (most recent call last):
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 178,
> in wrap_session
> INTERNALERROR> session.exitstatus = doit(config, session) or 0
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 214,
> in _main
> INTERNALERROR> config.hook.pytest_collection(session=session)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258,
> in __call__
> INTERNALERROR> return self._hookexec(self, self._nonwrappers +
> self._wrappers, kwargs)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67,
> in _hookexec
> INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61,
> in
> INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'),
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201,
> in _multicall
> INTERNALERROR> return outcome.get_result()
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76,
> in get_result
> INTERNALERROR> raise ex[1].with_traceback(ex[2])
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180,
> in _multicall
> INTERNALERROR> res = hook_impl.function(*args)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 224,
> in pytest_collection
> INTERNALERROR> return session.perform_collect()
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 429,
> in perform_collect
> INTERNALERROR> session=self, config=self.config, items=items
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258,
> in __call__
> INTERNALERROR> return self._hookexec(self, self._nonwrappers +
> self._wrappers, kwargs)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67,
> in _hookexec
> INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61,
> in
> INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'),
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201,
> in _multicall
> INTERNALERROR> return outcome.get_result()
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76,
> in get_result
> INTERNALERROR> raise ex[1].with_traceback(ex[2])
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180,
> in _multicall
> INTERNALERROR> res = hook_impl.function(*args)
> INTERNALERROR> File
>
[jira] [Updated] (CASSANDRA-15728) Setting "cassandra_dir" in pytest.ini has no effect
[
https://issues.apache.org/jira/browse/CASSANDRA-15728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15728:
Bug Category: Parent values: Correctness(12982)
Complexity: Low Hanging Fruit
Discovered By: User Report
Fix Version/s: 4.0-alpha
Severity: Low
Status: Open (was: Triage Needed)
> Setting "cassandra_dir" in pytest.ini has no effect
> ---
>
> Key: CASSANDRA-15728
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15728
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest
>Reporter: Eduard Tudenhoefner
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Fix For: 4.0-alpha
>
>
> Setting *cassandra_dir* in *pytest.ini* should not require specifying
> *--cassandra-dir* on the command line:
> {code}
> $ pytest cql_tracing_test.py
>
> test session starts
> =
> platform linux -- Python 3.6.9, pytest-3.6.4, py-1.8.1, pluggy-0.7.1
> rootdir: /home/nastra/Development/pycharm-projects/cassandra-dtest, inifile:
> pytest.ini
> plugins: timeout-1.3.4, flaky-3.6.1
> timeout: 900.0s
> timeout method: signal
> timeout func_only: False
> collecting 4 items
>
>
>
> INTERNALERROR> Traceback (most recent call last):
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 178,
> in wrap_session
> INTERNALERROR> session.exitstatus = doit(config, session) or 0
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 214,
> in _main
> INTERNALERROR> config.hook.pytest_collection(session=session)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258,
> in __call__
> INTERNALERROR> return self._hookexec(self, self._nonwrappers +
> self._wrappers, kwargs)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67,
> in _hookexec
> INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61,
> in
> INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'),
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201,
> in _multicall
> INTERNALERROR> return outcome.get_result()
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76,
> in get_result
> INTERNALERROR> raise ex[1].with_traceback(ex[2])
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180,
> in _multicall
> INTERNALERROR> res = hook_impl.function(*args)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 224,
> in pytest_collection
> INTERNALERROR> return session.perform_collect()
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 429,
> in perform_collect
> INTERNALERROR> session=self, config=self.config, items=items
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258,
> in __call__
> INTERNALERROR> return self._hookexec(self, self._nonwrappers +
> self._wrappers, kwargs)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67,
> in _hookexec
> INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61,
> in
> INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'),
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201,
> in _multicall
> INTERNALERROR> return outcome.get_result()
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76,
> in get_result
> INTERNALERROR> raise ex[1].with_traceback(ex[2])
> INTERNALERROR> File
> "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180,
> in _multicall
> INTERNALERROR> res = hook_impl.function(*args)
> INTERNALERROR> File
> "/home/nastra/Development/pycharm-projects/cassandra-dtest/conftest.py", line
> 440, in pytest_collection_modifyitems
[jira] [Created] (CASSANDRA-15728) Setting "cassandra_dir" in pytest.ini has no effect
Eduard Tudenhoefner created CASSANDRA-15728:
---
Summary: Setting "cassandra_dir" in pytest.ini has no effect
Key: CASSANDRA-15728
URL: https://issues.apache.org/jira/browse/CASSANDRA-15728
Project: Cassandra
Issue Type: Bug
Components: Test/dtest
Reporter: Eduard Tudenhoefner
Assignee: Eduard Tudenhoefner
Setting *cassandra_dir* in *pytest.ini* should not require specifying
*--cassandra-dir* on the command line:
{code}
$ pytest cql_tracing_test.py
test session starts
=
platform linux -- Python 3.6.9, pytest-3.6.4, py-1.8.1, pluggy-0.7.1
rootdir: /home/nastra/Development/pycharm-projects/cassandra-dtest, inifile:
pytest.ini
plugins: timeout-1.3.4, flaky-3.6.1
timeout: 900.0s
timeout method: signal
timeout func_only: False
collecting 4 items
INTERNALERROR> Traceback (most recent call last):
INTERNALERROR> File
"/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 178, in
wrap_session
INTERNALERROR> session.exitstatus = doit(config, session) or 0
INTERNALERROR> File
"/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 214, in
_main
INTERNALERROR> config.hook.pytest_collection(session=session)
INTERNALERROR> File
"/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258, in
__call__
INTERNALERROR> return self._hookexec(self, self._nonwrappers +
self._wrappers, kwargs)
INTERNALERROR> File
"/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67, in
_hookexec
INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
INTERNALERROR> File
"/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61, in
INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'),
INTERNALERROR> File
"/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201,
in _multicall
INTERNALERROR> return outcome.get_result()
INTERNALERROR> File
"/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76, in
get_result
INTERNALERROR> raise ex[1].with_traceback(ex[2])
INTERNALERROR> File
"/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180,
in _multicall
INTERNALERROR> res = hook_impl.function(*args)
INTERNALERROR> File
"/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 224, in
pytest_collection
INTERNALERROR> return session.perform_collect()
INTERNALERROR> File
"/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 429, in
perform_collect
INTERNALERROR> session=self, config=self.config, items=items
INTERNALERROR> File
"/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258, in
__call__
INTERNALERROR> return self._hookexec(self, self._nonwrappers +
self._wrappers, kwargs)
INTERNALERROR> File
"/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67, in
_hookexec
INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
INTERNALERROR> File
"/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61, in
INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'),
INTERNALERROR> File
"/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201,
in _multicall
INTERNALERROR> return outcome.get_result()
INTERNALERROR> File
"/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76, in
get_result
INTERNALERROR> raise ex[1].with_traceback(ex[2])
INTERNALERROR> File
"/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180,
in _multicall
INTERNALERROR> res = hook_impl.function(*args)
INTERNALERROR> File
"/home/nastra/Development/pycharm-projects/cassandra-dtest/conftest.py", line
440, in pytest_collection_modifyitems
INTERNALERROR> raise Exception("Required dtest arguments were missing! You
must provide either --cassandra-dir "
INTERNALERROR> Exception: Required dtest arguments were missing! You must
provide either --cassandra-dir or --cassandra-version. Refer to the
documentation or invoke the help with --help.
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15659) Better support of Python 3 for cqlsh
[ https://issues.apache.org/jira/browse/CASSANDRA-15659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-15659: Reviewers: Michael Semb Wever, Eduard Tudenhoefner (was: Eduard Tudenhoefner, Michael Semb Wever) Michael Semb Wever, Eduard Tudenhoefner (was: Michael Semb Wever) Status: Review In Progress (was: Patch Available) > Better support of Python 3 for cqlsh > > > Key: CASSANDRA-15659 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15659 > Project: Cassandra > Issue Type: Task > Components: Tool/cqlsh >Reporter: Stefan Miklosovic >Assignee: Eduard Tudenhoefner >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Time Spent: 40m > Remaining Estimate: 0h > > h2. From mailing list: > [https://lists.apache.org/thread.html/r377099b632c62b641e4feef5b738084fc5369b0c7157fae867853597%40%3Cdev.cassandra.apache.org%3E] > > As of today (24/3/2020) and current trunk, there is Python 3.6 supported (1) > but there is not any 3.6 version ootb in Debian for example. E.g. Buster has > Python 3.7 and other (recent) releases have version 2.7. This means that if > one wants to use Python 3 in Debian, he has to use 3.6 but it is not in the > repository so he has to download / compile / install it on his own. > There should be some sane Python 3 version supported which is as well present > in Debian repository (or requirement to run with 3.6 should be relaxed) . > (1) > [https://github.com/apache/cassandra/blob/bf9a1d487b9ba469e8d740cf7d1cd419535a7e79/bin/cqlsh#L57-L65] > h2. Summary of work that was done: > I relaxed the requirement of *cqlsh* only working with Python 2.7 & 3.6 by > allowing Python 3.6+. > Note that I left the constraint for Python 3.6 being the minimum Python3 > version. > As [~ptbannister] pointed out, we could remove the Python 3.6 min version > once we remove Python 2.7 support, as otherwise testing with lots of > different Python versions will get costly. > 2 Dockerfiles were added in *pylib* for minimal local testing of *cqlsh* > starting up with Python 3.7 & 3.8 and that both revealed > CASSANDRA-15572 and CASSANDRA-15573. > CASSANDRA-15572 was fixed here as it was a one-liner. And I'm going to > tackle CASSANDRA-15573 later. > Python 3.8 testing was added to the CircleCI config so that we can actually > see what else breaks with newer Python versions. > A new Docker images with Ubuntu 19.10 was required for testing > ([https://github.com/apache/cassandra-builds/pull/17]). This docker image > sets up Python 2.7/3.6/3.7/3.8 with their respective virtual environments, > which are then being used by the CircleCI yaml. > The image *spod/cassandra-testing-ubuntu1810-java11-w-dependencies:20190306* > couldn't be updated unfortunately because it can't be built anymore, due to > Ubuntu 18.10 being EOL. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15573) Python 3.8 fails to execute cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-15573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15573:
Reviewers: Dinesh Joshi, Michael Semb Wever (was: Dinesh Joshi)
> Python 3.8 fails to execute cqlsh
> -
>
> Key: CASSANDRA-15573
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15573
> Project: Cassandra
> Issue Type: Sub-task
> Components: Tool/cqlsh
>Reporter: Yuki Morishita
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Python 3.8 renamed sre_parse.Pattern to sre_parse.State (see
> [https://bugs.python.org/issue34681] and corresponding pull request
> [https://github.com/python/cpython/pull/9310])
> So when executing cqlsh with Python 3.8, it throws error:
> {code:java}
> Traceback (most recent call last):
> File ".\bin\cqlsh.py", line 175, in
> from cqlshlib import cql3handling, cqlhandling, pylexotron, sslhandling,
> cqlshhandling
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cql3handling.py", line 19,
> in
> from cqlshlib.cqlhandling import CqlParsingRuleSet, Hint
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cqlhandling.py", line 23,
> in
> from cqlshlib import pylexotron, util
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 342,
> in
> class ParsingRuleSet:
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 343,
> in ParsingRuleSet
> RuleSpecScanner = SaferScanner([
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\saferscanner.py", line 74,
> in __init__
> s = re.sre_parse.Pattern()
> AttributeError: module 'sre_parse' has no attribute 'Pattern'
> {code}
> h2. Summary of Work that was done
> Added a Python 3.8 compatible SaferScanner implementation ([diff
> here|https://github.com/apache/cassandra/pull/518/commits/2e6813f0ef5817e5d8d655052d61ce75a5fc062c]).
> Note that the changes from CASSANDRA-15659 are required in order to verify
> that the issue is fixed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15659) Better support of Python 3 for cqlsh
[ https://issues.apache.org/jira/browse/CASSANDRA-15659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-15659: Reviewers: Michael Semb Wever (was: Eduard Tudenhoefner, Michael Semb Wever) > Better support of Python 3 for cqlsh > > > Key: CASSANDRA-15659 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15659 > Project: Cassandra > Issue Type: Task > Components: Tool/cqlsh >Reporter: Stefan Miklosovic >Assignee: Eduard Tudenhoefner >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Time Spent: 40m > Remaining Estimate: 0h > > h2. From mailing list: > [https://lists.apache.org/thread.html/r377099b632c62b641e4feef5b738084fc5369b0c7157fae867853597%40%3Cdev.cassandra.apache.org%3E] > > As of today (24/3/2020) and current trunk, there is Python 3.6 supported (1) > but there is not any 3.6 version ootb in Debian for example. E.g. Buster has > Python 3.7 and other (recent) releases have version 2.7. This means that if > one wants to use Python 3 in Debian, he has to use 3.6 but it is not in the > repository so he has to download / compile / install it on his own. > There should be some sane Python 3 version supported which is as well present > in Debian repository (or requirement to run with 3.6 should be relaxed) . > (1) > [https://github.com/apache/cassandra/blob/bf9a1d487b9ba469e8d740cf7d1cd419535a7e79/bin/cqlsh#L57-L65] > h2. Summary of work that was done: > I relaxed the requirement of *cqlsh* only working with Python 2.7 & 3.6 by > allowing Python 3.6+. > Note that I left the constraint for Python 3.6 being the minimum Python3 > version. > As [~ptbannister] pointed out, we could remove the Python 3.6 min version > once we remove Python 2.7 support, as otherwise testing with lots of > different Python versions will get costly. > 2 Dockerfiles were added in *pylib* for minimal local testing of *cqlsh* > starting up with Python 3.7 & 3.8 and that both revealed > CASSANDRA-15572 and CASSANDRA-15573. > CASSANDRA-15572 was fixed here as it was a one-liner. And I'm going to > tackle CASSANDRA-15573 later. > Python 3.8 testing was added to the CircleCI config so that we can actually > see what else breaks with newer Python versions. > A new Docker images with Ubuntu 19.10 was required for testing > ([https://github.com/apache/cassandra-builds/pull/17]). This docker image > sets up Python 2.7/3.6/3.7/3.8 with their respective virtual environments, > which are then being used by the CircleCI yaml. > The image *spod/cassandra-testing-ubuntu1810-java11-w-dependencies:20190306* > couldn't be updated unfortunately because it can't be built anymore, due to > Ubuntu 18.10 being EOL. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15659) Better support of Python 3 for cqlsh
[ https://issues.apache.org/jira/browse/CASSANDRA-15659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-15659: Reviewers: Michael Semb Wever > Better support of Python 3 for cqlsh > > > Key: CASSANDRA-15659 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15659 > Project: Cassandra > Issue Type: Task > Components: Tool/cqlsh >Reporter: Stefan Miklosovic >Assignee: Eduard Tudenhoefner >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Time Spent: 40m > Remaining Estimate: 0h > > h2. From mailing list: > [https://lists.apache.org/thread.html/r377099b632c62b641e4feef5b738084fc5369b0c7157fae867853597%40%3Cdev.cassandra.apache.org%3E] > > As of today (24/3/2020) and current trunk, there is Python 3.6 supported (1) > but there is not any 3.6 version ootb in Debian for example. E.g. Buster has > Python 3.7 and other (recent) releases have version 2.7. This means that if > one wants to use Python 3 in Debian, he has to use 3.6 but it is not in the > repository so he has to download / compile / install it on his own. > There should be some sane Python 3 version supported which is as well present > in Debian repository (or requirement to run with 3.6 should be relaxed) . > (1) > [https://github.com/apache/cassandra/blob/bf9a1d487b9ba469e8d740cf7d1cd419535a7e79/bin/cqlsh#L57-L65] > h2. Summary of work that was done: > I relaxed the requirement of *cqlsh* only working with Python 2.7 & 3.6 by > allowing Python 3.6+. > Note that I left the constraint for Python 3.6 being the minimum Python3 > version. > As [~ptbannister] pointed out, we could remove the Python 3.6 min version > once we remove Python 2.7 support, as otherwise testing with lots of > different Python versions will get costly. > 2 Dockerfiles were added in *pylib* for minimal local testing of *cqlsh* > starting up with Python 3.7 & 3.8 and that both revealed > CASSANDRA-15572 and CASSANDRA-15573. > CASSANDRA-15572 was fixed here as it was a one-liner. And I'm going to > tackle CASSANDRA-15573 later. > Python 3.8 testing was added to the CircleCI config so that we can actually > see what else breaks with newer Python versions. > A new Docker images with Ubuntu 19.10 was required for testing > ([https://github.com/apache/cassandra-builds/pull/17]). This docker image > sets up Python 2.7/3.6/3.7/3.8 with their respective virtual environments, > which are then being used by the CircleCI yaml. > The image *spod/cassandra-testing-ubuntu1810-java11-w-dependencies:20190306* > couldn't be updated unfortunately because it can't be built anymore, due to > Ubuntu 18.10 being EOL. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-15711) cqlsh ALTER KEYSPACE completion show virtual table keyspaces
[
https://issues.apache.org/jira/browse/CASSANDRA-15711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17079224#comment-17079224
]
Eduard Tudenhoefner edited comment on CASSANDRA-15711 at 4/9/20, 2:41 PM:
--
Tests on Jenkins
[here|https://ci-cassandra.apache.org/job/Cassandra-devbranch/46/], more
specifically
[this|https://ci-cassandra.apache.org/job/Cassandra-devbranch-cqlsh-tests/36/cython=no,jdk=JDK%201.8%20(latest),label=cassandra/testReport/cqlshlib.test.test_cqlsh_completion/TestCqlshCompletion/test_complete_in_alter_keyspace/]
is the newly added test.
was (Author: eduard.tudenhoefner):
Tests on Jenkins
[here|https://ci-cassandra.apache.org/job/Cassandra-devbranch/46/]
> cqlsh ALTER KEYSPACE completion show virtual table keyspaces
>
>
> Key: CASSANDRA-15711
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15711
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: Benjamin Lerer
>Assignee: Eduard Tudenhoefner
>Priority: Low
> Labels: pull-request-available
> Fix For: 4.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code}
> cqlsh> ALTER KEYSPACE
> system_traces system_virtual_schema system_auth
> system_views system_distributed
> {code}
> The {{system_virtual_schema}} and {{system_views}} keyspaces are virtual
> tables keyspaces that cannot be altered and by consequence they should not
> appear in this list.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15711) cqlsh ALTER KEYSPACE completion show virtual table keyspaces
[
https://issues.apache.org/jira/browse/CASSANDRA-15711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17079224#comment-17079224
]
Eduard Tudenhoefner commented on CASSANDRA-15711:
-
Tests on Jenkins
[here|https://ci-cassandra.apache.org/job/Cassandra-devbranch/46/]
> cqlsh ALTER KEYSPACE completion show virtual table keyspaces
>
>
> Key: CASSANDRA-15711
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15711
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: Benjamin Lerer
>Assignee: Eduard Tudenhoefner
>Priority: Low
> Labels: pull-request-available
> Fix For: 4.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code}
> cqlsh> ALTER KEYSPACE
> system_traces system_virtual_schema system_auth
> system_views system_distributed
> {code}
> The {{system_virtual_schema}} and {{system_views}} keyspaces are virtual
> tables keyspaces that cannot be altered and by consequence they should not
> appear in this list.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15711) cqlsh ALTER KEYSPACE completion show virtual table keyspaces
[
https://issues.apache.org/jira/browse/CASSANDRA-15711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15711:
Test and Documentation Plan: execute *ALTER KEYSPACE* and
*system_virtual_schema* and *system_views* shouldn't show up in the completion
Status: Patch Available (was: In Progress)
> cqlsh ALTER KEYSPACE completion show virtual table keyspaces
>
>
> Key: CASSANDRA-15711
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15711
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: Benjamin Lerer
>Assignee: Eduard Tudenhoefner
>Priority: Low
> Labels: pull-request-available
> Fix For: 4.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code}
> cqlsh> ALTER KEYSPACE
> system_traces system_virtual_schema system_auth
> system_views system_distributed
> {code}
> The {{system_virtual_schema}} and {{system_views}} keyspaces are virtual
> tables keyspaces that cannot be altered and by consequence they should not
> appear in this list.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15711) cqlsh ALTER KEYSPACE completion show virtual table keyspaces
[
https://issues.apache.org/jira/browse/CASSANDRA-15711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15711:
Status: Open (was: Triage Needed)
> cqlsh ALTER KEYSPACE completion show virtual table keyspaces
>
>
> Key: CASSANDRA-15711
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15711
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: Benjamin Lerer
>Assignee: Eduard Tudenhoefner
>Priority: Low
> Labels: pull-request-available
> Fix For: 4.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code}
> cqlsh> ALTER KEYSPACE
> system_traces system_virtual_schema system_auth
> system_views system_distributed
> {code}
> The {{system_virtual_schema}} and {{system_views}} keyspaces are virtual
> tables keyspaces that cannot be altered and by consequence they should not
> appear in this list.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-15711) cqlsh ALTER KEYSPACE completion show virtual table keyspaces
[
https://issues.apache.org/jira/browse/CASSANDRA-15711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner reassigned CASSANDRA-15711:
---
Assignee: Eduard Tudenhoefner
> cqlsh ALTER KEYSPACE completion show virtual table keyspaces
>
>
> Key: CASSANDRA-15711
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15711
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: Benjamin Lerer
>Assignee: Eduard Tudenhoefner
>Priority: Low
> Fix For: 4.0
>
>
> {code}
> cqlsh> ALTER KEYSPACE
> system_traces system_virtual_schema system_auth
> system_views system_distributed
> {code}
> The {{system_virtual_schema}} and {{system_views}} keyspaces are virtual
> tables keyspaces that cannot be altered and by consequence they should not
> appear in this list.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-15573) Python 3.8 fails to execute cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-15573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17077015#comment-17077015
]
Eduard Tudenhoefner edited comment on CASSANDRA-15573 at 4/9/20, 9:26 AM:
--
||[Patch|https://github.com/apache/cassandra/pull/518]||[CircleCI|https://app.circleci.com/pipelines/github/nastra/cassandra?branch=CASSANDRA-15573]||[Docker
Image
update|https://github.com/apache/cassandra-builds/pull/17]||[Jenkins|https://ci-cassandra.apache.org/job/Cassandra-devbranch/43/]||
was (Author: eduard.tudenhoefner):
||[Patch|https://github.com/apache/cassandra/pull/518]||[CircleCI|https://app.circleci.com/pipelines/github/nastra/cassandra?branch=CASSANDRA-15573]||[Docker
Image update|https://github.com/apache/cassandra-builds/pull/17]||
> Python 3.8 fails to execute cqlsh
> -
>
> Key: CASSANDRA-15573
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15573
> Project: Cassandra
> Issue Type: Sub-task
> Components: Tool/cqlsh
>Reporter: Yuki Morishita
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Python 3.8 renamed sre_parse.Pattern to sre_parse.State (see
> [https://bugs.python.org/issue34681] and corresponding pull request
> [https://github.com/python/cpython/pull/9310])
> So when executing cqlsh with Python 3.8, it throws error:
> {code:java}
> Traceback (most recent call last):
> File ".\bin\cqlsh.py", line 175, in
> from cqlshlib import cql3handling, cqlhandling, pylexotron, sslhandling,
> cqlshhandling
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cql3handling.py", line 19,
> in
> from cqlshlib.cqlhandling import CqlParsingRuleSet, Hint
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cqlhandling.py", line 23,
> in
> from cqlshlib import pylexotron, util
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 342,
> in
> class ParsingRuleSet:
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 343,
> in ParsingRuleSet
> RuleSpecScanner = SaferScanner([
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\saferscanner.py", line 74,
> in __init__
> s = re.sre_parse.Pattern()
> AttributeError: module 'sre_parse' has no attribute 'Pattern'
> {code}
> h2. Summary of Work that was done
> Added a Python 3.8 compatible SaferScanner implementation ([diff
> here|https://github.com/apache/cassandra/pull/518/commits/2e6813f0ef5817e5d8d655052d61ce75a5fc062c]).
> Note that the changes from CASSANDRA-15659 are required in order to verify
> that the issue is fixed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-15659) Better support of Python 3 for cqlsh
[ https://issues.apache.org/jira/browse/CASSANDRA-15659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17077009#comment-17077009 ] Eduard Tudenhoefner edited comment on CASSANDRA-15659 at 4/9/20, 9:25 AM: -- ||Pull Request||Tests||Docker Image||Jenkins|| |[PR#505|https://github.com/apache/cassandra/pull/505]|[CircleCI|https://app.circleci.com/pipelines/github/nastra/cassandra/19/workflows/dc0a8771-321f-40bf-a5e8-6e05b20bbca1]|[PR|https://github.com/apache/cassandra-builds/pull/17]|[Jenkins tests|https://ci-cassandra.apache.org/job/Cassandra-devbranch/42/]| Note that the test failures when testing with Python 3.8 are due to CASSANDRA-15573 and should be fixed in [this|https://app.circleci.com/pipelines/github/nastra/cassandra/18/workflows/0549d320-a53d-4bff-b8d8-56d1a4ccc8bf] test run. was (Author: eduard.tudenhoefner): ||Pull Request||Tests||Docker Image|| |[PR#505|https://github.com/apache/cassandra/pull/505]|[CircleCI|https://app.circleci.com/pipelines/github/nastra/cassandra/19/workflows/dc0a8771-321f-40bf-a5e8-6e05b20bbca1]|[PR|https://github.com/apache/cassandra-builds/pull/17] Note that the test failures when testing with Python 3.8 are due to CASSANDRA-15573 and should be fixed in [this|https://app.circleci.com/pipelines/github/nastra/cassandra/18/workflows/0549d320-a53d-4bff-b8d8-56d1a4ccc8bf] test run. > Better support of Python 3 for cqlsh > > > Key: CASSANDRA-15659 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15659 > Project: Cassandra > Issue Type: Task > Components: Tool/cqlsh >Reporter: Stefan Miklosovic >Assignee: Eduard Tudenhoefner >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Time Spent: 40m > Remaining Estimate: 0h > > h2. From mailing list: > [https://lists.apache.org/thread.html/r377099b632c62b641e4feef5b738084fc5369b0c7157fae867853597%40%3Cdev.cassandra.apache.org%3E] > > As of today (24/3/2020) and current trunk, there is Python 3.6 supported (1) > but there is not any 3.6 version ootb in Debian for example. E.g. Buster has > Python 3.7 and other (recent) releases have version 2.7. This means that if > one wants to use Python 3 in Debian, he has to use 3.6 but it is not in the > repository so he has to download / compile / install it on his own. > There should be some sane Python 3 version supported which is as well present > in Debian repository (or requirement to run with 3.6 should be relaxed) . > (1) > [https://github.com/apache/cassandra/blob/bf9a1d487b9ba469e8d740cf7d1cd419535a7e79/bin/cqlsh#L57-L65] > h2. Summary of work that was done: > I relaxed the requirement of *cqlsh* only working with Python 2.7 & 3.6 by > allowing Python 3.6+. > Note that I left the constraint for Python 3.6 being the minimum Python3 > version. > As [~ptbannister] pointed out, we could remove the Python 3.6 min version > once we remove Python 2.7 support, as otherwise testing with lots of > different Python versions will get costly. > 2 Dockerfiles were added in *pylib* for minimal local testing of *cqlsh* > starting up with Python 3.7 & 3.8 and that both revealed > CASSANDRA-15572 and CASSANDRA-15573. > CASSANDRA-15572 was fixed here as it was a one-liner. And I'm going to > tackle CASSANDRA-15573 later. > Python 3.8 testing was added to the CircleCI config so that we can actually > see what else breaks with newer Python versions. > A new Docker images with Ubuntu 19.10 was required for testing > ([https://github.com/apache/cassandra-builds/pull/17]). This docker image > sets up Python 2.7/3.6/3.7/3.8 with their respective virtual environments, > which are then being used by the CircleCI yaml. > The image *spod/cassandra-testing-ubuntu1810-java11-w-dependencies:20190306* > couldn't be updated unfortunately because it can't be built anymore, due to > Ubuntu 18.10 being EOL. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-15573) Python 3.8 fails to execute cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-15573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17077015#comment-17077015
]
Eduard Tudenhoefner edited comment on CASSANDRA-15573 at 4/9/20, 7:19 AM:
--
||[Patch|https://github.com/apache/cassandra/pull/518]||[CircleCI|https://app.circleci.com/pipelines/github/nastra/cassandra?branch=CASSANDRA-15573]||[Docker
Image update|https://github.com/apache/cassandra-builds/pull/17]||
was (Author: eduard.tudenhoefner):
||[Patch|https://github.com/apache/cassandra/pull/518]||[CircleCI|https://app.circleci.com/pipelines/github/nastra/cassandra/18/workflows/0549d320-a53d-4bff-b8d8-56d1a4ccc8bf]||[Docker
Image update|https://github.com/apache/cassandra-builds/pull/17]||
> Python 3.8 fails to execute cqlsh
> -
>
> Key: CASSANDRA-15573
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15573
> Project: Cassandra
> Issue Type: Sub-task
> Components: Tool/cqlsh
>Reporter: Yuki Morishita
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Python 3.8 renamed sre_parse.Pattern to sre_parse.State (see
> [https://bugs.python.org/issue34681] and corresponding pull request
> [https://github.com/python/cpython/pull/9310])
> So when executing cqlsh with Python 3.8, it throws error:
> {code:java}
> Traceback (most recent call last):
> File ".\bin\cqlsh.py", line 175, in
> from cqlshlib import cql3handling, cqlhandling, pylexotron, sslhandling,
> cqlshhandling
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cql3handling.py", line 19,
> in
> from cqlshlib.cqlhandling import CqlParsingRuleSet, Hint
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cqlhandling.py", line 23,
> in
> from cqlshlib import pylexotron, util
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 342,
> in
> class ParsingRuleSet:
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 343,
> in ParsingRuleSet
> RuleSpecScanner = SaferScanner([
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\saferscanner.py", line 74,
> in __init__
> s = re.sre_parse.Pattern()
> AttributeError: module 'sre_parse' has no attribute 'Pattern'
> {code}
> h2. Summary of Work that was done
> Added a Python 3.8 compatible SaferScanner implementation ([diff
> here|https://github.com/apache/cassandra/pull/518/commits/2e6813f0ef5817e5d8d655052d61ce75a5fc062c]).
> Note that the changes from CASSANDRA-15659 are required in order to verify
> that the issue is fixed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-15706) Fix cqlsh completion test
[
https://issues.apache.org/jira/browse/CASSANDRA-15706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17078039#comment-17078039
]
Eduard Tudenhoefner edited comment on CASSANDRA-15706 at 4/9/20, 7:04 AM:
--
Relevant cqlsh test on Jenkins is
[here|https://ci-cassandra.apache.org/job/Cassandra-devbranch-cqlsh-tests/34/],
which shows that the test is fixed
was (Author: eduard.tudenhoefner):
Relevant cqlsh test on Jenkins is
[here|https://ci-cassandra.apache.org/job/Cassandra-devbranch-cqlsh-tests/34/]
> Fix cqlsh completion test
> -
>
> Key: CASSANDRA-15706
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15706
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Testing
>Reporter: Eduard Tudenhoefner
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This has been failing for a while now because *system_views* and
> *system_virtual_schema* are occuring in the completion.
> {code}
> cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion.test_complete_in_drop_keyspace
> (from nosetests)
> Failing for the past 1 build (Since Unstable#42 )
> Took 2 sec.
> Error Message
> Items in the second set but not the first:
> 'system_views'
> 'system_virtual_schema'
> """Fail immediately, with the given message."""
> >> raise self.failureException("Items in the second set but not the
> >> first:\n'system_views'\n'system_virtual_schema'")
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15707) Fix cqlsh output test
[
https://issues.apache.org/jira/browse/CASSANDRA-15707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17078988#comment-17078988
]
Eduard Tudenhoefner commented on CASSANDRA-15707:
-
Relevant cqlsh test on Jenkins is
[here|https://ci-cassandra.apache.org/job/Cassandra-devbranch-cqlsh-tests/35/],
which shows that the test is fixed
> Fix cqlsh output test
> -
>
> Key: CASSANDRA-15707
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15707
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Eduard Tudenhoefner
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> https://ci-cassandra.apache.org/view/branches/job/Cassandra-trunk/45/testReport/cqlshlib.test.test_cqlsh_output/TestCqlshOutput/
> {code}
> Sequences differ: ['CRE[438 chars]nt', ") WITH additional_write_policy =
> '99p'",[710 chars], ''] != ['CRE[438 chars]nt', ') WITH
> bloom_filter_fp_chance = 0.01', "[711 chars], '']
> First differing element 17:
> ") WITH additional_write_policy = '99p'"
> ') WITH bloom_filter_fp_chance = 0.01'
> Diff is 1475 characters long. Set self.maxDiff to None to see it.
> """Fail immediately, with the given message."""
> >> raise self.failureException('Sequences differ: [\'CRE[438 chars]nt\', ")
> >> WITH additional_write_policy = \'99p\'",[710 chars], \'\'] != [\'CRE[438
> >> chars]nt\', \') WITH bloom_filter_fp_chance = 0.01\', "[711 chars],
> >> \'\']\n\nFirst differing element 17:\n") WITH additional_write_policy =
> >> \'99p\'"\n\') WITH bloom_filter_fp_chance = 0.01\'\n\nDiff is 1475
> >> characters long. Set self.maxDiff to None to see it.')
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-15706) Fix cqlsh completion test
[
https://issues.apache.org/jira/browse/CASSANDRA-15706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17078039#comment-17078039
]
Eduard Tudenhoefner edited comment on CASSANDRA-15706 at 4/9/20, 7:01 AM:
--
Relevant cqlsh test on Jenkins is
[here|https://ci-cassandra.apache.org/job/Cassandra-devbranch-cqlsh-tests/34/]
was (Author: eduard.tudenhoefner):
Tests on Jenkins
[here|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/35/pipeline/]
> Fix cqlsh completion test
> -
>
> Key: CASSANDRA-15706
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15706
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Testing
>Reporter: Eduard Tudenhoefner
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This has been failing for a while now because *system_views* and
> *system_virtual_schema* are occuring in the completion.
> {code}
> cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion.test_complete_in_drop_keyspace
> (from nosetests)
> Failing for the past 1 build (Since Unstable#42 )
> Took 2 sec.
> Error Message
> Items in the second set but not the first:
> 'system_views'
> 'system_virtual_schema'
> """Fail immediately, with the given message."""
> >> raise self.failureException("Items in the second set but not the
> >> first:\n'system_views'\n'system_virtual_schema'")
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15707) Fix cqlsh output test
[
https://issues.apache.org/jira/browse/CASSANDRA-15707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15707:
Bug Category: Parent values: Correctness(12982)
Complexity: Low Hanging Fruit
Discovered By: Unit Test
Fix Version/s: 4.0-alpha
Severity: Low
Status: Open (was: Triage Needed)
> Fix cqlsh output test
> -
>
> Key: CASSANDRA-15707
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15707
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Eduard Tudenhoefner
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://ci-cassandra.apache.org/view/branches/job/Cassandra-trunk/45/testReport/cqlshlib.test.test_cqlsh_output/TestCqlshOutput/
> {code}
> Sequences differ: ['CRE[438 chars]nt', ") WITH additional_write_policy =
> '99p'",[710 chars], ''] != ['CRE[438 chars]nt', ') WITH
> bloom_filter_fp_chance = 0.01', "[711 chars], '']
> First differing element 17:
> ") WITH additional_write_policy = '99p'"
> ') WITH bloom_filter_fp_chance = 0.01'
> Diff is 1475 characters long. Set self.maxDiff to None to see it.
> """Fail immediately, with the given message."""
> >> raise self.failureException('Sequences differ: [\'CRE[438 chars]nt\', ")
> >> WITH additional_write_policy = \'99p\'",[710 chars], \'\'] != [\'CRE[438
> >> chars]nt\', \') WITH bloom_filter_fp_chance = 0.01\', "[711 chars],
> >> \'\']\n\nFirst differing element 17:\n") WITH additional_write_policy =
> >> \'99p\'"\n\') WITH bloom_filter_fp_chance = 0.01\'\n\nDiff is 1475
> >> characters long. Set self.maxDiff to None to see it.')
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15707) Fix cqlsh output test
[
https://issues.apache.org/jira/browse/CASSANDRA-15707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15707:
Test and Documentation Plan: nosetests test/test_cqlsh_output.py
Status: Patch Available (was: In Progress)
Passes now locally
{code}
$ nosetests test/test_cqlsh_output.py
nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$']
test_blob_output (cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ... ok
test_boolean_output (cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ... ok
test_cancel_statement (cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ... ok
test_color_output (cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ... ok
test_columnless_key_output (cqlshlib.test.test_cqlsh_output.TestCqlshOutput)
... ok
test_count_output (cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ... ok
test_describe_cluster_output (cqlshlib.test.test_cqlsh_output.TestCqlshOutput)
... ok
test_describe_columnfamilies_output
(cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ... ok
test_describe_columnfamily_output
(cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ... ok
test_describe_keyspace_output (cqlshlib.test.test_cqlsh_output.TestCqlshOutput)
... ok
test_describe_schema_output (cqlshlib.test.test_cqlsh_output.TestCqlshOutput)
... ok
test_empty_cf_output (cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ... ok
test_empty_line (cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ... ok
test_eof_prints_newline (cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ... ok
test_exit_prints_no_newline (cqlshlib.test.test_cqlsh_output.TestCqlshOutput)
... ok
test_help (cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ... ok
test_help_types (cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ... ok
test_multiline_statements (cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ...
ok
test_no_color_output (cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ... ok
test_no_prompt_or_colors_output
(cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ... ok
test_null_output (cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ... ok
test_numeric_output (cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ... ok
test_printing_cql_error (cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ... ok
test_printing_integrity_error (cqlshlib.test.test_cqlsh_output.TestCqlshOutput)
... ok
test_printing_lex_error (cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ... ok
test_printing_parse_error (cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ...
ok
test_prompt (cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ... ok
test_show_output (cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ... ok
test_static_cf_output (cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ... ok
test_string_output_ascii (cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ...
ok
test_string_output_utf8 (cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ... ok
test_timestamp_output (cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ... ok
test_user_types_output (cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ... ok
test_user_types_with_collections
(cqlshlib.test.test_cqlsh_output.TestCqlshOutput) ... ok
cqlshlib.test.test_cqlsh_output.testrun_cqlsh ... ok
cqlshlib.test.test_cqlsh_output.testcall_cqlsh ... ok
--
XML: /home/nastra/Development/workspace/cassandra/pylib/cqlshlib/nosetests.xml
--
Ran 36 tests in 24.021s
OK
{code}
> Fix cqlsh output test
> -
>
> Key: CASSANDRA-15707
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15707
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Eduard Tudenhoefner
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://ci-cassandra.apache.org/view/branches/job/Cassandra-trunk/45/testReport/cqlshlib.test.test_cqlsh_output/TestCqlshOutput/
> {code}
> Sequences differ: ['CRE[438 chars]nt', ") WITH additional_write_policy =
> '99p'",[710 chars], ''] != ['CRE[438 chars]nt', ') WITH
> bloom_filter_fp_chance = 0.01', "[711 chars], '']
> First differing element 17:
> ") WITH additional_write_policy = '99p'"
> ') WITH bloom_filter_fp_chance = 0.01'
> Diff is 1475 characters long. Set self.maxDiff to None to see it.
> """Fail immediately, with the given message."""
> >> raise self.failureException('Sequences differ: [\'CRE[438 chars]nt\', ")
> >> WITH additional_write_policy = \'99p\'",[710 chars], \'\'] != [\'CRE[438
> >> chars]nt\', \') WITH bloom_filter_fp_chance = 0.01\', "[711 chars],
> >> \'\']\n\nFirst differing element 17:\n") WITH additional_write_policy =
> >>
[jira] [Assigned] (CASSANDRA-15707) Fix cqlsh output test
[
https://issues.apache.org/jira/browse/CASSANDRA-15707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner reassigned CASSANDRA-15707:
---
Assignee: Eduard Tudenhoefner
> Fix cqlsh output test
> -
>
> Key: CASSANDRA-15707
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15707
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Eduard Tudenhoefner
>Assignee: Eduard Tudenhoefner
>Priority: Normal
>
> https://ci-cassandra.apache.org/view/branches/job/Cassandra-trunk/45/testReport/cqlshlib.test.test_cqlsh_output/TestCqlshOutput/
> {code}
> Sequences differ: ['CRE[438 chars]nt', ") WITH additional_write_policy =
> '99p'",[710 chars], ''] != ['CRE[438 chars]nt', ') WITH
> bloom_filter_fp_chance = 0.01', "[711 chars], '']
> First differing element 17:
> ") WITH additional_write_policy = '99p'"
> ') WITH bloom_filter_fp_chance = 0.01'
> Diff is 1475 characters long. Set self.maxDiff to None to see it.
> """Fail immediately, with the given message."""
> >> raise self.failureException('Sequences differ: [\'CRE[438 chars]nt\', ")
> >> WITH additional_write_policy = \'99p\'",[710 chars], \'\'] != [\'CRE[438
> >> chars]nt\', \') WITH bloom_filter_fp_chance = 0.01\', "[711 chars],
> >> \'\']\n\nFirst differing element 17:\n") WITH additional_write_policy =
> >> \'99p\'"\n\') WITH bloom_filter_fp_chance = 0.01\'\n\nDiff is 1475
> >> characters long. Set self.maxDiff to None to see it.')
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15706) Fix cqlsh completion test
[
https://issues.apache.org/jira/browse/CASSANDRA-15706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17078039#comment-17078039
]
Eduard Tudenhoefner commented on CASSANDRA-15706:
-
Tests on Jenkins
[here|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/35/pipeline/]
> Fix cqlsh completion test
> -
>
> Key: CASSANDRA-15706
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15706
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Testing
>Reporter: Eduard Tudenhoefner
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This has been failing for a while now because *system_views* and
> *system_virtual_schema* are occuring in the completion.
> {code}
> cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion.test_complete_in_drop_keyspace
> (from nosetests)
> Failing for the past 1 build (Since Unstable#42 )
> Took 2 sec.
> Error Message
> Items in the second set but not the first:
> 'system_views'
> 'system_virtual_schema'
> """Fail immediately, with the given message."""
> >> raise self.failureException("Items in the second set but not the
> >> first:\n'system_views'\n'system_virtual_schema'")
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15707) Fix cqlsh output test
Eduard Tudenhoefner created CASSANDRA-15707:
---
Summary: Fix cqlsh output test
Key: CASSANDRA-15707
URL: https://issues.apache.org/jira/browse/CASSANDRA-15707
Project: Cassandra
Issue Type: Bug
Components: Test/unit
Reporter: Eduard Tudenhoefner
https://ci-cassandra.apache.org/view/branches/job/Cassandra-trunk/45/testReport/cqlshlib.test.test_cqlsh_output/TestCqlshOutput/
{code}
Sequences differ: ['CRE[438 chars]nt', ") WITH additional_write_policy =
'99p'",[710 chars], ''] != ['CRE[438 chars]nt', ') WITH bloom_filter_fp_chance
= 0.01', "[711 chars], '']
First differing element 17:
") WITH additional_write_policy = '99p'"
') WITH bloom_filter_fp_chance = 0.01'
Diff is 1475 characters long. Set self.maxDiff to None to see it.
"""Fail immediately, with the given message."""
>> raise self.failureException('Sequences differ: [\'CRE[438 chars]nt\', ")
>> WITH additional_write_policy = \'99p\'",[710 chars], \'\'] != [\'CRE[438
>> chars]nt\', \') WITH bloom_filter_fp_chance = 0.01\', "[711 chars],
>> \'\']\n\nFirst differing element 17:\n") WITH additional_write_policy =
>> \'99p\'"\n\') WITH bloom_filter_fp_chance = 0.01\'\n\nDiff is 1475
>> characters long. Set self.maxDiff to None to see it.')
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15706) Fix cqlsh completion test
[
https://issues.apache.org/jira/browse/CASSANDRA-15706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17078006#comment-17078006
]
Eduard Tudenhoefner commented on CASSANDRA-15706:
-
{code}
$ nosetests test/test_cqlsh_completion.py
nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$']
test_complete_command_words
(cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion) ... ok
test_complete_in_alter_columnfamily
(cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion) ... ok
test_complete_in_batch
(cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion) ... ok
test_complete_in_create_columnfamily
(cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion) ... ok
test_complete_in_create_index
(cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion) ... ok
test_complete_in_create_keyspace
(cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion) ... ok
test_complete_in_create_table
(cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion) ... ok
test_complete_in_delete
(cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion) ... ok
Tests for Cassandra-10733 ... ok
test_complete_in_drop (cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion)
... ok
test_complete_in_drop_columnfamily
(cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion) ... ok
test_complete_in_drop_index
(cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion) ... ok
test_complete_in_drop_keyspace
(cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion) ... ok
test_complete_in_insert
(cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion) ... ok
test_complete_in_select
(cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion) ... ok
test_complete_in_string_literals
(cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion) ... ok
test_complete_in_truncate
(cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion) ... ok
test_complete_in_update
(cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion) ... ok
test_complete_in_use (cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion)
... ok
test_complete_in_uuid (cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion)
... ok
test_complete_on_empty_string
(cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion) ... ok
cqlshlib.test.test_cqlsh_completion.testrun_cqlsh ... ok
--
XML: /home/nastra/Development/workspace/cassandra/pylib/cqlshlib/nosetests.xml
--
Ran 22 tests in 165.902s
OK
{code}
Passes now locally as well
> Fix cqlsh completion test
> -
>
> Key: CASSANDRA-15706
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15706
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Testing
>Reporter: Eduard Tudenhoefner
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This has been failing for a while now because *system_views* and
> *system_virtual_schema* are occuring in the completion.
> {code}
> cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion.test_complete_in_drop_keyspace
> (from nosetests)
> Failing for the past 1 build (Since Unstable#42 )
> Took 2 sec.
> Error Message
> Items in the second set but not the first:
> 'system_views'
> 'system_virtual_schema'
> """Fail immediately, with the given message."""
> >> raise self.failureException("Items in the second set but not the
> >> first:\n'system_views'\n'system_virtual_schema'")
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15706) Fix cqlsh completion test
[
https://issues.apache.org/jira/browse/CASSANDRA-15706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15706:
Test and Documentation Plan: Start up cqlsh and try *CREATE TABLE ...*
completions. No system keyspaces should show up during completions
Status: Patch Available (was: In Progress)
> Fix cqlsh completion test
> -
>
> Key: CASSANDRA-15706
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15706
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Testing
>Reporter: Eduard Tudenhoefner
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This has been failing for a while now because *system_views* and
> *system_virtual_schema* are occuring in the completion.
> {code}
> cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion.test_complete_in_drop_keyspace
> (from nosetests)
> Failing for the past 1 build (Since Unstable#42 )
> Took 2 sec.
> Error Message
> Items in the second set but not the first:
> 'system_views'
> 'system_virtual_schema'
> """Fail immediately, with the given message."""
> >> raise self.failureException("Items in the second set but not the
> >> first:\n'system_views'\n'system_virtual_schema'")
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15706) Fix cqlsh completion test
[
https://issues.apache.org/jira/browse/CASSANDRA-15706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15706:
Bug Category: Parent values: Correctness(12982)
Complexity: Low Hanging Fruit
Discovered By: Unit Test
Fix Version/s: 4.0-alpha
Severity: Low
Status: Open (was: Triage Needed)
> Fix cqlsh completion test
> -
>
> Key: CASSANDRA-15706
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15706
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Testing
>Reporter: Eduard Tudenhoefner
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Fix For: 4.0-alpha
>
>
> This has been failing for a while now because *system_views* and
> *system_virtual_schema* are occuring in the completion.
> {code}
> cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion.test_complete_in_drop_keyspace
> (from nosetests)
> Failing for the past 1 build (Since Unstable#42 )
> Took 2 sec.
> Error Message
> Items in the second set but not the first:
> 'system_views'
> 'system_virtual_schema'
> """Fail immediately, with the given message."""
> >> raise self.failureException("Items in the second set but not the
> >> first:\n'system_views'\n'system_virtual_schema'")
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15706) Fix cqlsh completion test
Eduard Tudenhoefner created CASSANDRA-15706:
---
Summary: Fix cqlsh completion test
Key: CASSANDRA-15706
URL: https://issues.apache.org/jira/browse/CASSANDRA-15706
Project: Cassandra
Issue Type: Bug
Components: Legacy/Testing
Reporter: Eduard Tudenhoefner
Assignee: Eduard Tudenhoefner
This has been failing for a while now because *system_views* and
*system_virtual_schema* are occuring in the completion.
{code}
cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion.test_complete_in_drop_keyspace
(from nosetests)
Failing for the past 1 build (Since Unstable#42 )
Took 2 sec.
Error Message
Items in the second set but not the first:
'system_views'
'system_virtual_schema'
"""Fail immediately, with the given message."""
>> raise self.failureException("Items in the second set but not the
>> first:\n'system_views'\n'system_virtual_schema'")
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15676) flaky test testWriteUnknownResult- org.apache.cassandra.distributed.test.CasWriteTest
[
https://issues.apache.org/jira/browse/CASSANDRA-15676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17077964#comment-17077964
]
Eduard Tudenhoefner commented on CASSANDRA-15676:
-
For completeness, here's the history on Jenkins:
https://ci-cassandra.apache.org/view/branches/job/Cassandra-trunk/45/testReport/junit/org.apache.cassandra.distributed.test/CasWriteTest/history/
> flaky test testWriteUnknownResult-
> org.apache.cassandra.distributed.test.CasWriteTest
> -
>
> Key: CASSANDRA-15676
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15676
> Project: Cassandra
> Issue Type: Task
> Components: Test/dtest
>Reporter: Kevin Gallardo
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Fix For: 4.0-beta
>
>
> Failure observed in:
> https://app.circleci.com/pipelines/github/newkek/cassandra/33/workflows/54007cf7-4424-4ec1-9655-665f6044e6d1/jobs/187/tests
> {noformat}
> testWriteUnknownResult - org.apache.cassandra.distributed.test.CasWriteTest
> junit.framework.AssertionFailedError: Expecting cause to be
> CasWriteUncertainException
> at
> org.apache.cassandra.distributed.test.CasWriteTest.testWriteUnknownResult(CasWriteTest.java:257)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15313) Fix flaky - ChecksummingTransformerTest - org.apache.cassandra.transport.frame.checksum.ChecksummingTransformerTest
[
https://issues.apache.org/jira/browse/CASSANDRA-15313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17077959#comment-17077959
]
Eduard Tudenhoefner commented on CASSANDRA-15313:
-
For completeness, here's the Jenkins history for this test failure:
https://ci-cassandra.apache.org/view/branches/job/Cassandra-trunk/45/testReport/junit/org.apache.cassandra.transport.frame.checksum/ChecksummingTransformerTest/history/
> Fix flaky - ChecksummingTransformerTest -
> org.apache.cassandra.transport.frame.checksum.ChecksummingTransformerTest
> ---
>
> Key: CASSANDRA-15313
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15313
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest
>Reporter: Vinay Chella
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.0-beta
>
> Attachments: CASSANDRA-15313-hack.patch
>
>
> During the recent runs, this test appears to be flaky.
> Example failure:
> [https://circleci.com/gh/vinaykumarchella/cassandra/459#tests/containers/94]
> corruptionCausesFailure-compression -
> org.apache.cassandra.transport.frame.checksum.ChecksummingTransformerTest
> {code:java}
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> at java.nio.HeapByteBuffer.(HeapByteBuffer.java:57)
> at java.nio.ByteBuffer.allocate(ByteBuffer.java:335)
> at org.quicktheories.impl.Precursor.(Precursor.java:17)
> at
> org.quicktheories.impl.ConcreteDetachedSource.(ConcreteDetachedSource.java:8)
> at
> org.quicktheories.impl.ConcreteDetachedSource.detach(ConcreteDetachedSource.java:23)
> at org.quicktheories.generators.Retry.generate(CodePoints.java:51)
> at
> org.quicktheories.generators.Generate.lambda$intArrays$10(Generate.java:190)
> at
> org.quicktheories.generators.Generate$$Lambda$17/1847008471.generate(Unknown
> Source)
> at org.quicktheories.core.DescribingGenerator.generate(Gen.java:255)
> at org.quicktheories.core.Gen.lambda$map$0(Gen.java:36)
> at org.quicktheories.core.Gen$$Lambda$20/71399214.generate(Unknown
> Source)
> at org.quicktheories.core.Gen.lambda$map$0(Gen.java:36)
> at org.quicktheories.core.Gen$$Lambda$20/71399214.generate(Unknown
> Source)
> at org.quicktheories.core.Gen.lambda$mix$10(Gen.java:184)
> at org.quicktheories.core.Gen$$Lambda$45/802243390.generate(Unknown
> Source)
> at org.quicktheories.core.Gen.lambda$flatMap$5(Gen.java:93)
> at org.quicktheories.core.Gen$$Lambda$48/363509958.generate(Unknown
> Source)
> at
> org.quicktheories.dsl.TheoryBuilder4.lambda$prgnToTuple$12(TheoryBuilder4.java:188)
> at
> org.quicktheories.dsl.TheoryBuilder4$$Lambda$40/2003496028.generate(Unknown
> Source)
> at org.quicktheories.core.DescribingGenerator.generate(Gen.java:255)
> at org.quicktheories.core.FilteredGenerator.generate(Gen.java:225)
> at org.quicktheories.core.Gen.lambda$map$0(Gen.java:36)
> at org.quicktheories.core.Gen$$Lambda$20/71399214.generate(Unknown
> Source)
> at org.quicktheories.impl.Core.generate(Core.java:150)
> at org.quicktheories.impl.Core.shrink(Core.java:103)
> at org.quicktheories.impl.Core.run(Core.java:39)
> at org.quicktheories.impl.TheoryRunner.check(TheoryRunner.java:35)
> at org.quicktheories.dsl.TheoryBuilder4.check(TheoryBuilder4.java:150)
> at
> org.quicktheories.dsl.TheoryBuilder4.checkAssert(TheoryBuilder4.java:162)
> at
> org.apache.cassandra.transport.frame.checksum.ChecksummingTransformerTest.corruptionCausesFailure(ChecksummingTransformerTest.java:87)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15551) Fix flaky tests org.apache.cassandra.service.MoveTest testStateJumpToNormal and testMoveWithPendingRangesNetworkStrategyRackAwareThirtyNodes
[
https://issues.apache.org/jira/browse/CASSANDRA-15551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17077953#comment-17077953
]
Eduard Tudenhoefner commented on CASSANDRA-15551:
-
According to
https://ci-cassandra.apache.org/view/branches/job/Cassandra-trunk/45/testReport/junit/org.apache.cassandra.service/MoveTest/history/
this hasn't been failing in a while. Can we close this ticket?
> Fix flaky tests org.apache.cassandra.service.MoveTest testStateJumpToNormal
> and testMoveWithPendingRangesNetworkStrategyRackAwareThirtyNodes
>
>
> Key: CASSANDRA-15551
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15551
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: David Capwell
>Assignee: Gianluca Righetto
>Priority: Normal
> Fix For: 4.0-alpha
>
>
> testStateJumpToNormal failure was on java 11
> {code}
> java.lang.NullPointerException
> at org.apache.cassandra.gms.Gossiper.getHostId(Gossiper.java:1028)
> at org.apache.cassandra.gms.Gossiper.getHostId(Gossiper.java:1023)
> at
> org.apache.cassandra.service.StorageService.handleStateNormal(StorageService.java:2513)
> at
> org.apache.cassandra.service.StorageService.onChange(StorageService.java:2055)
> at org.apache.cassandra.Util.createInitialRing(Util.java:225)
> at
> org.apache.cassandra.service.MoveTest.testStateJumpToNormal(MoveTest.java:935)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
> testMoveWithPendingRangesNetworkStrategyRackAwareThirtyNodes failure was on
> java 8
> {code}
> java.lang.NullPointerException
> at
> org.apache.cassandra.service.StorageService.updatePeerInfo(StorageService.java:2174)
> at
> org.apache.cassandra.service.StorageService.handleStateNormal(StorageService.java:2511)
> at
> org.apache.cassandra.service.StorageService.onChange(StorageService.java:2055)
> at org.apache.cassandra.Util.createInitialRing(Util.java:225)
> at
> org.apache.cassandra.service.MoveTest.testMoveWithPendingRangesNetworkStrategyRackAwareThirtyNodes(MoveTest.java:199)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15573) Python 3.8 fails to execute cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-15573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17077856#comment-17077856
]
Eduard Tudenhoefner commented on CASSANDRA-15573:
-
[~djoshi] I completely agree that testing with all sorts of Python versions
won't be feasible. That's why I aimed for adding additional testing for Python
3.8 only as part of CASSANDRA-15659, since I had to make sure that the problem
is actually fixed in a newer Python version.
I think once CASSANDRA-15659 and CASSANDRA-15573 are in, we could tackle of how
and what versions of Python to test. wdyt?
I'm not familiar with tox, but I'm more than happy to take a look at it in
order to simplify Python testing.
> Python 3.8 fails to execute cqlsh
> -
>
> Key: CASSANDRA-15573
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15573
> Project: Cassandra
> Issue Type: Sub-task
> Components: Tool/cqlsh
>Reporter: Yuki Morishita
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Python 3.8 renamed sre_parse.Pattern to sre_parse.State (see
> [https://bugs.python.org/issue34681] and corresponding pull request
> [https://github.com/python/cpython/pull/9310])
> So when executing cqlsh with Python 3.8, it throws error:
> {code:java}
> Traceback (most recent call last):
> File ".\bin\cqlsh.py", line 175, in
> from cqlshlib import cql3handling, cqlhandling, pylexotron, sslhandling,
> cqlshhandling
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cql3handling.py", line 19,
> in
> from cqlshlib.cqlhandling import CqlParsingRuleSet, Hint
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cqlhandling.py", line 23,
> in
> from cqlshlib import pylexotron, util
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 342,
> in
> class ParsingRuleSet:
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 343,
> in ParsingRuleSet
> RuleSpecScanner = SaferScanner([
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\saferscanner.py", line 74,
> in __init__
> s = re.sre_parse.Pattern()
> AttributeError: module 'sre_parse' has no attribute 'Pattern'
> {code}
> h2. Summary of Work that was done
> Added a Python 3.8 compatible SaferScanner implementation ([diff
> here|https://github.com/apache/cassandra/pull/518/commits/2e6813f0ef5817e5d8d655052d61ce75a5fc062c]).
> Note that the changes from CASSANDRA-15659 are required in order to verify
> that the issue is fixed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15702) copyutil.py uses Exception.message which doesn't exist in Python 3
[ https://issues.apache.org/jira/browse/CASSANDRA-15702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-15702: Test and Documentation Plan: https://github.com/apache/cassandra/pull/521 Status: Patch Available (was: In Progress) > copyutil.py uses Exception.message which doesn't exist in Python 3 > -- > > Key: CASSANDRA-15702 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15702 > Project: Cassandra > Issue Type: Bug > Components: Tool/cqlsh >Reporter: Eduard Tudenhoefner >Assignee: Eduard Tudenhoefner >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Time Spent: 10m > Remaining Estimate: 0h > > Python 3 deprecated and removed the use of Exception.message. The purpose of > this ticket is to convert *Exception.message* to something that is Python 3 > compatible -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15702) copyutil.py uses Exception.message which doesn't exist in Python 3
[ https://issues.apache.org/jira/browse/CASSANDRA-15702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-15702: Bug Category: Parent values: Correctness(12982) Complexity: Low Hanging Fruit Discovered By: Adhoc Test Severity: Low Status: Open (was: Triage Needed) > copyutil.py uses Exception.message which doesn't exist in Python 3 > -- > > Key: CASSANDRA-15702 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15702 > Project: Cassandra > Issue Type: Bug > Components: Tool/cqlsh >Reporter: Eduard Tudenhoefner >Assignee: Eduard Tudenhoefner >Priority: Normal > Fix For: 4.0-alpha > > > Python 3 deprecated and removed the use of Exception.message. The purpose of > this ticket is to convert *Exception.message* to something that is Python 3 > compatible -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15702) copyutil.py uses Exception.message which doesn't exist in Python 3
[ https://issues.apache.org/jira/browse/CASSANDRA-15702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-15702: Fix Version/s: 4.0-alpha > copyutil.py uses Exception.message which doesn't exist in Python 3 > -- > > Key: CASSANDRA-15702 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15702 > Project: Cassandra > Issue Type: Bug > Components: Tool/cqlsh >Reporter: Eduard Tudenhoefner >Assignee: Eduard Tudenhoefner >Priority: Normal > Fix For: 4.0-alpha > > > Python 3 deprecated and removed the use of Exception.message. The purpose of > this ticket is to convert *Exception.message* to something that is Python 3 > compatible -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15702) copyutil.py uses Exception.message which doesn't exist in Python 3
Eduard Tudenhoefner created CASSANDRA-15702: --- Summary: copyutil.py uses Exception.message which doesn't exist in Python 3 Key: CASSANDRA-15702 URL: https://issues.apache.org/jira/browse/CASSANDRA-15702 Project: Cassandra Issue Type: Bug Components: Tool/cqlsh Reporter: Eduard Tudenhoefner Assignee: Eduard Tudenhoefner Python 3 deprecated and removed the use of Exception.message. The purpose of this ticket is to convert *Exception.message* to something that is Python 3 compatible -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15573) Python 3.8 fails to execute cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-15573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15573:
Description:
Python 3.8 renamed sre_parse.Pattern to sre_parse.State (see
[https://bugs.python.org/issue34681] and corresponding pull request
[https://github.com/python/cpython/pull/9310])
So when executing cqlsh with Python 3.8, it throws error:
{code:java}
Traceback (most recent call last):
File ".\bin\cqlsh.py", line 175, in
from cqlshlib import cql3handling, cqlhandling, pylexotron, sslhandling,
cqlshhandling
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cql3handling.py", line 19,
in
from cqlshlib.cqlhandling import CqlParsingRuleSet, Hint
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cqlhandling.py", line 23, in
from cqlshlib import pylexotron, util
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 342, in
class ParsingRuleSet:
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 343, in
ParsingRuleSet
RuleSpecScanner = SaferScanner([
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\saferscanner.py", line 74,
in __init__
s = re.sre_parse.Pattern()
AttributeError: module 'sre_parse' has no attribute 'Pattern'
{code}
h2. Summary of Work that was done
Added a Python 3.8 compatible SaferScanner implementation ([diff
here|https://github.com/apache/cassandra/pull/518/commits/2e6813f0ef5817e5d8d655052d61ce75a5fc062c]).
Note that the changes from CASSANDRA-15659 are required in order to verify
that the issue is fixed.
was:
Python 3.8 renamed sre_parse.Pattern to sre_parse.State (see
[https://bugs.python.org/issue34681] and corresponding pull request
[https://github.com/python/cpython/pull/9310])
So when executing cqlsh with Python 3.8, it throws error:
{code:java}
Traceback (most recent call last):
File ".\bin\cqlsh.py", line 175, in
from cqlshlib import cql3handling, cqlhandling, pylexotron, sslhandling,
cqlshhandling
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cql3handling.py", line 19,
in
from cqlshlib.cqlhandling import CqlParsingRuleSet, Hint
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cqlhandling.py", line 23, in
from cqlshlib import pylexotron, util
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 342, in
class ParsingRuleSet:
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 343, in
ParsingRuleSet
RuleSpecScanner = SaferScanner([
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\saferscanner.py", line 74,
in __init__
s = re.sre_parse.Pattern()
AttributeError: module 'sre_parse' has no attribute 'Pattern'
{code}
h2. Summary of Work that was done
Added a Python 3.8 compatible SaferScanner implementation. Note that the
changes from CASSANDRA-15659 are required in order to verify that the issue is
fixed.
> Python 3.8 fails to execute cqlsh
> -
>
> Key: CASSANDRA-15573
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15573
> Project: Cassandra
> Issue Type: Sub-task
> Components: Tool/cqlsh
>Reporter: Yuki Morishita
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Python 3.8 renamed sre_parse.Pattern to sre_parse.State (see
> [https://bugs.python.org/issue34681] and corresponding pull request
> [https://github.com/python/cpython/pull/9310])
> So when executing cqlsh with Python 3.8, it throws error:
> {code:java}
> Traceback (most recent call last):
> File ".\bin\cqlsh.py", line 175, in
> from cqlshlib import cql3handling, cqlhandling, pylexotron, sslhandling,
> cqlshhandling
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cql3handling.py", line 19,
> in
> from cqlshlib.cqlhandling import CqlParsingRuleSet, Hint
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cqlhandling.py", line 23,
> in
> from cqlshlib import pylexotron, util
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 342,
> in
> class ParsingRuleSet:
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 343,
> in ParsingRuleSet
> RuleSpecScanner = SaferScanner([
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\saferscanner.py", line 74,
> in __init__
> s = re.sre_parse.Pattern()
> AttributeError: module
[jira] [Updated] (CASSANDRA-15573) Python 3.8 fails to execute cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-15573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15573:
Description:
Python 3.8 renamed sre_parse.Pattern to sre_parse.State (see
[https://bugs.python.org/issue34681] and corresponding pull request
[https://github.com/python/cpython/pull/9310])
So when executing cqlsh with Python 3.8, it throws error:
{code:java}
Traceback (most recent call last):
File ".\bin\cqlsh.py", line 175, in
from cqlshlib import cql3handling, cqlhandling, pylexotron, sslhandling,
cqlshhandling
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cql3handling.py", line 19,
in
from cqlshlib.cqlhandling import CqlParsingRuleSet, Hint
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cqlhandling.py", line 23, in
from cqlshlib import pylexotron, util
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 342, in
class ParsingRuleSet:
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 343, in
ParsingRuleSet
RuleSpecScanner = SaferScanner([
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\saferscanner.py", line 74,
in __init__
s = re.sre_parse.Pattern()
AttributeError: module 'sre_parse' has no attribute 'Pattern'
{code}
h2. Summary of Work that was done
Added a Python 3.8 compatible SaferScanner implementation. Note that the
changes from CASSANDRA-15659 are required in order to verify that the issue is
fixed.
was:
Python 3.8 renamed sre_parse.Pattern to sre_parse.State (see
https://bugs.python.org/issue34681 and corresponding pull request
https://github.com/python/cpython/pull/9310)
So when executing cqlsh with Python 3.8, it throws error:
{code}
Traceback (most recent call last):
File ".\bin\cqlsh.py", line 175, in
from cqlshlib import cql3handling, cqlhandling, pylexotron, sslhandling,
cqlshhandling
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cql3handling.py", line 19,
in
from cqlshlib.cqlhandling import CqlParsingRuleSet, Hint
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cqlhandling.py", line 23, in
from cqlshlib import pylexotron, util
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 342, in
class ParsingRuleSet:
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 343, in
ParsingRuleSet
RuleSpecScanner = SaferScanner([
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\saferscanner.py", line 74,
in __init__
s = re.sre_parse.Pattern()
AttributeError: module 'sre_parse' has no attribute 'Pattern'
{code}
h2. Summary of Work that was done
Added a Python 3.8 compatible SafeScanner implementation. Note that the changes
from CASSANDRA-15659 are required in order to verify that the issue is fixed.
> Python 3.8 fails to execute cqlsh
> -
>
> Key: CASSANDRA-15573
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15573
> Project: Cassandra
> Issue Type: Sub-task
> Components: Tool/cqlsh
>Reporter: Yuki Morishita
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Python 3.8 renamed sre_parse.Pattern to sre_parse.State (see
> [https://bugs.python.org/issue34681] and corresponding pull request
> [https://github.com/python/cpython/pull/9310])
> So when executing cqlsh with Python 3.8, it throws error:
> {code:java}
> Traceback (most recent call last):
> File ".\bin\cqlsh.py", line 175, in
> from cqlshlib import cql3handling, cqlhandling, pylexotron, sslhandling,
> cqlshhandling
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cql3handling.py", line 19,
> in
> from cqlshlib.cqlhandling import CqlParsingRuleSet, Hint
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cqlhandling.py", line 23,
> in
> from cqlshlib import pylexotron, util
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 342,
> in
> class ParsingRuleSet:
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 343,
> in ParsingRuleSet
> RuleSpecScanner = SaferScanner([
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\saferscanner.py", line 74,
> in __init__
> s = re.sre_parse.Pattern()
> AttributeError: module 'sre_parse' has no attribute 'Pattern'
> {code}
> h2. Summary of Work that was done
> Added a Python 3.8 compatible
[jira] [Updated] (CASSANDRA-15573) Python 3.8 fails to execute cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-15573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15573:
Description:
Python 3.8 renamed sre_parse.Pattern to sre_parse.State (see
https://bugs.python.org/issue34681 and corresponding pull request
https://github.com/python/cpython/pull/9310)
So when executing cqlsh with Python 3.8, it throws error:
{code}
Traceback (most recent call last):
File ".\bin\cqlsh.py", line 175, in
from cqlshlib import cql3handling, cqlhandling, pylexotron, sslhandling,
cqlshhandling
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cql3handling.py", line 19,
in
from cqlshlib.cqlhandling import CqlParsingRuleSet, Hint
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cqlhandling.py", line 23, in
from cqlshlib import pylexotron, util
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 342, in
class ParsingRuleSet:
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 343, in
ParsingRuleSet
RuleSpecScanner = SaferScanner([
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\saferscanner.py", line 74,
in __init__
s = re.sre_parse.Pattern()
AttributeError: module 'sre_parse' has no attribute 'Pattern'
{code}
h2. Summary of Work that was done
Added a Python 3.8 compatible SafeScanner implementation. Note that the changes
from CASSANDRA-15659 are required in order to verify that the issue is fixed.
was:
Python 3.8 renamed sre_parse.Pattern to sre_parse.State (see
https://bugs.python.org/issue34681 and corresponding pull request
https://github.com/python/cpython/pull/9310)
So when executing cqlsh with Python 3.8, it throws error:
{code}
Traceback (most recent call last):
File ".\bin\cqlsh.py", line 175, in
from cqlshlib import cql3handling, cqlhandling, pylexotron, sslhandling,
cqlshhandling
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cql3handling.py", line 19,
in
from cqlshlib.cqlhandling import CqlParsingRuleSet, Hint
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cqlhandling.py", line 23, in
from cqlshlib import pylexotron, util
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 342, in
class ParsingRuleSet:
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 343, in
ParsingRuleSet
RuleSpecScanner = SaferScanner([
File "C:\Users\Yuki
Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\saferscanner.py", line 74,
in __init__
s = re.sre_parse.Pattern()
AttributeError: module 'sre_parse' has no attribute 'Pattern'
{code}
> Python 3.8 fails to execute cqlsh
> -
>
> Key: CASSANDRA-15573
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15573
> Project: Cassandra
> Issue Type: Sub-task
> Components: Tool/cqlsh
>Reporter: Yuki Morishita
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Python 3.8 renamed sre_parse.Pattern to sre_parse.State (see
> https://bugs.python.org/issue34681 and corresponding pull request
> https://github.com/python/cpython/pull/9310)
> So when executing cqlsh with Python 3.8, it throws error:
> {code}
> Traceback (most recent call last):
> File ".\bin\cqlsh.py", line 175, in
> from cqlshlib import cql3handling, cqlhandling, pylexotron, sslhandling,
> cqlshhandling
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cql3handling.py", line 19,
> in
> from cqlshlib.cqlhandling import CqlParsingRuleSet, Hint
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cqlhandling.py", line 23,
> in
> from cqlshlib import pylexotron, util
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 342,
> in
> class ParsingRuleSet:
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 343,
> in ParsingRuleSet
> RuleSpecScanner = SaferScanner([
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\saferscanner.py", line 74,
> in __init__
> s = re.sre_parse.Pattern()
> AttributeError: module 'sre_parse' has no attribute 'Pattern'
> {code}
> h2. Summary of Work that was done
> Added a Python 3.8 compatible SafeScanner implementation. Note that the
> changes from CASSANDRA-15659 are required in order to verify that the issue
> is fixed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CASSANDRA-15573) Python 3.8 fails to execute cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-15573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15573:
Test and Documentation Plan: https://github.com/apache/cassandra/pull/518
Status: Patch Available (was: In Progress)
||[Patch|https://github.com/apache/cassandra/pull/518]||[CircleCI|https://app.circleci.com/pipelines/github/nastra/cassandra/18/workflows/0549d320-a53d-4bff-b8d8-56d1a4ccc8bf]||[Docker
Image update|https://github.com/apache/cassandra-builds/pull/17]||
> Python 3.8 fails to execute cqlsh
> -
>
> Key: CASSANDRA-15573
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15573
> Project: Cassandra
> Issue Type: Sub-task
> Components: Tool/cqlsh
>Reporter: Yuki Morishita
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Python 3.8 renamed sre_parse.Pattern to sre_parse.State (see
> https://bugs.python.org/issue34681 and corresponding pull request
> https://github.com/python/cpython/pull/9310)
> So when executing cqlsh with Python 3.8, it throws error:
> {code}
> Traceback (most recent call last):
> File ".\bin\cqlsh.py", line 175, in
> from cqlshlib import cql3handling, cqlhandling, pylexotron, sslhandling,
> cqlshhandling
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cql3handling.py", line 19,
> in
> from cqlshlib.cqlhandling import CqlParsingRuleSet, Hint
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cqlhandling.py", line 23,
> in
> from cqlshlib import pylexotron, util
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 342,
> in
> class ParsingRuleSet:
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 343,
> in ParsingRuleSet
> RuleSpecScanner = SaferScanner([
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\saferscanner.py", line 74,
> in __init__
> s = re.sre_parse.Pattern()
> AttributeError: module 'sre_parse' has no attribute 'Pattern'
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-15659) Better support of Python 3 for cqlsh
[ https://issues.apache.org/jira/browse/CASSANDRA-15659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17077009#comment-17077009 ] Eduard Tudenhoefner edited comment on CASSANDRA-15659 at 4/7/20, 7:43 AM: -- ||Pull Request||Tests||Docker Image|| |[PR#505|https://github.com/apache/cassandra/pull/505]|[CircleCI|https://app.circleci.com/pipelines/github/nastra/cassandra/19/workflows/dc0a8771-321f-40bf-a5e8-6e05b20bbca1]|[PR|https://github.com/apache/cassandra-builds/pull/17] Note that the test failures when testing with Python 3.8 are due to CASSANDRA-15573 and should be fixed in [this|https://app.circleci.com/pipelines/github/nastra/cassandra/18/workflows/0549d320-a53d-4bff-b8d8-56d1a4ccc8bf] test run. was (Author: eduard.tudenhoefner): ||Pull Request||Tests||Docker Image|| |[PR#505|https://github.com/apache/cassandra/pull/505]|[CircleCI|https://app.circleci.com/pipelines/github/nastra/cassandra/19/workflows/dc0a8771-321f-40bf-a5e8-6e05b20bbca1]|[PR|https://github.com/apache/cassandra-builds/pull/17] Note that the test failures when testing with Python 3.8 are due to CASSANDRA-15573. > Better support of Python 3 for cqlsh > > > Key: CASSANDRA-15659 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15659 > Project: Cassandra > Issue Type: Task > Components: Tool/cqlsh >Reporter: Stefan Miklosovic >Assignee: Eduard Tudenhoefner >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Time Spent: 40m > Remaining Estimate: 0h > > h2. From mailing list: > [https://lists.apache.org/thread.html/r377099b632c62b641e4feef5b738084fc5369b0c7157fae867853597%40%3Cdev.cassandra.apache.org%3E] > > As of today (24/3/2020) and current trunk, there is Python 3.6 supported (1) > but there is not any 3.6 version ootb in Debian for example. E.g. Buster has > Python 3.7 and other (recent) releases have version 2.7. This means that if > one wants to use Python 3 in Debian, he has to use 3.6 but it is not in the > repository so he has to download / compile / install it on his own. > There should be some sane Python 3 version supported which is as well present > in Debian repository (or requirement to run with 3.6 should be relaxed) . > (1) > [https://github.com/apache/cassandra/blob/bf9a1d487b9ba469e8d740cf7d1cd419535a7e79/bin/cqlsh#L57-L65] > h2. Summary of work that was done: > I relaxed the requirement of *cqlsh* only working with Python 2.7 & 3.6 by > allowing Python 3.6+. > Note that I left the constraint for Python 3.6 being the minimum Python3 > version. > As [~ptbannister] pointed out, we could remove the Python 3.6 min version > once we remove Python 2.7 support, as otherwise testing with lots of > different Python versions will get costly. > 2 Dockerfiles were added in *pylib* for minimal local testing of *cqlsh* > starting up with Python 3.7 & 3.8 and that both revealed > CASSANDRA-15572 and CASSANDRA-15573. > CASSANDRA-15572 was fixed here as it was a one-liner. And I'm going to > tackle CASSANDRA-15573 later. > Python 3.8 testing was added to the CircleCI config so that we can actually > see what else breaks with newer Python versions. > A new Docker images with Ubuntu 19.10 was required for testing > ([https://github.com/apache/cassandra-builds/pull/17]). This docker image > sets up Python 2.7/3.6/3.7/3.8 with their respective virtual environments, > which are then being used by the CircleCI yaml. > The image *spod/cassandra-testing-ubuntu1810-java11-w-dependencies:20190306* > couldn't be updated unfortunately because it can't be built anymore, due to > Ubuntu 18.10 being EOL. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-15659) Better support of Python 3 for cqlsh
[ https://issues.apache.org/jira/browse/CASSANDRA-15659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17077009#comment-17077009 ] Eduard Tudenhoefner edited comment on CASSANDRA-15659 at 4/7/20, 7:42 AM: -- ||Pull Request||Tests||Docker Image|| |[PR#505|https://github.com/apache/cassandra/pull/505]|[CircleCI|https://app.circleci.com/pipelines/github/nastra/cassandra/19/workflows/dc0a8771-321f-40bf-a5e8-6e05b20bbca1]|[PR|https://github.com/apache/cassandra-builds/pull/17] Note that the test failures when testing with Python 3.8 are due to CASSANDRA-15573. was (Author: eduard.tudenhoefner): ||Pull Request||Tests|| |[PR#505|https://github.com/apache/cassandra/pull/505]|[CircleCI|https://app.circleci.com/pipelines/github/nastra/cassandra/19/workflows/dc0a8771-321f-40bf-a5e8-6e05b20bbca1]| Note that the test failures when testing with Python 3.8 are due to CASSANDRA-15573. > Better support of Python 3 for cqlsh > > > Key: CASSANDRA-15659 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15659 > Project: Cassandra > Issue Type: Task > Components: Tool/cqlsh >Reporter: Stefan Miklosovic >Assignee: Eduard Tudenhoefner >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Time Spent: 40m > Remaining Estimate: 0h > > h2. From mailing list: > [https://lists.apache.org/thread.html/r377099b632c62b641e4feef5b738084fc5369b0c7157fae867853597%40%3Cdev.cassandra.apache.org%3E] > > As of today (24/3/2020) and current trunk, there is Python 3.6 supported (1) > but there is not any 3.6 version ootb in Debian for example. E.g. Buster has > Python 3.7 and other (recent) releases have version 2.7. This means that if > one wants to use Python 3 in Debian, he has to use 3.6 but it is not in the > repository so he has to download / compile / install it on his own. > There should be some sane Python 3 version supported which is as well present > in Debian repository (or requirement to run with 3.6 should be relaxed) . > (1) > [https://github.com/apache/cassandra/blob/bf9a1d487b9ba469e8d740cf7d1cd419535a7e79/bin/cqlsh#L57-L65] > h2. Summary of work that was done: > I relaxed the requirement of *cqlsh* only working with Python 2.7 & 3.6 by > allowing Python 3.6+. > Note that I left the constraint for Python 3.6 being the minimum Python3 > version. > As [~ptbannister] pointed out, we could remove the Python 3.6 min version > once we remove Python 2.7 support, as otherwise testing with lots of > different Python versions will get costly. > 2 Dockerfiles were added in *pylib* for minimal local testing of *cqlsh* > starting up with Python 3.7 & 3.8 and that both revealed > CASSANDRA-15572 and CASSANDRA-15573. > CASSANDRA-15572 was fixed here as it was a one-liner. And I'm going to > tackle CASSANDRA-15573 later. > Python 3.8 testing was added to the CircleCI config so that we can actually > see what else breaks with newer Python versions. > A new Docker images with Ubuntu 19.10 was required for testing > ([https://github.com/apache/cassandra-builds/pull/17]). This docker image > sets up Python 2.7/3.6/3.7/3.8 with their respective virtual environments, > which are then being used by the CircleCI yaml. > The image *spod/cassandra-testing-ubuntu1810-java11-w-dependencies:20190306* > couldn't be updated unfortunately because it can't be built anymore, due to > Ubuntu 18.10 being EOL. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15659) Better support of Python 3 for cqlsh
[ https://issues.apache.org/jira/browse/CASSANDRA-15659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-15659: Test and Documentation Plan: https://github.com/apache/cassandra/pull/505 Status: Patch Available (was: In Progress) ||Pull Request||Tests|| |[PR#505|https://github.com/apache/cassandra/pull/505]|[CircleCI|https://app.circleci.com/pipelines/github/nastra/cassandra/19/workflows/dc0a8771-321f-40bf-a5e8-6e05b20bbca1]| Note that the test failures when testing with Python 3.8 are due to CASSANDRA-15573. > Better support of Python 3 for cqlsh > > > Key: CASSANDRA-15659 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15659 > Project: Cassandra > Issue Type: Task > Components: Tool/cqlsh >Reporter: Stefan Miklosovic >Assignee: Eduard Tudenhoefner >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Time Spent: 40m > Remaining Estimate: 0h > > h2. From mailing list: > [https://lists.apache.org/thread.html/r377099b632c62b641e4feef5b738084fc5369b0c7157fae867853597%40%3Cdev.cassandra.apache.org%3E] > > As of today (24/3/2020) and current trunk, there is Python 3.6 supported (1) > but there is not any 3.6 version ootb in Debian for example. E.g. Buster has > Python 3.7 and other (recent) releases have version 2.7. This means that if > one wants to use Python 3 in Debian, he has to use 3.6 but it is not in the > repository so he has to download / compile / install it on his own. > There should be some sane Python 3 version supported which is as well present > in Debian repository (or requirement to run with 3.6 should be relaxed) . > (1) > [https://github.com/apache/cassandra/blob/bf9a1d487b9ba469e8d740cf7d1cd419535a7e79/bin/cqlsh#L57-L65] > h2. Summary of work that was done: > I relaxed the requirement of *cqlsh* only working with Python 2.7 & 3.6 by > allowing Python 3.6+. > Note that I left the constraint for Python 3.6 being the minimum Python3 > version. > As [~ptbannister] pointed out, we could remove the Python 3.6 min version > once we remove Python 2.7 support, as otherwise testing with lots of > different Python versions will get costly. > 2 Dockerfiles were added in *pylib* for minimal local testing of *cqlsh* > starting up with Python 3.7 & 3.8 and that both revealed > CASSANDRA-15572 and CASSANDRA-15573. > CASSANDRA-15572 was fixed here as it was a one-liner. And I'm going to > tackle CASSANDRA-15573 later. > Python 3.8 testing was added to the CircleCI config so that we can actually > see what else breaks with newer Python versions. > A new Docker images with Ubuntu 19.10 was required for testing > ([https://github.com/apache/cassandra-builds/pull/17]). This docker image > sets up Python 2.7/3.6/3.7/3.8 with their respective virtual environments, > which are then being used by the CircleCI yaml. > The image *spod/cassandra-testing-ubuntu1810-java11-w-dependencies:20190306* > couldn't be updated unfortunately because it can't be built anymore, due to > Ubuntu 18.10 being EOL. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15573) Python 3.8 fails to execute cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-15573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076424#comment-17076424
]
Eduard Tudenhoefner commented on CASSANDRA-15573:
-
The issue itself can also be manually verified with the below steps, which are
from [the pylib
readme|https://github.com/nastra/cassandra/blob/e840b458dd8fda021871ceee1efb5187ad94aad3/pylib/README.asc]
and require CASSANDRA-15659)
{code}
docker build . --file Dockerfile.ubuntu.py38 -t ubuntu-lts-py3
docker run -v $CASSANDRA_DIR:/code -it ubuntu-lts-py3:latest /code/bin/cqlsh
host.docker.internal
{code}
> Python 3.8 fails to execute cqlsh
> -
>
> Key: CASSANDRA-15573
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15573
> Project: Cassandra
> Issue Type: Sub-task
> Components: Tool/cqlsh
>Reporter: Yuki Morishita
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Python 3.8 renamed sre_parse.Pattern to sre_parse.State (see
> https://bugs.python.org/issue34681 and corresponding pull request
> https://github.com/python/cpython/pull/9310)
> So when executing cqlsh with Python 3.8, it throws error:
> {code}
> Traceback (most recent call last):
> File ".\bin\cqlsh.py", line 175, in
> from cqlshlib import cql3handling, cqlhandling, pylexotron, sslhandling,
> cqlshhandling
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cql3handling.py", line 19,
> in
> from cqlshlib.cqlhandling import CqlParsingRuleSet, Hint
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cqlhandling.py", line 23,
> in
> from cqlshlib import pylexotron, util
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 342,
> in
> class ParsingRuleSet:
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 343,
> in ParsingRuleSet
> RuleSpecScanner = SaferScanner([
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\saferscanner.py", line 74,
> in __init__
> s = re.sre_parse.Pattern()
> AttributeError: module 'sre_parse' has no attribute 'Pattern'
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15573) Python 3.8 fails to execute cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-15573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15573:
Change Category: Operability
Complexity: Low Hanging Fruit
Fix Version/s: 4.0-alpha
Status: Open (was: Triage Needed)
> Python 3.8 fails to execute cqlsh
> -
>
> Key: CASSANDRA-15573
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15573
> Project: Cassandra
> Issue Type: Sub-task
> Components: Tool/cqlsh
>Reporter: Yuki Morishita
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Python 3.8 renamed sre_parse.Pattern to sre_parse.State (see
> https://bugs.python.org/issue34681 and corresponding pull request
> https://github.com/python/cpython/pull/9310)
> So when executing cqlsh with Python 3.8, it throws error:
> {code}
> Traceback (most recent call last):
> File ".\bin\cqlsh.py", line 175, in
> from cqlshlib import cql3handling, cqlhandling, pylexotron, sslhandling,
> cqlshhandling
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cql3handling.py", line 19,
> in
> from cqlshlib.cqlhandling import CqlParsingRuleSet, Hint
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cqlhandling.py", line 23,
> in
> from cqlshlib import pylexotron, util
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 342,
> in
> class ParsingRuleSet:
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 343,
> in ParsingRuleSet
> RuleSpecScanner = SaferScanner([
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\saferscanner.py", line 74,
> in __init__
> s = re.sre_parse.Pattern()
> AttributeError: module 'sre_parse' has no attribute 'Pattern'
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15573) Python 3.8 fails to execute cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-15573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076421#comment-17076421
]
Eduard Tudenhoefner commented on CASSANDRA-15573:
-
I added a Python3.8 compatible SaferScanner in
https://github.com/apache/cassandra/pull/518. Note that the PR currently
contains 2 commits from CASSANDRA-15659 because those are required for testing
things with newer Python versions.
> Python 3.8 fails to execute cqlsh
> -
>
> Key: CASSANDRA-15573
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15573
> Project: Cassandra
> Issue Type: Sub-task
> Components: Tool/cqlsh
>Reporter: Yuki Morishita
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Python 3.8 renamed sre_parse.Pattern to sre_parse.State (see
> https://bugs.python.org/issue34681 and corresponding pull request
> https://github.com/python/cpython/pull/9310)
> So when executing cqlsh with Python 3.8, it throws error:
> {code}
> Traceback (most recent call last):
> File ".\bin\cqlsh.py", line 175, in
> from cqlshlib import cql3handling, cqlhandling, pylexotron, sslhandling,
> cqlshhandling
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cql3handling.py", line 19,
> in
> from cqlshlib.cqlhandling import CqlParsingRuleSet, Hint
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\cqlhandling.py", line 23,
> in
> from cqlshlib import pylexotron, util
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 342,
> in
> class ParsingRuleSet:
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\pylexotron.py", line 343,
> in ParsingRuleSet
> RuleSpecScanner = SaferScanner([
> File "C:\Users\Yuki
> Morishita\Projects\cassandra\bin\..\pylib\cqlshlib\saferscanner.py", line 74,
> in __init__
> s = re.sre_parse.Pattern()
> AttributeError: module 'sre_parse' has no attribute 'Pattern'
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15659) Better support of Python 3 for cqlsh
[ https://issues.apache.org/jira/browse/CASSANDRA-15659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-15659: Description: h2. From mailing list: [https://lists.apache.org/thread.html/r377099b632c62b641e4feef5b738084fc5369b0c7157fae867853597%40%3Cdev.cassandra.apache.org%3E] As of today (24/3/2020) and current trunk, there is Python 3.6 supported (1) but there is not any 3.6 version ootb in Debian for example. E.g. Buster has Python 3.7 and other (recent) releases have version 2.7. This means that if one wants to use Python 3 in Debian, he has to use 3.6 but it is not in the repository so he has to download / compile / install it on his own. There should be some sane Python 3 version supported which is as well present in Debian repository (or requirement to run with 3.6 should be relaxed) . (1) [https://github.com/apache/cassandra/blob/bf9a1d487b9ba469e8d740cf7d1cd419535a7e79/bin/cqlsh#L57-L65] h2. Summary of work that was done: I relaxed the requirement of *cqlsh* only working with Python 2.7 & 3.6 by allowing Python 3.6+. Note that I left the constraint for Python 3.6 being the minimum Python3 version. As [~ptbannister] pointed out, we could remove the Python 3.6 min version once we remove Python 2.7 support, as otherwise testing with lots of different Python versions will get costly. 2 Dockerfiles were added in *pylib* for minimal local testing of *cqlsh* starting up with Python 3.7 & 3.8 and that both revealed CASSANDRA-15572 and CASSANDRA-15573. CASSANDRA-15572 was fixed here as it was a one-liner. And I'm going to tackle CASSANDRA-15573 later. Python 3.8 testing was added to the CircleCI config so that we can actually see what else breaks with newer Python versions. A new Docker images with Ubuntu 19.10 was required (https://github.com/apache/cassandra-builds/pull/17). This docker image sets up Python 2.7/3.6/3.7/3.8 with their respective virtual environments, which are then being used by the CircleCI yaml. The image *spod/cassandra-testing-ubuntu1810-java11-w-dependencies:20190306* couldn't be updated unfortunately because it can't be built anymore, due to Ubuntu 18.10 being EOL. was: >From mailing list: [https://lists.apache.org/thread.html/r377099b632c62b641e4feef5b738084fc5369b0c7157fae867853597%40%3Cdev.cassandra.apache.org%3E] As of today (24/3/2020) and current trunk, there is Python 3.6 supported (1) but there is not any 3.6 version ootb in Debian for example. E.g. Buster has Python 3.7 and other (recent) releases have version 2.7. This means that if one wants to use Python 3 in Debian, he has to use 3.6 but it is not in the repository so he has to download / compile / install it on his own. There should be some sane Python 3 version supported which is as well present in Debian repository (or requirement to run with 3.6 should be relaxed) . (1) [https://github.com/apache/cassandra/blob/bf9a1d487b9ba469e8d740cf7d1cd419535a7e79/bin/cqlsh#L57-L65] > Better support of Python 3 for cqlsh > > > Key: CASSANDRA-15659 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15659 > Project: Cassandra > Issue Type: Task > Components: Tool/cqlsh >Reporter: Stefan Miklosovic >Assignee: Eduard Tudenhoefner >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Time Spent: 40m > Remaining Estimate: 0h > > h2. From mailing list: > [https://lists.apache.org/thread.html/r377099b632c62b641e4feef5b738084fc5369b0c7157fae867853597%40%3Cdev.cassandra.apache.org%3E] > > As of today (24/3/2020) and current trunk, there is Python 3.6 supported (1) > but there is not any 3.6 version ootb in Debian for example. E.g. Buster has > Python 3.7 and other (recent) releases have version 2.7. This means that if > one wants to use Python 3 in Debian, he has to use 3.6 but it is not in the > repository so he has to download / compile / install it on his own. > There should be some sane Python 3 version supported which is as well present > in Debian repository (or requirement to run with 3.6 should be relaxed) . > (1) > [https://github.com/apache/cassandra/blob/bf9a1d487b9ba469e8d740cf7d1cd419535a7e79/bin/cqlsh#L57-L65] > h2. Summary of work that was done: > I relaxed the requirement of *cqlsh* only working with Python 2.7 & 3.6 by > allowing Python 3.6+. > Note that I left the constraint for Python 3.6 being the minimum Python3 > version. > As [~ptbannister] pointed out, we could remove the Python 3.6 min version > once we remove Python 2.7 support, as otherwise testing with lots of > different Python versions will get costly. > 2 Dockerfiles were added in *pylib* for minimal local testing of *cqlsh* > starting up with Python 3.7 & 3.8 and that both revealed
[jira] [Updated] (CASSANDRA-15659) Better support of Python 3 for cqlsh
[ https://issues.apache.org/jira/browse/CASSANDRA-15659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-15659: Description: h2. From mailing list: [https://lists.apache.org/thread.html/r377099b632c62b641e4feef5b738084fc5369b0c7157fae867853597%40%3Cdev.cassandra.apache.org%3E] As of today (24/3/2020) and current trunk, there is Python 3.6 supported (1) but there is not any 3.6 version ootb in Debian for example. E.g. Buster has Python 3.7 and other (recent) releases have version 2.7. This means that if one wants to use Python 3 in Debian, he has to use 3.6 but it is not in the repository so he has to download / compile / install it on his own. There should be some sane Python 3 version supported which is as well present in Debian repository (or requirement to run with 3.6 should be relaxed) . (1) [https://github.com/apache/cassandra/blob/bf9a1d487b9ba469e8d740cf7d1cd419535a7e79/bin/cqlsh#L57-L65] h2. Summary of work that was done: I relaxed the requirement of *cqlsh* only working with Python 2.7 & 3.6 by allowing Python 3.6+. Note that I left the constraint for Python 3.6 being the minimum Python3 version. As [~ptbannister] pointed out, we could remove the Python 3.6 min version once we remove Python 2.7 support, as otherwise testing with lots of different Python versions will get costly. 2 Dockerfiles were added in *pylib* for minimal local testing of *cqlsh* starting up with Python 3.7 & 3.8 and that both revealed CASSANDRA-15572 and CASSANDRA-15573. CASSANDRA-15572 was fixed here as it was a one-liner. And I'm going to tackle CASSANDRA-15573 later. Python 3.8 testing was added to the CircleCI config so that we can actually see what else breaks with newer Python versions. A new Docker images with Ubuntu 19.10 was required for testing ([https://github.com/apache/cassandra-builds/pull/17]). This docker image sets up Python 2.7/3.6/3.7/3.8 with their respective virtual environments, which are then being used by the CircleCI yaml. The image *spod/cassandra-testing-ubuntu1810-java11-w-dependencies:20190306* couldn't be updated unfortunately because it can't be built anymore, due to Ubuntu 18.10 being EOL. was: h2. From mailing list: [https://lists.apache.org/thread.html/r377099b632c62b641e4feef5b738084fc5369b0c7157fae867853597%40%3Cdev.cassandra.apache.org%3E] As of today (24/3/2020) and current trunk, there is Python 3.6 supported (1) but there is not any 3.6 version ootb in Debian for example. E.g. Buster has Python 3.7 and other (recent) releases have version 2.7. This means that if one wants to use Python 3 in Debian, he has to use 3.6 but it is not in the repository so he has to download / compile / install it on his own. There should be some sane Python 3 version supported which is as well present in Debian repository (or requirement to run with 3.6 should be relaxed) . (1) [https://github.com/apache/cassandra/blob/bf9a1d487b9ba469e8d740cf7d1cd419535a7e79/bin/cqlsh#L57-L65] h2. Summary of work that was done: I relaxed the requirement of *cqlsh* only working with Python 2.7 & 3.6 by allowing Python 3.6+. Note that I left the constraint for Python 3.6 being the minimum Python3 version. As [~ptbannister] pointed out, we could remove the Python 3.6 min version once we remove Python 2.7 support, as otherwise testing with lots of different Python versions will get costly. 2 Dockerfiles were added in *pylib* for minimal local testing of *cqlsh* starting up with Python 3.7 & 3.8 and that both revealed CASSANDRA-15572 and CASSANDRA-15573. CASSANDRA-15572 was fixed here as it was a one-liner. And I'm going to tackle CASSANDRA-15573 later. Python 3.8 testing was added to the CircleCI config so that we can actually see what else breaks with newer Python versions. A new Docker images with Ubuntu 19.10 was required (https://github.com/apache/cassandra-builds/pull/17). This docker image sets up Python 2.7/3.6/3.7/3.8 with their respective virtual environments, which are then being used by the CircleCI yaml. The image *spod/cassandra-testing-ubuntu1810-java11-w-dependencies:20190306* couldn't be updated unfortunately because it can't be built anymore, due to Ubuntu 18.10 being EOL. > Better support of Python 3 for cqlsh > > > Key: CASSANDRA-15659 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15659 > Project: Cassandra > Issue Type: Task > Components: Tool/cqlsh >Reporter: Stefan Miklosovic >Assignee: Eduard Tudenhoefner >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Time Spent: 40m > Remaining Estimate: 0h > > h2. From mailing list: >
[jira] [Updated] (CASSANDRA-15695) Fix NoSuchMethodError: 'org.apache.cassandra.distributed.api.NodeToolResult$Asserts
[
https://issues.apache.org/jira/browse/CASSANDRA-15695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15695:
Resolution: Duplicate
Status: Resolved (was: Open)
> Fix NoSuchMethodError:
> 'org.apache.cassandra.distributed.api.NodeToolResult$Asserts
>
>
> Key: CASSANDRA-15695
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15695
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Eduard Tudenhoefner
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Fix For: 4.0-alpha
>
>
> It seems that there was a regression introduced with CASSANDRA-15650 as the
> first failures of that kind started to happen
> [here.|https://ci-cassandra.apache.org/view/branches/job/Cassandra-trunk/30/#showFailuresLink]
> {code}
> [junit-timeout] Testcase:
> prepareRPCTimeout[DATACENTER_AWARE/true](org.apache.cassandra.distributed.test.PreviewRepairCoordinatorTimeoutTest):
> Caused an ERROR
> [junit-timeout] 'org.apache.cassandra.distributed.api.NodeToolResult$Asserts
> org.apache.cassandra.distributed.api.NodeToolResult$Asserts.errorContains(java.lang.String[])'
> [junit-timeout] java.lang.NoSuchMethodError:
> 'org.apache.cassandra.distributed.api.NodeToolResult$Asserts
> org.apache.cassandra.distributed.api.NodeToolResult$Asserts.errorContains(java.lang.String[])'
> [junit-timeout] at
> org.apache.cassandra.distributed.test.RepairCoordinatorTimeout.lambda$prepareRPCTimeout$0(RepairCoordinatorTimeout.java:45)
> [junit-timeout] at
> org.apache.cassandra.utils.AssertUtil.lambda$assertTimeoutPreemptively$0(AssertUtil.java:39)
> [junit-timeout] at
> org.apache.cassandra.utils.AssertUtil.lambda$assertTimeoutPreemptively$1(AssertUtil.java:67)
> [junit-timeout] at
> java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> [junit-timeout] at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> [junit-timeout] at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> [junit-timeout] at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> [junit-timeout] at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15695) Fix NoSuchMethodError: 'org.apache.cassandra.distributed.api.NodeToolResult$Asserts
[
https://issues.apache.org/jira/browse/CASSANDRA-15695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15695:
Bug Category: Parent values: Code(13163)
Complexity: Normal
Discovered By: Unit Test
Severity: Normal
Status: Open (was: Triage Needed)
> Fix NoSuchMethodError:
> 'org.apache.cassandra.distributed.api.NodeToolResult$Asserts
>
>
> Key: CASSANDRA-15695
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15695
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Eduard Tudenhoefner
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Fix For: 4.0-alpha
>
>
> It seems that there was a regression introduced with CASSANDRA-15650 as the
> first failures of that kind started to happen
> [here.|https://ci-cassandra.apache.org/view/branches/job/Cassandra-trunk/30/#showFailuresLink]
> {code}
> [junit-timeout] Testcase:
> prepareRPCTimeout[DATACENTER_AWARE/true](org.apache.cassandra.distributed.test.PreviewRepairCoordinatorTimeoutTest):
> Caused an ERROR
> [junit-timeout] 'org.apache.cassandra.distributed.api.NodeToolResult$Asserts
> org.apache.cassandra.distributed.api.NodeToolResult$Asserts.errorContains(java.lang.String[])'
> [junit-timeout] java.lang.NoSuchMethodError:
> 'org.apache.cassandra.distributed.api.NodeToolResult$Asserts
> org.apache.cassandra.distributed.api.NodeToolResult$Asserts.errorContains(java.lang.String[])'
> [junit-timeout] at
> org.apache.cassandra.distributed.test.RepairCoordinatorTimeout.lambda$prepareRPCTimeout$0(RepairCoordinatorTimeout.java:45)
> [junit-timeout] at
> org.apache.cassandra.utils.AssertUtil.lambda$assertTimeoutPreemptively$0(AssertUtil.java:39)
> [junit-timeout] at
> org.apache.cassandra.utils.AssertUtil.lambda$assertTimeoutPreemptively$1(AssertUtil.java:67)
> [junit-timeout] at
> java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> [junit-timeout] at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> [junit-timeout] at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> [junit-timeout] at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> [junit-timeout] at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15695) Fix NoSuchMethodError: 'org.apache.cassandra.distributed.api.NodeToolResult$Asserts
[
https://issues.apache.org/jira/browse/CASSANDRA-15695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15695:
Since Version: 4.0-alpha
> Fix NoSuchMethodError:
> 'org.apache.cassandra.distributed.api.NodeToolResult$Asserts
>
>
> Key: CASSANDRA-15695
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15695
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Eduard Tudenhoefner
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Fix For: 4.0-alpha
>
>
> It seems that there was a regression introduced with CASSANDRA-15650 as the
> first failures of that kind started to happen
> [here.|https://ci-cassandra.apache.org/view/branches/job/Cassandra-trunk/30/#showFailuresLink]
> {code}
> [junit-timeout] Testcase:
> prepareRPCTimeout[DATACENTER_AWARE/true](org.apache.cassandra.distributed.test.PreviewRepairCoordinatorTimeoutTest):
> Caused an ERROR
> [junit-timeout] 'org.apache.cassandra.distributed.api.NodeToolResult$Asserts
> org.apache.cassandra.distributed.api.NodeToolResult$Asserts.errorContains(java.lang.String[])'
> [junit-timeout] java.lang.NoSuchMethodError:
> 'org.apache.cassandra.distributed.api.NodeToolResult$Asserts
> org.apache.cassandra.distributed.api.NodeToolResult$Asserts.errorContains(java.lang.String[])'
> [junit-timeout] at
> org.apache.cassandra.distributed.test.RepairCoordinatorTimeout.lambda$prepareRPCTimeout$0(RepairCoordinatorTimeout.java:45)
> [junit-timeout] at
> org.apache.cassandra.utils.AssertUtil.lambda$assertTimeoutPreemptively$0(AssertUtil.java:39)
> [junit-timeout] at
> org.apache.cassandra.utils.AssertUtil.lambda$assertTimeoutPreemptively$1(AssertUtil.java:67)
> [junit-timeout] at
> java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> [junit-timeout] at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> [junit-timeout] at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> [junit-timeout] at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> [junit-timeout] at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15695) Fix NoSuchMethodError: 'org.apache.cassandra.distributed.api.NodeToolResult$Asserts
[
https://issues.apache.org/jira/browse/CASSANDRA-15695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner updated CASSANDRA-15695:
Fix Version/s: 4.0-alpha
> Fix NoSuchMethodError:
> 'org.apache.cassandra.distributed.api.NodeToolResult$Asserts
>
>
> Key: CASSANDRA-15695
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15695
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Eduard Tudenhoefner
>Assignee: Eduard Tudenhoefner
>Priority: Normal
> Fix For: 4.0-alpha
>
>
> It seems that there was a regression introduced with CASSANDRA-15650 as the
> first failures of that kind started to happen
> [here.|https://ci-cassandra.apache.org/view/branches/job/Cassandra-trunk/30/#showFailuresLink]
> {code}
> [junit-timeout] Testcase:
> prepareRPCTimeout[DATACENTER_AWARE/true](org.apache.cassandra.distributed.test.PreviewRepairCoordinatorTimeoutTest):
> Caused an ERROR
> [junit-timeout] 'org.apache.cassandra.distributed.api.NodeToolResult$Asserts
> org.apache.cassandra.distributed.api.NodeToolResult$Asserts.errorContains(java.lang.String[])'
> [junit-timeout] java.lang.NoSuchMethodError:
> 'org.apache.cassandra.distributed.api.NodeToolResult$Asserts
> org.apache.cassandra.distributed.api.NodeToolResult$Asserts.errorContains(java.lang.String[])'
> [junit-timeout] at
> org.apache.cassandra.distributed.test.RepairCoordinatorTimeout.lambda$prepareRPCTimeout$0(RepairCoordinatorTimeout.java:45)
> [junit-timeout] at
> org.apache.cassandra.utils.AssertUtil.lambda$assertTimeoutPreemptively$0(AssertUtil.java:39)
> [junit-timeout] at
> org.apache.cassandra.utils.AssertUtil.lambda$assertTimeoutPreemptively$1(AssertUtil.java:67)
> [junit-timeout] at
> java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> [junit-timeout] at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> [junit-timeout] at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> [junit-timeout] at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> [junit-timeout] at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-15695) Fix NoSuchMethodError: 'org.apache.cassandra.distributed.api.NodeToolResult$Asserts
[
https://issues.apache.org/jira/browse/CASSANDRA-15695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Tudenhoefner reassigned CASSANDRA-15695:
---
Assignee: Eduard Tudenhoefner
> Fix NoSuchMethodError:
> 'org.apache.cassandra.distributed.api.NodeToolResult$Asserts
>
>
> Key: CASSANDRA-15695
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15695
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Eduard Tudenhoefner
>Assignee: Eduard Tudenhoefner
>Priority: Normal
>
> It seems that there was a regression introduced with CASSANDRA-15650 as the
> first failures of that kind started to happen
> [here.|https://ci-cassandra.apache.org/view/branches/job/Cassandra-trunk/30/#showFailuresLink]
> {code}
> [junit-timeout] Testcase:
> prepareRPCTimeout[DATACENTER_AWARE/true](org.apache.cassandra.distributed.test.PreviewRepairCoordinatorTimeoutTest):
> Caused an ERROR
> [junit-timeout] 'org.apache.cassandra.distributed.api.NodeToolResult$Asserts
> org.apache.cassandra.distributed.api.NodeToolResult$Asserts.errorContains(java.lang.String[])'
> [junit-timeout] java.lang.NoSuchMethodError:
> 'org.apache.cassandra.distributed.api.NodeToolResult$Asserts
> org.apache.cassandra.distributed.api.NodeToolResult$Asserts.errorContains(java.lang.String[])'
> [junit-timeout] at
> org.apache.cassandra.distributed.test.RepairCoordinatorTimeout.lambda$prepareRPCTimeout$0(RepairCoordinatorTimeout.java:45)
> [junit-timeout] at
> org.apache.cassandra.utils.AssertUtil.lambda$assertTimeoutPreemptively$0(AssertUtil.java:39)
> [junit-timeout] at
> org.apache.cassandra.utils.AssertUtil.lambda$assertTimeoutPreemptively$1(AssertUtil.java:67)
> [junit-timeout] at
> java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> [junit-timeout] at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> [junit-timeout] at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> [junit-timeout] at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> [junit-timeout] at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15695) Fix NoSuchMethodError: 'org.apache.cassandra.distributed.api.NodeToolResult$Asserts
Eduard Tudenhoefner created CASSANDRA-15695:
---
Summary: Fix NoSuchMethodError:
'org.apache.cassandra.distributed.api.NodeToolResult$Asserts
Key: CASSANDRA-15695
URL: https://issues.apache.org/jira/browse/CASSANDRA-15695
Project: Cassandra
Issue Type: Bug
Components: Test/unit
Reporter: Eduard Tudenhoefner
It seems that there was a regression introduced with CASSANDRA-15650 as the
first failures of that kind started to happen
[here.|https://ci-cassandra.apache.org/view/branches/job/Cassandra-trunk/30/#showFailuresLink]
{code}
[junit-timeout] Testcase:
prepareRPCTimeout[DATACENTER_AWARE/true](org.apache.cassandra.distributed.test.PreviewRepairCoordinatorTimeoutTest):
Caused an ERROR
[junit-timeout] 'org.apache.cassandra.distributed.api.NodeToolResult$Asserts
org.apache.cassandra.distributed.api.NodeToolResult$Asserts.errorContains(java.lang.String[])'
[junit-timeout] java.lang.NoSuchMethodError:
'org.apache.cassandra.distributed.api.NodeToolResult$Asserts
org.apache.cassandra.distributed.api.NodeToolResult$Asserts.errorContains(java.lang.String[])'
[junit-timeout] at
org.apache.cassandra.distributed.test.RepairCoordinatorTimeout.lambda$prepareRPCTimeout$0(RepairCoordinatorTimeout.java:45)
[junit-timeout] at
org.apache.cassandra.utils.AssertUtil.lambda$assertTimeoutPreemptively$0(AssertUtil.java:39)
[junit-timeout] at
org.apache.cassandra.utils.AssertUtil.lambda$assertTimeoutPreemptively$1(AssertUtil.java:67)
[junit-timeout] at
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
[junit-timeout] at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
[junit-timeout] at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
[junit-timeout] at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
[junit-timeout] at java.base/java.lang.Thread.run(Thread.java:834)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-15659) Better support of Python 3 for cqlsh
[ https://issues.apache.org/jira/browse/CASSANDRA-15659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17073545#comment-17073545 ] Eduard Tudenhoefner edited comment on CASSANDRA-15659 at 4/2/20, 10:54 AM: --- I relaxed the requirement of *cqlsh* only working with Python 2.7 & 3.6 by allowing Python 3.6+. Note that I left the constraint for Python 3.6 being the minimum Python3 version. As [~ptbannister] pointed out, we could remove the Python 3.6 min version once we remove Python 2.7 support, as otherwise testing with lots of different Python versions will get costly. I also added 2 Dockerfiles in *pylib* for minimal local testing of *cqlsh* starting up with Python 3.7 & 3.8 and that both revealed CASSANDRA-15572 and CASSANDRA-15573. I fixed CASSANDRA-15572 in my branch as it was a one-liner. And I'm going to tackle CASSANDRA-15573 later. I also added Python 3.8 testing to the CircleCI config so that we can actually see what else breaks with newer Python versions. Update: I tried running things with my CircleCI config changes and Python 3.8 in https://app.circleci.com/pipelines/github/nastra/cassandra/jobs/106 but it seems the Docker image we're using has only Python 2.7&3.6 installed [~spod] would we need new Docker images that have Python 3.8 installed in order to be able to test with Python 3.6 + 3.8? What's the process for that? Any help/hint would be appreciated. was (Author: eduard.tudenhoefner): I relaxed the requirement of *cqlsh* only working with Python 2.7 & 3.6 by allowing Python 3.6+. Note that I left the constraint for Python 3.6 being the minimum Python3 version. As [~ptbannister] pointed out, we could remove the Python 3.6 min version once we remove Python 2.7 support, as otherwise testing with lots of different Python versions will get costly. I also added 2 Dockerfiles in *pylib* for minimal local testing of *cqlsh* starting up with Python 3.7 & 3.8 and that both revealed CASSANDRA-15572 and CASSANDRA-15573. I fixed CASSANDRA-15572 in my branch as it was a one-liner. And I'm going to tackle CASSANDRA-15573 later. I also added Python 3.8 testing to the CircleCI config so that we can actually see what else breaks with newer Python versions. > Better support of Python 3 for cqlsh > > > Key: CASSANDRA-15659 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15659 > Project: Cassandra > Issue Type: Task > Components: Tool/cqlsh >Reporter: Stefan Miklosovic >Assignee: Eduard Tudenhoefner >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Time Spent: 40m > Remaining Estimate: 0h > > From mailing list: > [https://lists.apache.org/thread.html/r377099b632c62b641e4feef5b738084fc5369b0c7157fae867853597%40%3Cdev.cassandra.apache.org%3E] > > As of today (24/3/2020) and current trunk, there is Python 3.6 supported (1) > but there is not any 3.6 version ootb in Debian for example. E.g. Buster has > Python 3.7 and other (recent) releases have version 2.7. This means that if > one wants to use Python 3 in Debian, he has to use 3.6 but it is not in the > repository so he has to download / compile / install it on his own. > There should be some sane Python 3 version supported which is as well present > in Debian repository (or requirement to run with 3.6 should be relaxed) . > (1) > [https://github.com/apache/cassandra/blob/bf9a1d487b9ba469e8d740cf7d1cd419535a7e79/bin/cqlsh#L57-L65] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15659) Better support of Python 3 for cqlsh
[ https://issues.apache.org/jira/browse/CASSANDRA-15659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17073545#comment-17073545 ] Eduard Tudenhoefner commented on CASSANDRA-15659: - I relaxed the requirement of *cqlsh* only working with Python 2.7 & 3.6 by allowing Python 3.6+. Note that I left the constraint for Python 3.6 being the minimum Python3 version. As [~ptbannister] pointed out, we could remove the Python 3.6 min version once we remove Python 2.7 support, as otherwise testing with lots of different Python versions will get costly. I also added 2 Dockerfiles in *pylib* for minimal local testing of *cqlsh* starting up with Python 3.7 & 3.8 and that both revealed CASSANDRA-15572 and CASSANDRA-15573. I fixed CASSANDRA-15572 in my branch as it was a one-liner. And I'm going to tackle CASSANDRA-15573 later. I also added Python 3.8 testing to the CircleCI config so that we can actually see what else breaks with newer Python versions. > Better support of Python 3 for cqlsh > > > Key: CASSANDRA-15659 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15659 > Project: Cassandra > Issue Type: Task > Components: Tool/cqlsh >Reporter: Stefan Miklosovic >Assignee: Eduard Tudenhoefner >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Time Spent: 40m > Remaining Estimate: 0h > > From mailing list: > [https://lists.apache.org/thread.html/r377099b632c62b641e4feef5b738084fc5369b0c7157fae867853597%40%3Cdev.cassandra.apache.org%3E] > > As of today (24/3/2020) and current trunk, there is Python 3.6 supported (1) > but there is not any 3.6 version ootb in Debian for example. E.g. Buster has > Python 3.7 and other (recent) releases have version 2.7. This means that if > one wants to use Python 3 in Debian, he has to use 3.6 but it is not in the > repository so he has to download / compile / install it on his own. > There should be some sane Python 3 version supported which is as well present > in Debian repository (or requirement to run with 3.6 should be relaxed) . > (1) > [https://github.com/apache/cassandra/blob/bf9a1d487b9ba469e8d740cf7d1cd419535a7e79/bin/cqlsh#L57-L65] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
