HighFile-scopeJava Plug & play

Propagate exceptions instead of hiding failures

Never swallow exceptions silently; wrap with context and rethrow or translate to a domain exception.

Why this matters

Hidden failures corrupt state and break retries/alerts.

Side-by-side examples engineers can pattern-match during review.

Avoid

try { doWork(); } catch (IOException e) { /* ignore */ }

Prefer

try { doWork(); } catch (IOException e) { throw new UncheckedIOException("doWork failed", e); }

Bad

catch(Exception e){}

Good

catch(Exception e){ throw new RuntimeException("context", e); }

From the same buckets as this rule.

Critical
Avoid equality operators in loop termination conditions
Check if loops use equality operators (== or !=) in termination conditions. These can lead to infinite loops if the condition is never met exactly. Instead, use relational operators like < or > for safer loop termination.
error-handlingreadability-refactor
Critical
Avoid Returning Null in Non-Async Task Methods
Returning null from a Task or Task<T> method causes a NullReferenceException if awaited. Use Task.CompletedTask or Task.FromResult<T>(null) instead.
error-handlingreadability-refactor+1
Critical
Avoid Using Boolean Expressions in `except` Statements
Detect `except` clauses that use `or` or `and` to catch multiple exceptions. This does not work as intended. Recommend using a tuple of exceptions instead.
error-handlingstack-python