https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-2425 Lustre <p>The code generated by wirecheck and wirecheck.c do not follow new coding style (use of space + line too long)</p> LU-2425

wirecheck does not follow new coding style

Bug Minor Resolved Won't Fix Bob Glossman CEA Tue, 4 Dec 2012 11:25:06 +0000 Wed, 5 Aug 2020 13:32:56 +0000 Sat, 8 Mar 2014 01:24:51 +0000 0 5 <p>Bob</p> <p>Could you please look into this one?</p> <p>Thanks</p> <p>Peter</p> <p>While it's true that the generated sources like wiretest.c still use spaces instead of tabs as the newest coding conventions recommend, is this really important to fix? It seems to me that the risk of introducing bugs by fiddling with the generator code in wirecheck.c far exceeds the value of exactly matching current conventions. The existing generated code is still perfectly good and valid.</p> <p>If you use the official and mandatory git/hooks, you cannot commit a patch which does not follow the coding style.<br/> Without the right coding style, a patch does not pass the review.<br/> There are multiple issues that build/checkpatch.pl does not like in the generated code (line too long, space vs tab, missing spaces, ...)</p> <p>Bob, it is an oversight that the wiretest.c and wirecheck.c files do not match the coding style.</p> <p>I suspect it would be relatively straight forward to fix the wirecheck.c code to match the coding style (use a tab for indentation, add a line break and indent in the middle) and then regenerate the wiretest.c files.</p> <p>With diff highlighting in Gerrit, it should be relatively straight forward to verify that the commit which updates these files does not introduce any semantic changes.</p> <p>JC, please note that while the git commit hooks may report warnings and errors with the <em>code</em> style, these do not prevent committing the change. It only prevents committing the change if the commit message itself is incorrect. </p> <p>I have revised wirecheck.c and generated new wiretest files that eliminate all the errors and warnings except for the ones for lines over 80 characters. Given the very long casts and offestof() and other complex strings with few spaces, I couldn't figure out good ways to shorten many lines.</p> <p>Pushing what changes I have for review.</p> <p><a href="http://review.whamcloud.com/#change,4751" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#change,4751</a></p> <p>It seems this was fixed as part of the HSM patch <a href="http://review.whamcloud.com/4736" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/4736</a>. Are there still bits left in the 4751 patch that are needed, or should this be closed?</p> <p>It's been quite a while since I revisited this. It looks to me like all the tabs/spaces issues have been fixed. There are still lines &gt; 80 chars in wiretest.c, but the proposed patch didn't fix those anyway.</p> <p>I believe this should be closed. I'll go ahead and mark <a href="http://review.whamcloud.com/4751" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/4751</a> ABANDONED.</p> <p>Partly fixed, but not completely.</p> Development Rank 1|hzvd8n: Rank (Obsolete) 5750 Severity