Notes

Short write-ups of one problem and its cause, from day-to-day work with Azure, .NET, CI and web tooling.

17 notes in 2 weeks

Week 47

16–22 Nov 2026

4 notes

  1. Unset GitHub Actions variables defeat Bicep readEnvironmentVariable defaultsA workflow that passes an unset variable defines it as an empty string, so Bicep's readEnvironmentVariable never falls back to its default and the deployment fails only in CI.
  2. Guid.CreateVersion7() keys are not insert-ordered in a SQL Server clustered indexSQL Server sorts uniqueidentifier values by their last six bytes first, so version 7 GUIDs still land on random pages of a clustered index.
  3. Brevo transactional API renders inline images when cid: matches the attachment filenameBrevo's transactional API has no Content-ID field, but an inline image renders when the cid: value is exactly the attachment's name.
  4. Sample stored file bytes before tightening upload validation by magic bytesA stricter upload check based on file signatures would have rejected every upload from the current client. Reading the first bytes of the newest stored blobs showed that before release.

Week 46

9–15 Nov 2026

13 notes

  1. three.js skinned-mesh crowds are processor-bound by bone count, not triangles or backendPer-frame processor time for a crowd of skinned meshes in three.js scales with bones times characters. Triangle count and the WebGPU backend did not change it.
  2. Azure Front Door DRS 2.1 flags legitimate multipart uploads (General-200002/200003)Most legitimate browser multipart uploads reach the anomaly threshold of Azure Front Door's Default Rule Set 2.1 through two General rules, and field exclusions do not cover them.
  3. Azure Document Intelligence flips valueDate on a composed front+back ID imageDocument Intelligence returned a month-first valueDate for a German ID card when front and back were sent as one image, so a fix to the date parser changed nothing.
  4. Identity-keyed WeakMap cache went stale when the key object was mutated in placeA cache keyed on object identity keeps returning the first result after the key object is mutated in place, and tests that only build fresh objects do not catch it.
  5. vite preview returns 404 for the module script of a subpath build that static hosts serve finevite preview answered 404 for the entry script of a build with a base path, while a plain static server and GitHub Pages served the same files without errors.
  6. Playwright --with-deps fails on some hosted CI runners when their Ubuntu mirror does not resolveWhen every e2e test fails with "Executable doesn't exist", the browser install failed one step earlier in apt, and whether it fails depends on which hosted runner the job landed on.
  7. A newly published NuGet advisory can break every restore without any repo changeWith NuGet audit on and warnings treated as errors, a newly published advisory fails dotnet restore with NU1903 on every branch at once, even for a transitive package.
  8. Cloudflare's AI Training "Disallow" policy returns 403 at the edge while robots.txt still says AllowAI crawlers got 403 on every path of a Cloudflare site whose robots.txt allowed them. The block came from the zone's AI Training policy, not from the settings that read as bot protection.
  9. Browser File.type comes from the file name, not the contentThe browser derives File.type from the file extension, so a PDF without the .pdf ending fails a MIME type check in the client and on the server. Check the leading bytes instead.
  10. Azure Blob metadata with non-ASCII values fails in .NET and is retried as if transientBlob metadata travels as HTTP headers, so a file name with an umlaut makes the upload fail in .NET before it reaches Storage, and the Azure SDK retries it six times as if the error were transient.
  11. Round-trip Container Apps templates through az rest, not az containerapp showA template read with az containerapp show cannot be sent back with an ARM PATCH, because the CLI extension adds fields the API rejects. Read it with az rest at the same api-version instead.
  12. Cancelling a GitHub Actions run leaves its ARM deployment running in AzureCancelling a workflow run stops the runner but not the ARM deployment it started, so the next run with the same deployment name fails with DeploymentActive.
  13. Aspire CLI can stop in-process test AppHosts via the auxiliary backchannelAspire integration tests fail at random when someone runs aspire stop or aspire start, because the AppHost inside the test process opens the same CLI backchannel socket as a real one.