News For Dev-ops

Amazon CloudWatch pipelines now supports processing and enriching OpenTelemetry (OTel) metrics during ingestion. CloudWatch pipelines is a fully managed service that ingests, transforms, and routes telemetry data to CloudWatch without requiring you to manage infrastructure. Until now, customers who needed to enrich or transform OTel metrics before storage had to build custom processing layers or modify application instrumentation at the source. With OTel metric processing in CloudWatch pipelines, you can apply metric transformations centrally as part of the ingestion path with no new infrastructure required. With CloudWatch pipelines, you can enrich metrics by adding business context such as team ownership, cost center, and environment tags to metrics from sources you cannot modify. You can strip high-cardinality labels from custom workloads to reduce storage costs, and rename metrics and attributes to enforce consistent naming conventions across your organization. Processing is appl...

GitHub Copilot is now a first-class, native option in JetBrains AI Assistant agent picker( read more ).  You can select it directly from the chat interface, no extra configuration needed, and immediately put Copilot to work on real coding tasks without ever leaving AI Assistant . Millions of developers already rely on the GitHub Copilot plugin as their AI pair programmer inside JetBrains IDEs. Copilot has long been reachable through JetBrains AI Assistant via the Agent Client Protocol (ACP) , but today we are taking that integration a significant step further. [alert type="tip" heading="✨ What's new at a glance"]Open the Chat Panel in JetBrains AI Assistant -> Select GitHub Copilot from the AI Assistant agent picker -> Hand off coding tasks and iterate in real time [/alert] This is not a separate window or a plugin toggle. Inside the AI Assistant chat panel you now have a unified place to choose which AI agent drives your conversation, and GitHub...

Starting today, Amazon Elastic Compute Cloud (Amazon EC2) C9g and C9gd instances, powered by AWS Graviton5 processors, are generally available. AWS Graviton5 processors are the fifth generation of custom-designed CPUs, delivering the best price performance for compute-intensive workloads running on Amazon EC2. C9g instances are ideal for workloads such as high-performance computing (HPC), batch processing, gaming, video encoding, scientific modeling, distributed analytics, CPU-based machine learning (ML) inference, real time analytics, and ad serving. C9gd instances offer local NVMe-based SSD block-level storage for customers running compute-intensive workloads that also require high-speed, low-latency local storage for scratch space, temporary files, and caches. C9g and C9gd instances deliver up to 25% better compute performance compared to AWS Graviton4-based C8g and C8gd instances. They are up to 30% faster for databases, up to 35% faster for web applications, and up to 35% fas...

We're excited to release React Native Windows 0.84.0, aligned with React Native 0.84.1. React Native Windows v0.84 delivers input-handling improvements such as standard click events and imperative focus, theme-aware defaults and robust hit-testing semantics. 🔥 What's New in RNW v0.84? Minimum Requirements Visual Studio 2026 is required for 0.84 version of RNW. onClick  and  onAuxClick  Events for Fabric Components Fabric components now fire standard  onClick  and  onAuxClick  events, bringing RNW's click-handling model in line with the W3C specification. Windows developers can now handle primary and auxiliary (middle-click) interactions using the same patterns as web and other React Native platforms — enabling consistent context menus, open-in-new-tab gestures, and multi-button input without custom workarounds. Imperative Focus via  view.focus() The imperative  focus()  API is now enabled for Fabric views. Windows developers can programmatically move focus to any ...

Windows provides a family of functions for accessing so-called "extra bytes". There are two categories of extra bytes: Class extra bytes (which belong to the window class) and window extra bytes (which belong to each window created from that class). Applications can request extra bytes at class registration, and those are accessed at increasing offsets starting at zero. The system also defines a number of extra bytes, and those use negative offsets. We're going to look at the system-defined offsets. In 16-bit Windows, these were the available extra bytes and the function you used to read them: Name Size Accessor Notes GCW_MENUNAME int16_t GetClassWord   GCW_HBRBACKGROUND int16_t GetClassWord   GCW_HCURSOR int16_t GetClassWord   GCW_HICON int16_t GetClassWord   GCW_HMODULE int16_t GetClassWord   GCW_CBWNDEXTRA int16_t GetClassWord   GCW_CBCLSEXTRA int16_t GetClassWord   GCL_WNDPROC int32_t GetClass...

Amazon ElastiCache now supports Valkey 9.1 for node-based clusters, delivering higher throughput, improved memory efficiency, and stronger access control for multi-tenant workloads. This release helps customers get more performance from existing infrastructure while simplifying common application patterns with new commands. Valkey 9.1 includes a redesigned I/O threading model that improves throughput by up to 17%, reduces memory usage for strings under 128 bytes by up to 20%, and introduces database-level access control lists that let administrators scope user permissions to specific numbered databases. New commands like HGETDEL for atomic hash field retrieval and deletion, MSETEX for setting multiple keys with a shared expiration, and CLUSTERSCAN for cluster-wide key iteration simplify workflows that previously required multi-step client logic. The release also adds new main-thread and I/O-thread usage metrics for better operational visibility.  To get started, see Creating a...

If you’re building and maintaining Visual Studio extensions, you’ve probably ended up with some sort of build and publishing workflow - whether it’s manual, scripted, or stitched together over time. This post is for extension authors who want a simple, repeatable way to build, version, and publish their VSIX files using GitHub Actions. I’m going to show how I do this across my own extensions. I’ve been using this approach for a long time, and over time I pulled the most repetitive pieces into a few small reusable actions, so I don’t have to keep rewriting the same logic in every repo. Those are: vsix-version-stamp – keeps your versioning in sync publish-vsixgallery – publishes CI builds for testing publish-marketplace – publishes to the Visual Studio Marketplace You can use them independently or together, but I tend to use all three. If you want to see this wired up in a real repo, take a look at Start Screen . A real workflow Here’s a simplified setup very s...

Part 2 of Build your own claw and agent harness with Microsoft Agent Framework . In Part 1 we stood up a harness and gave our personal finance assistant its first abilities: a custom tool, web search, and planning. It can talk about the markets - but it can't yet touch your data, and nothing stops it from taking a sensitive action on a whim. This part fixes both, using three abilities that are all included in the harness: File access - read your portfolio from a CSV and write reports back to disk. Approvals - gate risky actions (like placing a trade) behind a human's explicit OK. Durable memory - remember things across sessions, in two complementary ways. As before, we only supply what makes our agent ours ; the harness provides the machinery. Let's take the three in turn. Give it your data: file access Our assistant should work from the user's actual holdings, not made-up numbers. The harness includes a file-access provider that exposes a set...

On July 1, 2027 , Remote Event Receivers (RERs) will stop working in SharePoint Online. After that date, no remote event receiver will fire events, regardless of how it was registered. If your application still relies on remote event receivers to react to changes in SharePoint, now is the time to plan your move to SharePoint webhooks . [alert type="important" heading="Key message"]All remote event receivers in SharePoint Online will stop working on July 1, 2027. Migrate any remaining RER-based functionality to SharePoint webhooks (or Microsoft Graph change notifications) before that date.[/alert] Background Remote event receivers are part of the SharePoint Add-in model and depend on Azure Access Control Services (Azure ACS) for authentication. With the retirement of Azure ACS now complete, remote event receivers registered using Azure ACS have stopped functioning correctly as of April 2, 2026 . They can still be added programmatically, events might still fire, bu...

The wait is over.  Spring AI 2.0 is generally available , and Azure Cosmos DB is right there with it. With this release, Spring AI graduates into a mature, production-ready framework for building AI applications in Java, and Azure Cosmos DB ships  dedicated, vendor-maintained integrations  that plug straight into the Spring AI ecosystem. The Spring AI 2.0 GA announcement names Azure Cosmos DB among its vendor-maintained modules, maintained directly by Microsoft rather than the core Spring AI team. This means the integration is built and supported by the engineers who work on Cosmos DB itself, bringing deep, first-hand knowledge of how to get the most out of it. If you are a Java or Spring developer building RAG pipelines, chatbots, or multi-agent systems, this is a great moment to start (or restart) on Azure Cosmos DB. What changed in Spring AI 2.0 (and why it's good news for Cosmos DB) Spring AI 2.0 brings a cleaner, more modular architecture built on  Spring Boot 4.1  and ...

Last time, we looked at crashes caused by a DLL being removed from memory behind everybody's back , causing crashes when somebody tried to call into that no-longer-there DLL that everybody thought was still there. A colleague of mine who was looking at other crashes coming from this process found that most of those other crashes were also of the form "a data structure was corrupted because somebody wrote the single byte 01 into it." That piece of information made everything fall into place for my side of the investigation. We saw earlier that the bottom bit of the HMODULE is set for datafile module handles . Therefore, if one of these stray 01 bytes happens to overwrite the bottom byte of an existing HMODULE handle, that turns it into a (fake) datafile module handle. And then, during process destruction, a component dutifully cleans up the DLLs they loaded by freeing them (say because they were stored in an RAII type like wil:: unique_ hmodule ), the code will pas...