News For Dev-ops

If an agent isn't doing the right thing, the obvious move is to make the docs clearer. Add a tip, spell out the correct command, describe the right approach more prominently. You do all of that, and the agent still ignores it. It does what it had already decided to do. The tip wasn't ignored because it was unclear, it was ignored because the agent had already made its plan before it read the page. The agent plans before it reads An AI coding agent doesn't arrive at your documentation as a blank slate. The moment you give it a task, it forms a plan based on what it learned during training, before it goes and fetches a single doc from your site. We wrote about this general behaviour in Models don't have preferences, they have context : when there's nothing in the context to redirect a model, it falls back to whatever the statistical default is from its training data. The thing is, your docs might already be in that training data. If they are, the agent may not eve...

Amazon Relational Database Service (Amazon RDS) Custom for SQL Server now supports the latest Cumulative Updates (CU) and General Distribution Release (GDR) updates for Microsoft SQL Server. This release includes support for SQL Server 2019 CU32+GDR KB5090407 (RDS version 15.00.4470.1.v1) and SQL Server 2022 CU25 KB5081477 (RDS version 15.00.4255.1.v1). The GDR updates address vulnerabilities described in CVE-2026-40370. For additional information on the improvements and fixes included in these updates, see Microsoft documentation for KB5090407, KB5081477. You can upgrade your Amazon RDS Custom for SQL Server instances to apply these recommended updates using Amazon RDS Management Console, or by using the AWS SDK or CLI. To learn more about upgrading your database instances, see Amazon RDS Custom User Guide . Post Updated on June 25, 2026 at 08:44AM

"If we give it no flavor, we can say that it's really subtle." Post Updated on June 25, 2026 at 03:00PM Thanks for reading from devamazonaws.blogspot.com

The team responsible for shell32.dll received a bug saying that they were responsible for a large number of crashes in a particular third party program. Opening the crash dumps showed the clear signs of a stack overflow: # Child-SP RetAddr Call Site 00 000000ba`92851098 00007ff9`fed521c1 ntdll!_chkstk+0x37 01 000000ba`928510b0 00007ff9`feea5ace ntdll!RtlDispatchException+0x2d1 02 000000ba`92851300 00007ff9`fed4e02d ntdll!KiUserExceptionDispatch+0x2e 03 000000ba`92852060 00007ff9`fed5222f ntdll!RtlLookupFunctionEntry+0x8d 04 000000ba`928520b0 00007ff9`feea5ace ntdll!RtlDispatchException+0x33f 05 000000ba`92852800 00007ff9`fed4e02d ntdll!KiUserExceptionDispatch+0x2e 06 000000ba`92853560 00007ff9`fed5222f ntdll!RtlLookupFunctionEntry+0x8d 07 000000ba`928535b0 00007ff9`feea5ace ntdll!RtlDispatchException+0x33f 08 000000ba`92853d00 00007ff9`fed4e02d ntdll!KiUserExceptionDispatch+0x2e 09 000000ba`92854a60 00007ff9`fed5222f ntdll!RtlLookupFunctionEntry+0x8d 0a ...

In the Windows Runtime, there are four interface patterns for representing asynchronous activity.   No return type With return type T Without progress IAsyncAction IAsyncOperation<T> With progress IAsyncActionWithProgress<P> IAsyncOperationWithProgress<T, P> For the purpose of this discussion, I will collectively call these "asynchronous activities". One of the things you can do with asynchronous activities is cancel them, by calling the Cancel method. This method submits a request to cancel, but it does not wait for the operation to acknowledge the cancellation. If you want to wait for the operation to stop executing, you have to wait for it to call the completion callback.² Asynchronous cancellation is important for avoiding deadlocks. Most of the time, the scenarios involve cross-thread synchronous calls, but here's an extremely obvious way it can happen. Suppose that you have registered a progress callback on your asynchronou...

In the previous post in the series, we covered the security decisions you make on day one . In this part, we will talk about how to give your app access to Cosmos DB data, using roles and a managed identity instead of keys. The situation You’ve built your app. It works locally. Now you’re ready to connect it to Azure Cosmos DB, and you hit the question: how does my app get access? There are really only three questions you need to answer: Who  is asking for access? (your app's identity) What  are they allowed to do? (a role) Where  does that permission apply? (a scope)   First, the one distinction that trips everyone up Cosmos DB has two completely separate permission systems. If you remember nothing else from this post, remember this: Control Plane Data Plane What it governs Managing the account: create/delete databases and containers, change throughput, read keys, configure networking Reading and writing the actual data: documents, queries, stored proc...