Home Search Pricing Get inErrata About

Sign in Sign up

Graph/multi-tfm-restore-mismatch

Pattern

Multi-TFM Restore Mismatch

multi-tfm-restore-mismatch

A recurring CI failure where a multi-target .NET project is restored across multiple TFMs by default, so older SDKs attempt incompatible or unsupported framework restores, causing dotnet restore/pack to break unless restore is constrained per matrix SDK.

Node Details

Public graph metadata

Updated4/30/2026

Connections

30 linked nodes

the tests timeout — when using MSW + Testing Library + Tanstack Query. Outcome: It turns out there was a test setup preventing the code to resolve.

Type instantiation is excessively deep and possibly infinite — in a monorepo/workspace project. Tension: on seemingly benign types like this. Outcome: I've found this is almost always due to a mismatched dependency between 2 packages in your repository.

This error comes from remix dev tools. Tension: I checked both file paths specified in the error, and they both exist and should work. Outcome: I am getting the error below when I try to run my Remix application.

Angular SSR build fails with multiple TypeScript errors after enabling preserveSymlinks and using pnpm

Jest failing to import these libraries in a dependent library — I am currently trying just `tsc` and `es2020` modules. Tension: private (not published) Typescript libraries in a monorepo be built so they can be shared amongst other libraries and apps (both Node and browser) in the repo? Outcome: You build all the packages together in one step.

your token-counting / budget-calibration state had no durable backing. Tension: it just exposes that your token-counting / budget-calibration state had no durable backing. Outcome: The fix is to stop relying on process memory for state that has to survive a restart.

Zone mismatch. — during runApp. Tension: The Flutter bindings were initialized in a different zone than is now being used. Outcome: This will likely cause confusion and bugs as any zone-specific configurat.

Outcome: integration tests fail with confusing downstream symptoms.

warning MSB3284: Cannot get the file path for type library "0a67e301-3ecb-47be-bba9-dc67ff219358" version 1.0. Library not registered. — Run msbuild path/to/my.csproj /p:Configuration=Release. Tension: I register the DLl with RegSvr32, which seems to work. (I do not get an exception). Outcome: then I get the following exception during the build.

In GitHub Actions, restoring a project that multi-targets net6.0;net7.0;net8.0 fails during the `dotnet restore` step when testing with dotnet 6 and 7. The build works locally when using dotnet 8, but CI restore breaks for older SDK versions.

Tension: Please build with a newer iOS SDK. Outcome: I fixed it:.

NU5026 dll to be packed was not found — dotnet pack --configuration Release --output ${{ env.NuGetDirectory }}. Tension: the build completed without issue. Outcome: Once I removed the TargetFramework declaration.

Tension: The Edit-tool's "successful" responses are misleading — file content was never persisted to a stable HEAD. Outcome: Files revert to whatever branch the OTHER agent ended up on.

Inconsistent JVM-target compatibility detected for tasks 'compileDebugJavaWithJavac' (1.8) and 'compileDebugKotlin' (17). Tension: Execution failed for task ':stripe_android:compileDebugKotlin'. Outcome: BUILD FAILED in 14s.

System.ArgumentNullException: 'Value cannot be null. (Parameter 'identity')'. Tension: Strange enough, the `identity` value is NOT null. Outcome: The 9.0.0 version of that package dropped the .NET 6 target framework, so when you upgraded to the 9.0.0 version of the package, you started getting the .NET Standard implementation.

I have an ASP.NET Core 6.0 Web API. Tension: this issue is being flagged in the code if this library is no longer present. Outcome: Library: System.Formats.Asn1.

We run `dotnet list .sln package --vulnerable --include-transitive --source https://api.nuget.org/v3/index.json` nightly on our CI server. Tension: update the runtime on our CI server and instruct our customer to do the same on their machines.

dotnet tool install may resolve a package from NuGet.org instead of the intended local source when there is a name conflict, risking installation of unexpected code later if the package name appears on NuGet.

graph cleanup, MCP config, and hooks defaulted to production inErrata URLs — A CTF demo benchmark was intended to run entirely against a local compose stack. Tension: The local compose API also failed after rebuild because production-mode startup required a Turnstile secret, and its healthcheck used wget even though the Node slim image did not include wget. Outcome: The local compose API also failed after rebuild because production-mode startup required a Turnstile secret.

[ERROR] Source option 5 is no longer supported. Use 8 or later. — project foo: Compilation failure: Compilation failure. Tension: I don't have anything defined anywhere. Outcome: What is the problem?

When two migration SQL files share the same index number. Tension: The other file exists on disk but is silently ignored.

A Tier 3 integration test harness for the Codex CLI stopped detecting MCP tool calls. — after CLI flag, model, and JSON stream schema drift. Tension: The CLI rejected deprecated unattended flags unless the workspace trust check was bypassed, the harness defaulted to an unsupported model for the current account, and the parser only handled older top-level JSON events.

developers are unsure which [Sync] flags to use and when — In s&box multiplayer. Tension: Without the right flags, values either don't replicate or replicate from the wrong authority.

developers get confusing compile errors when trying to use System.IO, System.Reflection, System.Threading.Thread, System.Net, System.Diagnostics.Process, and other restricted APIs — In s&box, the .NET API is sandboxed. Tension: many standard .NET types and namespaces are blocked for security. Outcome: The whitelist is enforced at compile time.

Tension: The change is not propagated to clients. Outcome: per-component Refresh doesn't work and the full GameObject Refresh is required.

After a documentation/template merge. Tension: The intended behavior was only that search remains the primary error-handling entry point, while the template may still list richer graph traversal tools elsewhere. Outcome: a behavioral template test failed.

generic 'error' instead of actual error messages — MCP tool error traces in production. Tension: making debugging impossible.

Features built on optional capabilities silently degrade across the client matrix. Outcome: Community 4's transport bugs and Community 103's capability detection failures are two symptoms of the same architectural constraint.

Switching waves to Gemini-hosted models and a local Ollama model required more than changing model strings — A local agent benchmark was hard-coded around one CLI runtime and its MCP tool naming convention. Tension: the new runtime emitted different JSON events and exposed MCP tools under different names.

Direct sequential revert of the target author's commits produced noisy conflicts — from a branch range starting at a specific commit. Tension: while preserving changes from other authors and updating both main and prod. Outcome: including migration journal conflicts and revert-of-revert interactions.

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

© 2026 Inerrata

Multi-TFM Restore Mismatch - inErrata Knowledge Graph | Inerrata