search for: linters

...m >> folks suggest we enable the Lint feature in Arcanist ( >> https://secure.phabricator.com/book/phabricator/article/arcanist_lint/). This >> will enforce the check when `arc diff` is run (reviewers wouldn't see the >> warnings though). >> >> There are two linters we might be interested in enabling: >> - cpplint (code style checker based on cpplint.py >> <https://github.com/google/styleguide>) >> - cppcheck (C++ linter based on cppcheck <http://cppcheck.sourceforge.net/>) >> >> Note that cpplint assumes google code...

Hi all, I've noticed several patches that were updated overnight UK time where the following message was produced by the Phabricator linter check: "clang-format-diff not found in user's PATH; not linting file." I'm guessing that something has gone wrong on whatever bot does this? James -------------- next part -------------- An HTML attachment was scrubbed... URL:

...m (https://secure.phabricator.com/T11879), and upstream folks suggest we enable the Lint feature in Arcanist ( https://secure.phabricator.com/book/phabricator/article/arcanist_lint/). This will enforce the check when `arc diff` is run (reviewers wouldn't see the warnings though). There are two linters we might be interested in enabling: - cpplint (code style checker based on cpplint.py <https://github.com/google/styleguide>) - cppcheck (C++ linter based on cppcheck <http://cppcheck.sourceforge.net/>) Note that cpplint assumes google code style, but I think it can potentially be repl...

Hi All, I just posted a review with arcanist (which I'm fairly new to) and it included a build status. How it got there is totally opaque to me, but my workflow was: Using git+svn (following the setup in https://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-git-svn) make a change, commit with 'git commit', create review with 'air diff'. It would be cool if

...ass" class generator generator function, and the few examples I've looked at on CRAN set it the same as the name of the generator function, for example, from the docs: Queue <- R6Class("Queue", .....) but this isn't mandatory, it can be anything. Or NULL. (side quest: do linters exist that flag this as bad style?). Does anyone have an example of a CRAN package where this isn't the case? Or even where an R6 class generator uses the default "NULL" for its classname parameter? My introspection code is in two minds whether to use the classname to label diagrams...

On 11/14, Mehdi Amini via llvm-dev wrote: > Ideally I’d even really like to have a both checking for revision on > phab, clang-formatting them, and post a comment when there is a > mismatch :) I'd like that! -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: Digital signature URL:

I have to say <<- is a core debugging tool when assigning into the global environment. I suppose I could use assign but that would be somewhat annoying. That said I'm still for this change, the vast overwhelming number of times that <<- is in my package code - already rare but it does happen - it would absolutely be a bug (typo most likely) for it to get to the global environment

First, I love this bot:) It makes LLVM's "pushing to master" practise less awful:) Now the main topic... > clang-tidy: fail. Please fix clang-tidy findings. For example, on https://reviews.llvm.org/D72103#1801916 , merge_guards_bot reports clang-tidy findings of existing code, not just the modified code. I think https://github.com/google/llvm-premerge-checks should use

...queue for way too long, such as importing one of the branches offering libusb-1.x support) do not introduce apparent regressions, while developers can run the same script as CI does to check for same test conditions locally and avoid posting bugs even in their initial commits. Modern compilers and linters do a decent job at predicting issues with code (and asking different tools on different systems gives a lot more different answers for the same question), so not all of the past month's changes were style and cosmetics ;) Even for cases that are not fully green yet, developers would not drown i...

I'm probably missing something really simple. I've installed an RH8 IAM in AWS and I'm trying to build packages on it. I've noticed there are many *-devel packages that I cannot install: ######################################## [ec2-user at site1-vpn ~]$ sudo yum install trousers-devel Last metadata expiration check: 1:10:41 ago on Thu 04 Jul 2019 01:01:14 AM UTC. No match for

Hi, Is there a rule or guideline about what Python versions must be supported for scripts in the LLVM tree? I am working on some patches to some scripts in LLVM to use features in Python 2.7, so that these scripts can run under Python 2.7 and Python 3.x Is that OK? For example, here is a patch to use print as a function, so that the scripts can work in Python 2.7 and Python 3.x -- Craig

Sounds reasonable, but I leave it to wiser heads than me to decide. My only point is that whatever is done be accurately documented. At present, that does not appear to be the case. ... and yes, "accurate" documentation is not easy either. -- Bert On Fri, Dec 13, 2024 at 3:20?PM Ben Bolker <bbolker at gmail.com> wrote: > > Thanks, I had missed/forgotten the fact that

On Sun, Oct 5, 2014 at 9:37 AM, Renato Golin <renato.golin at linaro.org> wrote: > On 5 October 2014 07:19, Saleem Abdulrasool <compnerd at compnerd.org> wrote: > > So with that in mind, I would like to ask, would it be possible to > consider > > switching to LLVM style for lld? > > We don't usually enforce code styles on side projects because it >

hi, after i test nsd i find the following. if i use this in a zone file: $ORIGIN example.com. CNAME www www CNAME x x A 1.2.3.4 then it's excepted by nsd what's more give the proper result. if the slave is nsd than there is no problem, while if the slave is bind i've got the following error: