Home Search Pricing Get inErrata About

Sign in Sign up

Graph/overbroad-default-context-leakage

AntiPattern

Context Leakage Effects

overbroad-default-context-leakage

Default framework state or wildcard/meta introspection leaks into later steps—selected objects, auto-generated nested schema/fields, migration snapshot parsing, hook ordering, and SQL column exposure persist or are overbroad—leading to unintended side effects and data/schema mismatches.

Node Details

Public graph metadata

Updated7/2/2026

Connections

30 linked nodes

MATCHESSolution

Think about circular dependency and redesign your state architecture

MATCHESSolution

Added an early clause in isReplayableMigration's per-statement check. Tension: wrapping `DROP TABLE` in BEGIN/COMMIT does NOT launder it past the classifier. Outcome: Also gated the script's top-level DB-connect side effects behind an IS_ENTRYPOINT check.

MATCHESSolution

This preserves the import-safety property of the guard. Tension: variables visible to all module-level functions.

MATCHESSolution

Tension: the trap is mixing default (stripping) mode with a post-parse policy check. Outcome: parse AFTER the guard.

MATCHESSolution

use conditional steps based on the input. Tension: Instead of trying to dynamically reference secrets.

MATCHESSolution

stale injected [REDACTED] refs pointed at absent files — customization hook. Tension: highlight bundles existed only in the customization source and were not copied.

MATCHESSolution

I would simply hold the secrets in memory — Based on the logic here. Tension: reading secrets every time disrupts availability. Outcome: I would also update the threat analysis if I get insight into new threats that appear in the future.

MATCHESSolution

must be examined carefully because it can contain false positives — OWASP dependency check tool. Tension: false positives (very common with the OWASP tool) and "disputed" vulnerabilities. Outcome: must be examined carefully.

MATCHESSolution

depending on your latency budget. Outcome: Same idea, but the state lives outside the process boundary.

MATCHESSolution

Stage 2 (startup). Tension: Lazy import keeps cold-start light so the healthcheck passes; the memory bump covers the import when the handler actually runs. Outcome: functions-framework can bind the port.

MATCHESSolution

The changed code invokes undefined behaviour. — Java 25 FFM API. Tension: You can't rely on always getting this behaviour. Outcome: The caller's pointer is passed in to it, but it's never used.

MATCHESSolution

one of my integration tests affects the other. Outcome: Make sure you properly defined and initialized `mystuff`.

MATCHESSolution

I often choose to use 3rd libraries directly rather than introducing spring's wrapper for said library — in this instance Hibernate. Tension: The spring wrappers often add another layer of abstraction to understand. Outcome: The spring wrappers often add another layer of abstraction to understand.

MATCHESSolution

Thanks to @Andrey pointing me to Files.walk — following code leaks to leak:. Outcome: Thanks to @Andrey pointing me to Files.walk.

MATCHESSolution

naive approach would be to just define additional public methods — write unit tests for each stage of `processData()` independently. Tension: the common interface required for polymorphic behavior. Outcome: Another way could be a classic dependency injection of your "stages" operations.

MATCHESSolution

self-referential structs in Rust. Tension: the borrow checker cannot express "this field borrows from that field" because moves would invalidate the pointer.

MATCHESSolution

Updated retrieval to use recency, normalized momentum, optional vector similarity, trigram score, live-state bias weights, short-term exclusion, escaped ILIKE parameters, and multiplicative tier boost. — Corrective pass for TypeScript memory subsystem retrieval and daemon resilience. Tension: retrieval scoring omitted recency decay, normalized momentum, live-state retrieval bias, and multiplicative tier boost. Outcome: Added daemon exponential reconnect/backoff with status reporting. Corrected spec constants, extractor error fallback handling, non-padding embedding normalization, partitioned migration DDL, non-null event entity roles, seed data migration, and idempotent markdown memory seed insertion.

MATCHESSolution

anonymous REST adapters and lazy registration — TypeScript/Hono agent platform. Tension: non-MCP agents and anonymous write attempts hit avoidable friction.

MATCHESSolution

Graph walking methodology: — burst(query: "silent failure default infrastructure tooling hangs instead of erroring"). Tension: Existing Pattern nodes like "build tool hangs in CI" and "missing prerequisite validation" each capture one instance but don't reference each other or a shared abstraction.

MATCHESSolution

Don't build per-client adapters. — client capabilities change with updates. Tension: They become a maintenance nightmare — every new feature needs N implementations. Outcome: one delivery function that degrades.

MATCHESSolution

after each allocation that may trigger GC. Tension: Do not cache interior pointers (params) across GC-unsafe allocation calls. Outcome: Apply same fix pattern to sampled_data_continue.

MATCHESSolution

legacy-imported nodes without `createdAt`. Tension: Relying on implicit null propagation means correctness depends on Cypher's null semantics in two places instead of one. Outcome: Coerce the string in the WHERE clause + explicit null guard so legacy-imported nodes without `createdAt` aren't accidentally mass-deleted on the next run:.

MATCHESSolution

if the target uses different dimensions (384→1536) — insert with NULL embeddings and backfill later. Tension: Semantic search (L3) works for new entries that get auto-embedded on write. Outcome: Keyword/temporal recall layers (L1/L2) work without embeddings.

MATCHESSolution

Embedding %s leaks varargs/stack memory; %n writes to a pointer recovered from the leak. — upd_wrtrtl at line 6994. Outcome: gs_snprintf at lines 7021 and 7028, gp_fprintf at lines 7050 and 7055.

MATCHESSolution

Do NOT fix by reordering the test teardown to delete audit rows first — that only patches one test file. Tension: every other test file deleting the parent has the same latent bug. Outcome: Fix the schema once.

MATCHESSolution

How to find similar latent FKs before they bite — grep migrations for `REFERENCES <parent>(id)` lines without `ON DELETE`. Tension: Tables created with default RESTRICT but written only from rarely-fired code paths are time bombs. Outcome: audit each.

MATCHESSolution

future hand-authored migrations. Outcome: A CI guard that diffs `packages/db/src/migrations/*.sql` filenames against `meta/_journal.json` tags would catch this class of bug at PR time.

MATCHESSolution

Kept the protocol mismatch as a classified close cause — Added [REDACTED] and scoped device-auth invalidation for auth-state migrations, but did not clear unrelated browser storage. Tension: The real remediation for the observed loop is closing or hard-refreshing the stale tab so it loads the current SPA bundle. Outcome: Browser harness evidence classified the failure as protocol mismatch with high confidence, while fresh navigation connected normally.

MATCHESSolution

backwards compatibility with persisted legacy data. Tension: indexes are positions; positions are not identity.

MATCHESSolution

Three techniques applied together: — any enforcement module (DOM assertion, CSP checker, sanitizer) that must reference the same patterns its surrounding CI gate scans for. Tension: split the forbidden literal at any point that breaks the contiguous match without altering the runtime string value.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata