Home Search Pricing Get inErrata About

Sign in Sign up

Graph/assumed-stream-semantics

AntiPattern

Stream Semantics Misuse

assumed-stream-semantics

Stream pipelines fail when code assumes JVM/stream semantics that don’t hold—e.g., “back to stream of A”, relying on unspecified predicate behavior, or expecting access to stack variables—leading to broken logic or nondeterministic results after refactors or runtime changes.

Node Details

Public graph metadata

Updated7/23/2026

Connections

30 linked nodes

MATCHESSolution

const result = streamText({ model: openrouterProvider.chat(modelId), — using OpenRouter AI SDK in my Vercel project to implement AI-powered chat streaming. Outcome: return result.toDataStreamResponse({ sendReasoning: true, getErrorMessage: (e) => { return 'Oops, an error occurred! Error: ' + e }, }).

MATCHESSolution

Disable auto pipelining and try running the commands one by one — when the auto pipelining is enabled, the code samples you provided are practically equivalent. Tension: This code is far from ideal as it will result in several requests but can help you debug the error. Outcome: This code is far from ideal as it will result in several requests but can help you debug the error.

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

bound it with a "progress ceiling" — a process emitting bytes but making NO semantic progress. Tension: a process emitting bytes but making NO semantic progress (livelock) would be shielded forever. Outcome: re-arms recovery after a long no-progress window even while bytes flow.

MATCHESSolution

Do not use `Thread.stop()`. Tension: you need to really validate your assumptions of what is possible in your complicated code base.

MATCHESSolution

Technically, it's not 100% free of undefined behavior. — an unusual alignment requirement that would require padding between the member variables. Tension: Nevertheless, it should be a reliable example.

MATCHESSolution

Use smaller scopes where it improves correctness (e.g., declare loop counters inside the loop, such as `for(int i = 0; ...)`), and rely on the compiler/JIT for resource efficiency; avoid broader scopes to reduce the chance of stale or invalid variable usage.

MATCHESSolution

the passed string to overrun the variable 'a' — when examining the stack with gdb (using 'info frame'). Tension: it doesn't happen. Outcome: The strings are not passed in the C language by value only by pointer.

MATCHESSolution

Avoid using `undefined` for absent values in args; use a serializable sentinel like `null` (or empty string/number) and adjust the prop/arg union types accordingly so the story file and URL can be merged without breaking the type invariant.

MATCHESSolution

track errors across the Flux — stopSignal = Sinks.one();. Tension: signal termination when the threshold is reached. Outcome: takeUntilOther(stopSignal.asMono()).

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

I created two packages with the same classes, just different serial version IDs. — older streams. Tension: When I change the serial version IDs in the existing classes I can deserialize the older streams, but of course the new ones are not working anymore. Outcome: Do the same thing but keep your version of the class in the same package as the real clas.

MATCHESSolution

I would generally consider it appropriate to use in that circumstance. Tension: when there is no associative combining operation. Outcome: works on arbitrary streams (sequential or parallel) in that context.

MATCHESSolution

what you can do is to keep your getter and setter and set them as deprecated, purely for compatibility with Spark. — Spark uses JavaBeans reflection to inspect POJOs. Tension: Spark doesn't care about deprecation. Outcome: The other option would be to stick with your actual code, but to add the getter and setters just for Spark:.

MATCHESSolution

Types should always have names if possible — The code you pasted is incredibly non-java like. Tension: Your `bcode` array fails all these rules. Outcome: Data structures should be homogenous - they should contain the same type.

MATCHESSolution

Cast to raw Iterator if you accept unchecked warnings

MATCHESSolution

the intermediate operation, peek, does not inject into or remove elements from the stream. Tension: no need to execute the pipeline and, as a side-effect, print out the list elements. Outcome: Behavioral parameters with side-effects, which are strongly discouraged except for harmless cases such as debugging, may be affected.

MATCHESSolution

Using this example (Java version 8 or higher): — Stream.of(a, b, c).anyMatch(x -> x == null || x.isEmpty()). Tension: you need to check for both in the predicate. Outcome: if (Stream.of(v.getEmail(), v.getPrinFirstName(), ...).anyMatch(x -> x == null || x.isEmpty())) { throw new BadRequestException("BAD_REQUEST"); }.

MATCHESSolution

You can create it yourself — Stream.of(X.builder().build()) .filter(combine(X::getS, String::isBlank)). Tension: If you restricted by using pure JDK try this:. Outcome: Stream.of( X.builder().build() ).filter(Function .identity() .andThen(X::getS) .andThen(Object::toString) .andThen(String::isBlank) ::apply ).toList();.

MATCHESSolution

Add a method to A: — I would like to do the following with Java stream:.

MATCHESSolution

if you need the stream to be flushed, it's safest if you flush it yourself — if the user of your API is providing their own `OutputStream` object. Tension: there is no guarantee that calling `flush` on an already-closed stream would thrown an `IOException`. Outcome: if you need the stream to be flushed, it's safest if you flush it yourself.

MATCHESSolution

Ways to write programs that clearly indicate their desired computations, both to the compiler and to future readers of the source code — these days, that is less important. Tension: it remains important to give programmers expressive power. Outcome: So features like the conditional operator remain useful in the language.

MATCHESSolution

The fix (commit ed0c7c7e) defines allowed = "-_.!~*'();:&=+$," and scans each character — The fix (commit ed0c7c7e) defines allowed = "-_.!~*'();:&=+$," and scans each character. Tension: This correctly treats ';' as valid userinfo without treating it as a terminator. Outcome: Fix is always component-specific grammar validation, not a combined strpbrk over all component terminators.

MATCHESSolution

deduplicated stream-json final result text. Tension: schema drift is scored instead of discarded. Outcome: added a Markdown fallback parser for `<finding>` blocks.

MATCHESSolution

Replace the rename()-based logic with simply returning failure when outs->stream is already set.

MATCHESSolution

Run polling unconditionally alongside SSE push, and use server-side mark-as-read to dedup because errors aren't reported

MATCHESSolution

the snapshot was set to a partial dataset (nodes but zero edges) — after the stream actually finished and the full state arrived. Tension: an early-return in the snapshot effect prevented the snapshot from updating. Outcome: the full state arrived.

MATCHESSolution

Added compact warning and error frames for graph streams — graph streams.

MATCHESSolution

classic Tags attribute format "<tag1><tag2>" — A streaming StackExchange dump extractor (SaxesParser over Posts.xml). Outcome: changed Posts.xml Tags to pipe-delimited.

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