Skip to content
This repository has been archived by the owner on Nov 14, 2024. It is now read-only.

Cleanup warnings and enforce DefaultLocale error-prone check #6393

Merged
merged 2 commits into from
Dec 5, 2022

Conversation

schlosna
Copy link
Contributor

@schlosna schlosna commented Dec 2, 2022

General

Before this PR:
Many DefaultLocale error-prone warnings when compiling

See palantir/gradle-baseline#2343

After this PR:
Ran ./gradlew compileJava compileTestJava -PerrorProneApply=DefaultLocale to auto-fix and checked results.

==COMMIT_MSG==
Cleanup warnings and enforce DefaultLocale error-prone check
==COMMIT_MSG==

Priority:

Concerns / possible downsides (what feedback would you like?):

Is documentation needed?:

Compatibility

Does this PR create any API breaks (e.g. at the Java or HTTP layers) - if so, do we have compatibility?:

Does this PR change the persisted format of any data - if so, do we have forward and backward compatibility?:

The code in this PR may be part of a blue-green deploy. Can upgrades from previous versions safely coexist? (Consider restarts of blue or green nodes.):

Does this PR rely on statements being true about other products at a deployment - if so, do we have correct product dependencies on these products (or other ways of verifying that these statements are true)?:

Does this PR need a schema migration?

Testing and Correctness

What, if any, assumptions are made about the current state of the world? If they change over time, how will we find out?:

What was existing testing like? What have you done to improve it?:

If this PR contains complex concurrent or asynchronous code, is it correct? The onus is on the PR writer to demonstrate this.:

If this PR involves acquiring locks or other shared resources, how do we ensure that these are always released?:

Execution

How would I tell this PR works in production? (Metrics, logs, etc.):

Has the safety of all log arguments been decided correctly?:

Will this change significantly affect our spending on metrics or logs?:

How would I tell that this PR does not work in production? (monitors, etc.):

If this PR does not work as expected, how do I fix that state? Would rollback be straightforward?:

If the above plan is more complex than “recall and rollback”, please tag the support PoC here (if it is the end of the week, tag both the current and next PoC):

Scale

Would this PR be expected to pose a risk at scale? Think of the shopping product at our largest stack.:

Would this PR be expected to perform a large number of database calls, and/or expensive database calls (e.g., row range scans, concurrent CAS)?:

Would this PR ever, with time and scale, become the wrong thing to do - and if so, how would we know that we need to do something differently?:

Development Process

Where should we start reviewing?:

If this PR is in excess of 500 lines excluding versions lock-files, why does it not make sense to split it?:

Please tag any other people who should be aware of this PR:
@jeremyk-91
@sverma30
@raiju

@schlosna schlosna marked this pull request as ready for review December 5, 2022 15:25
@bulldozer-bot bulldozer-bot bot merged commit 0df1b6b into develop Dec 5, 2022
@bulldozer-bot bulldozer-bot bot deleted the ds/warnings branch December 5, 2022 15:25
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants