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

Brad Schoening edited comment on CASSANDRA-19105 at 10/1/24 9:07 PM:
---------------------------------------------------------------------

[~gautamg] ok, can you link the PR URL as an attachment and click submit patch. 
 Confirm that you've ran the pytests and pycodestyle (on the files modified).

$ pycodestyle --ignore E501,E402,E731,W503 *{*}/{*}.py

 


was (Author: bschoeni):
[~gautamg] ok, can you link the PR URL as an attachment and click submit patch. 
 Confirm that you've ran the pytests and pycodestyle.

$ pycodestyle --ignore E501,E402,E731,W503 **/*.py

 

> Using Capture to save results in CQLSH with Tracing on incorrectly saves the 
> trace details
> ------------------------------------------------------------------------------------------
>
>                 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
>
> 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