static-analysis
Here are 943 public repositories matching this topic...
infer version v0.15.0
in my case, 0xFFFF or 0xFFFFFFFF is a common initializer and there are a lot of this semantics in our code. I would like to ignore those harmless. but if I turn off liveness checker, I worry about missing some truely harmful bugs. Does Infer provide some filtering option or method?
Currently the GlobalNamespaceImportFixer tries to import classes from phpdoc annotations, even if they aren't actually used in the code. This is an issue when your coding style dictates that you always use FQCNs in doc blocks only. I don't want it to use the imported class name or import unnecessary classes.
Ideally, it would also have an option to rewrite it to use the FQCN, but that shoul
Feature request
I found that phpstan doesn't understand psalms numeric-string type (see https://psalm.dev/docs/annotating_code/type_syntax/scalar_types/#numeric-string)
It would be nice to support it.
here is playground link
https://phpstan.org/r/9e26dfae-706f-4e3a
One thing that's super useful for new users is code examples. Right now, the biggest problem for someone to start using PHP_CodeSniffer is lack of a list of available Sniffers with their options and examples. From what I know to get a list of all sniffs right now, you have to go through source code in src/Standards
, and it's exhausting. Something like [mlocati/phpPHP-cs-fixer-configurator
](htt
-
Updated
Jul 9, 2020 - Rust
-
Updated
Jun 23, 2020
-
Updated
Jul 7, 2020 - Python
[iOS Tool] Needle
Describe the issue
Needle doesn't seem to be maintained anymore. The last update was > 1 year and no issues have been answered this year. It also doesnt' seem to work on iOS JB devices with Chimera. FSecureLABS/needle#273
We should review where we use Needle and if other tools are a better alternative (e.g. objection, passionfruit).
As you may have read in this blog post, we plan to deprecate TSLint in 2019 and support the migration to ESLint as the standard linter for both TypeScript & JavaScript. This will not be an immediate deprecation; on the contrary, there is a lot of work to do to ensure a smooth transition to the new tooling without any regressions. There are
The email address provided in the "Commercial Uses" section in LICENSE.md is invalid. Emails send to that address return with "User unknown" notice.
discussed in checkstyle/checkstyle#7542 (comment)
we need to extend AbstractGoogleModuleTestSupport to allow load few modules from config file.
In referenced PR we need to load together for each test:
<module name="RightCurly">
<property name="id" value="RightCurlyAlone"/>
<property name="option" value="alone"/>
<property name="tokens"
Not sure how javadoc is managed currently. But I hope this could save some effort on every release.
Basically https://javadoc.io/doc/com.google.errorprone/error_prone_annotation will always point to the latest version published to JCenter / Central Maven.
Or you can add a badge with versions always up to date:
`[. It was also removed in uopz 5.0
internal/reflection_completeness_check.php will help if uopz is installed.
For a lot of things (especially usages) jedi's completely lazy approach is not good enough. It is probably better to use a database index cache. The index will basically be a graph that saves all the type inference findings.
This is just an issue for discussion and collection of possible ideas.
-
Updated
Jul 9, 2020 - C#
The documentation equates two kinds of attribute declarations:
explicit:
class Derp:
attribute: int = 1
@property
def property(self) -> int: ...
and implicit:
class Derp:
def __init__(self):
self.attribute: int = 1
Those two things are not about explicit v
I did a quick search of the issues, both open and closed, but didn't see something like what I'm proposing.
The problem I am having is that reek is throwing up warnings for scaffolding code that hasn't yet been fleshed out. I've included an example below.
I'd like a mechanism that will let me suppress all warnings for a function in the particular instance that the function is not yet impleme
Summary
Get URLs that have parameters, whether http or https, leak sensitive information when they capture parameters such as API-Keys, usernames, and passwords. Browser extensions, bookmarks, history, and server log files capture these, even when operating in anonymous mode. Browser providers could share the information and log files need to mask the sensitive information. Refer: https://ww
Write an article (possibly interactive) on tuning staticcheck's performance. With our new runner (to be committed), memory usage and CPU time behave as expected when you increase the number of processors:
- memory usage grows linearly
- runtime is inversely proportional
- speedups approach an upper limit as per Amdahl's law
If we let staticcheck measure and output the proportion of linear
Low priority since I'd expect the fraction of developers who use bash/zsh and look for completion scripts and set them up manually is small.
Tell us about your environment
- ESLint version: 5.9.0
- eslint-plugin-vue version: 6.1.2
- Node version: 10.13.0
Please show your full configuration:
Affects PMD Version:
All.
Rule:
ImmutableField
Description:
"Identifies private fields whose values never change once object initialization ends either in the declaration of the field or by a constructor. This helps in converting existing classes to becoming immutable ones."
Immutability, by defini
-
Updated
Jul 9, 2020 - C++
There is a step Adding Export Configuration (Step 11) in CMake Tutorial.
There seems no related examples about Export Configuration In the repository, could you add one?
Improve this page
Add a description, image, and links to the static-analysis topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the static-analysis topic, visit your repo's landing page and select "manage topics."
For new checks and feature suggestions
shellcheck.net (i.e. the latest commit) currently gives no useful warnings about thisI can't check shellcheck.net because it requires JavaScript.
Here's a snippet or screenshot that shows the problem: