[ 
https://issues.apache.org/jira/browse/CASSANDRA-19105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17894401#comment-17894401
 ] 

Brad Schoening edited comment on CASSANDRA-19105 at 11/1/24 2:46 AM:
---------------------------------------------------------------------

[~gautamg] you need to install wcwidth

{{pip install wcwidth}}

 

I ran the following:

% pycodestyle --ignore E501,E402,E731,W503 *.py         

cqlshmain.py:1547:1: W293 blank line contains whitespace

tracing.py:44:13: E117 over-indented

tracing.py:60:5: E303 too many blank lines (3)

tracing.py:73:1: E303 too many blank lines (3)


was (Author: bschoeni):
[~gautamg] you need to install wcwidth

{{pip install wcwidth}}

> Fix CQLSH Capture to save query results only and not trace details when 
> Tracing is on
> -------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-19105
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19105
>             Project: Cassandra
>          Issue Type: Bug
>          Components: CQL/Interpreter
>            Reporter: Brad Schoening
>            Assignee: Gautam G
>            Priority: Normal
>         Attachments: test_results.txt, trunk_test_results.txt
>
>
> When using *Tracing* in CQLSH, it's sometimes helpful to use *Capture* to 
> avoid paging through output when you want to see the trace results.  However, 
> the trace results are also incorrectly captured to the output file.
> According to *Help Capture* (below), only the query result should be saved. 
> The correct behavior should display the trace results and only capture the 
> query results.
>         {_}Help capture message{_}:  Only query result output is captured. 
> Errors and output from cqlsh-only commands will still be shown in the cqlsh 
> session.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to