Skip to content

Conversation

@Karthikmct
Copy link

This PR will take care of fixing the output format for "telemetry-string-log" command in ocp plug in

Fixed the code to handle json output crash and proper display of ASCII Table content
Disabling debug logs output while parsing telemetry-string-log data

Signed-off-by: Karthik Balan [email protected],

Reviewed-by: Arunpandian J [email protected],

@Karthikmct Karthikmct force-pushed the ocp-nvme-fix-telemetry-string-log branch 3 times, most recently from 9e43e6a to 4f4df42 Compare November 27, 2024 04:21
@igaw
Copy link
Collaborator

igaw commented Dec 2, 2024

Generally, if you commit message already contains bullet points which this change does, these bullet point changes should usually be separate patches.

As far I read the ascii output change, it's a output format change, right? Not sure how you want to handle this. @arthurshau what are you thoughts on this?

@Karthikmct
Copy link
Author

Generally, if you commit message already contains bullet points which this change does, these bullet point changes should usually be separate patches.
@igaw , patch is about fixing json output format for telemetry sting log, one is handling a crash and aligning the ASCII table as per specification requirement. These two fixes goes hand in hand, so raised as one PR.

As far I read the ascii output change, it's a output format change, right? Not sure how you want to handle this.
@igaw , It's about change in ascii table display in json output format. Not a change to output format itself. fix is to align with specification expected template.

Thanks.

@igaw
Copy link
Collaborator

igaw commented Dec 2, 2024

First point, okay. Didn't look too closely. Just thought, it's unrelated.

Second point. If your change doesn't change the field names, then all is good. My argument is that changing the json field names (e.g. renaming) is a regression. The json output should be stable, so that any parser doesn't have to be touched just because we rename something.

@Karthikmct
Copy link
Author

Second point. If your change doesn't change the field names, then all is good. My argument is that changing the json field names (e.g. renaming) is a regression. The json output should be stable, so that any parser doesn't have to be touched just because we rename something.

Got it. No changes are there for the field names. Its still noted 'ASCII Table'. The change is instead of printing the complete ascii data as a single dump, organized it in Byte wise ASCII data (as expected by specification)

@Karthikmct Karthikmct force-pushed the ocp-nvme-fix-telemetry-string-log branch from 4f4df42 to 422412c Compare December 3, 2024 02:49
@Karthikmct
Copy link
Author

@igaw , To ease the review and merge. I modified this pull request into 2 part. This part is to fix the json output format crash and disabling the debug prints only.

Will take up the ASCII Table alignment in a separate pull request. please check further :)

@igaw
Copy link
Collaborator

igaw commented Dec 3, 2024

Looks good, just the reserved field renaming thing

@Karthikmct Karthikmct force-pushed the ocp-nvme-fix-telemetry-string-log branch 2 times, most recently from 5030aa3 to db99855 Compare December 3, 2024 12:07
Fixed the code to handle the json output crash
Disabled debug logs output when parsing telemetry-string-log data

Signed-off-by: Karthik Balan [email protected] <[email protected]>
Reviewed-by: Arunpandian J <[email protected]>
@Karthikmct
Copy link
Author

@igaw , Could you please update further on the patch upstream?
Do let me know on clarification.

@igaw igaw merged commit 457d182 into linux-nvme:master Dec 5, 2024
17 checks passed
@igaw
Copy link
Collaborator

igaw commented Dec 5, 2024

Looks good to me. Thanks!

@Karthikmct Karthikmct deleted the ocp-nvme-fix-telemetry-string-log branch December 9, 2024 03:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants