The Scoped Singleton DI Bug Your AI Just Suggested

May 21, 2026 · 10:23 PM UTC ·5 min read · 0 reactions · 0 comments · 34 views

#programming #dotnet #ai #softwaredevelopment #bugs

TL;DR · WeSearch summary

The article discusses a common bug in dependency injection related to scoped and singleton lifetimes in .NET applications. It highlights how this bug can lead to data corruption when caching entities that are tied to a scoped DbContext. The author emphasizes the importance of understanding dependency lifetimes to avoid such issues, especially when using AI tools for coding assistance.

Key facts

▪The captured-dependency lifetime bug occurs when a singleton service holds a reference to a scoped service, leading to potential data corruption.
▪AI coding assistants often suggest patterns that omit important context about service lifetimes, resulting in the propagation of this bug.
▪Developers are encouraged to enforce rules regarding dependency lifetimes to prevent common pitfalls when integrating caching and database access.

About this source

DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.

All DEV.to (Top) coverage →

Original article

DEV.to (Top)

Read full at DEV.to (Top) →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	DEV.to (Top)
Canonical URL	https://dev.to/agentic_standard/the-scoped-singleton-di-bug-your-ai-just-suggested-jo0
Publication time	Thu, 21 May 2026 22:23:27 +0000
Retrieval time	2026-05-21T22:31:35.997Z
Last seen	2026-05-21T22:31:35.997Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	sBxewFO0Zeqf
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3943025) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } agentic.standard.contact Posted on May 21 • Originally published at agenticstandardcontact-byte.github.io The Scoped Singleton DI Bug Your AI Just Suggested #csharp #cursor #ai #dotnet The Scoped→Singleton DI bug your AI just suggested (and how to catch it) Of all the bugs that ship to production silently, the captured-dependency lifetime bug is one of the most expensive. It compiles. It passes your tests. It runs fine in dev.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed

Discussion

0 comments