| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit contains several other changes as part of the upgrade:
- Use -XepAllDisabledChecksAsWarnings to enable all available warnings so
that we don't need to enable each warning explicitly.
- Remove explicit suppression of warnings in generated code, since
-XepDisableWarningsInGeneratedCode is now sufficient to suppress all warnings
in AutoValue and Protocol Buffer generated classes.
- Remove a suppression of "ConstructorLeaksThis", since
https://github.com/google/error-prone/pull/789 was fixed.
- Fix a few occurrences of "FieldCanBeFinal".
|
| | |
|
| | |
|
| |
|
|
|
|
| |
MutableMethodReturnType suggests returning Guava immutable collections from API
methods, but OpenCensus doesn't expose Guava in its API. See
https://github.com/google/error-prone/issues/982.
|
| | |
|
| |
|
|
|
|
|
| |
This commit adds some Nullable annotations that are required by the Checker
Framework, but it doesn't change any other code. It also suppresses some Error
Prone and FindBugs warnings that conflict with the Checker Framework, since the
three tools use different algorithms.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
I used the latest list of bug patterns from http://errorprone.info/bugpatterns.
I had to turn off FieldMissingNullable because of an Error Prone bug and
suppress two instances of other warnings in the code.
I removed NonRuntimeAnnotation and ProtocolBufferOrdinal from the list because
they were promoted to errors. I also enabled two previously disabled warnings
because they seemed to no longer cause any problems in this project.
|
| |
|
|
| |
This commit also fixes two occurrences.
|
| |
|
|
| |
I also added some missing Nullable annotations.
|
| |
|
|
| |
This commit also adds some private constructors to utility and example classes.
|
| |
|
|
|
|
|
|
|
|
|
| |
Other changes:
- Remove references to warnings that were removed from Error Prone.
- Suppress occurrences of a new warning, JdkObsolete. All of the warnings are
about uses of LinkedList. We need to decide whether to use a different class
or continue suppressing the warnings. I left TODOs, since each occurrence may
need to be handled differently.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
I've run the following command line:
./gradlew wrapper --gradle-version=3.5
Among other things, this fixes the issue described in https://github.com/gradle/gradle/issues/1387
("Exception: java.lang.IllegalStateException thrown from the UncaughtExceptionHandler in thread...").
I've run into this issue when adding more instrumentation logic to the Java agent. It makes
debugging the actual issue nearly impossible as any useful debug output is lost.
While there, also upgrade the errorprone-plugin to 0.0.10 (was 0.0.9) because the previous version
is broken in Gradle 3.5, cf. https://github.com/tbroyer/gradle-errorprone-plugin/issues/37.
|
| | |
|
| |
|
|
|
| |
This includes RemoveUnusedImports. I excluded PrivateConstructorForUtilityClass
because there were too many warnings in the examples directory.
|
| | |
|
|
|
* Add support for gradle to build the instrumentation-java.
* Change the version to 0.4.0-SNAPSHOT.
|