RepoJournal
.NET

@dotnet

The .NET runtime, ASP.NET, and the C# tooling

Pick a date

  1. Sat 16 may
  2. Sun 17 may
  3. Tue 19 may
  4. Wed 20 may
  5. Thu 21 may
  6. Sat 23 may
  7. Sun 24 may
  8. Mon 25 may
  9. Tue 26 may
  10. Wed 27 may
  11. Thu 28 may
  12. Fri 29 may
  13. Sat 30 may
  14. Sun 31 may
  15. Mon 1 jun
  16. Mon 8 jun
  17. Tue 9 jun
  18. Today 10 jun

The Wire · Showcase

ANDROID CRYPTO CRASH FIXED, ORLEANS DURABLES GET MAJOR PERF OVERHAUL

By RepoJournal · Filed · About .NET

Runtime patched a JNI exception bug crashing Android RSA operations on Pixel 6a, while Orleans shipped a three-PR stack that rewires DurableJobs scheduling, journaling, and instrumentation for production scale.

The Android crypto fix [1] eliminates a CheckJNI SIGABRT when System.Security.Cryptography tries to import RSA keys that BoringSSL won't construct, particularly 16384-bit keys on Android 16. This lands alongside a JIT cleanup [2] that removes dead loop assertions and formatting alignment fixes [3] for generated thunk code. On the Orleans front, three interdependent PRs landed addressing the entire DurableJobs pipeline: the foundation improves journaled shard throughput with due-now execution, shard striping, and batched writes [4], while a second PR layers on distributed tracing and batching metrics [5]. A third PR tackles Azure Blob journaling instrumentation and WAL retry tuning [6]. The reminder scheduling fix [7] adds diagnostic events to prevent test races when advancing fake time. These Orleans changes represent the team's push toward production-ready distributed job handling at scale.

Action items

References

  1. [1] [Android] Clear pending JNI exceptions in pal_rsa.c to avoid CheckJNI aborts (#128747) dotnet/runtime
  2. [2] JIT: remove dead BBJ_RETURN-in-loop assertion in loop cloner (#128791) dotnet/runtime
  3. [3] Align thunk gen formating with dotnet-format ↗ dotnet/runtime
  4. [4] perf(durablejobs): improve journaled shard throughput ↗ dotnet/orleans
  5. [5] feat(durablejobs,journaling): add tracing and batching metrics ↗ dotnet/orleans
  6. [6] feat(journaling-azure): add instrumentation and retry tuning ↗ dotnet/orleans
  7. [7] Fix deterministic reminder scheduling waits ↗ dotnet/orleans

FAQ

What changed in .NET on May 31, 2026?
Runtime patched a JNI exception bug crashing Android RSA operations on Pixel 6a, while Orleans shipped a three-PR stack that rewires DurableJobs scheduling, journaling, and instrumentation for production scale.
What should .NET teams do about it?
Pull Android RSA crypto patch [ref:1] if shipping to Pixel 6a / Android 16 • Review Orleans DurableJobs three-PR stack [ref:9] [ref:8] [ref:10] if using journaled storage in production • Monitor DurableJobs instrumentation output once deployed to tune shard throughput
Which .NET repositories shipped on May 31, 2026?
dotnet/runtime, dotnet/orleans

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.