For Python, developers now can run Python tests with coverage and get rich results in the editor, Microsoft said. To run tests with coverage, users must select the coverage run icon in Test Explorer or “Run with coverage” from any menu that triggers test runs. The Python extension will run coverage by using the pytest-cov plugin if developers are using pytest, or by using coverage.py if using unittest. Once the coverage is complete, lines are highlighted in the editor for line-level coverage. The Python extension also has added a default problem matcher, simplifying issue tracking in Python code and providing more contextual feedback.

The Source Control Graph in Visual Studio Code 1.94 features a new history item reference picker in the view title, allowing developers to use the reference picker to filter the history items shown in the graph to a different branch or to view multiple branches. The Source Control Graph also expands the list of actions available in the context menu for source control history items. Actions have been added to create a new branch/tag from a history item, cherry-pick a history item, and check out an item.

Elsewhere in Visual Studio Code 1.94:

Business reputation and trust are always vulnerable; companies recognize that a security breach can instantly damage both. Indeed, you’ll get yourself on the morning news and watch your stock drop by 50%. By prioritizing security, businesses aim to safeguard their reputation and customer relationships.

Long-term cost implications mean that focusing initially on cost and scalability might seem feasible, but the long-term financial impact of security incidents can be severe. Most people in the cybersecurity space understand that risk equals money. The more risk, the less your systems are worth, considering the potential for a breach. Prioritizing security can prevent costly breaches and downtime.

Innovation and agility mean that to remain competitive, businesses need to innovate rapidly. A secure cloud infrastructure enables this by providing a reliable foundation for building and deploying new services without compromising data integrity or security.

For Python, developers now can run Python tests with coverage and get rich results in the editor, Microsoft said. To run tests with coverage, users must select the coverage run icon in Test Explorer or “Run with coverage” from any menu that triggers test runs. The Python extension will run coverage by using the pytest-cov plugin if developers are using pytest, or by using coverage.py if using unittest. Once the coverage is complete, lines are highlighted in the editor for line-level coverage. The Python extension also has added a default problem matcher, simplifying issue tracking in Python code and providing more contextual feedback.

The Source Control Graph in Visual Studio Code 1.94 features a new history item reference picker in the view title, allowing developers to use the reference picker to filter the history items shown in the graph to a different branch or to view multiple branches. The Source Control Graph also expands the list of actions available in the context menu for source control history items. Actions have been added to create a new branch/tag from a history item, cherry-pick a history item, and check out an item.

Elsewhere in Visual Studio Code 1.94:

Additionally, it also has a separate tool, SAP Data Lake Builder, that can be used to ingest data from SAP. Other specific data ingesting tools on offer include BryteFlow for Oracle, BryteFlow for SQL, BryteFLow for SQL Server, BryteFlow for PostgreSQL, and integrations with Databricks, Teradata, Google BigQuery, and Apache Kafka.

What effect will the acquisition have?

BryteFLow’s existing customers may have to look elsewhere for help with data integration if they use databases other than SingleStoreDB: “Our number one priority is to integrate BryteFlow into SingleStore and bring value to our customers through SingleConnect. We have no plan to sell BryteFlow independently at this time, apart from some special cases,” SingleStore CEO Raj Verma said via email.

But there will be opportunities for SingleStore customers, said Duncan Van Kouteren, research analyst at Nucleus Research. “The acquisition will enable customers to integrate data from various sources while maintaining real-time data analytics functionalities by utilizing BryteFlow’s capabilities such as change data capture (CDC),” he said.

“Many developers use the same context repeatedly across multiple API calls when building AI applications, like when making edits to a codebase or having long, multi-turn conversations with a chatbot,” OpenAI explained, adding that the rationale is to reduce token consumption when sending a request to the LLM.

What that means is that when a new request comes in, the LLM checks if some parts of the request are cached. In case it is cached, it uses the cached version, otherwise it runs the full request.

OpenAI’s new prompt caching capability works on the same fundamental principle, which could help developers save on cost and time.

Putting a trusted execution environment on a PC is useful for more than securing AI. It protects sensitive data, adding a new level of protection beyond at rest and in motion: in use. While it does require more work to define and use a VBS Enclave, it’s worth it to have more security with only limited performance impact.

With Windows 11’s memory integrity tools, a VBS Enclave uses Windows’ integral hypervisor to create a new, isolated, high-privilege area of system memory: Virtual Trust Level 1. Most of your code, and Windows itself, continues to run at Virtual Trust Level 0. VTL 1 is used by a secure version of the Windows kernel, with its own isolated user mode. This is where your VBS Enclave runs, as part of an application that appears to cross the boundary between the two zones. In reality, you’re separating off the VTL 1 enclave and using secure channels to communicate with it from the rest of your application in VTL 0.

Using VBS Enclaves in your applications

So how do you build and use VBS Enclaves? First, you’ll need Windows 11 or Windows Server 2019 or later, with VBS enabled. You can do this from the Windows security tool, via a Group Policy, or with Intune to control it via MDM. It’s part of the Memory Integrity service, so you should really be enabling it on all supported devices to help reduce security risks, even if you don’t plan to use VBS Enclaves in your code.

public static class MyListExtensions
{
    public static T GetLastElement(this List list)
    {
        if(list.Count > 0)
            return list[list.Count - 1];
        return default(T);
    }
}

The GetLastElement is an extension method that returns the last element of a list. You can invoke this extension method using the following code snippet.

List integers = new List { 1, 2, 3, 4, 5, 6, 7, 8, 9 };
int element = integers.GetLastElement();
Console.WriteLine(element);

Overloading an extension method in C#

Similar to other methods, you can also overload an extension method. The following code snippet shows how you can overload the Substring method of the string class to return a substring of a string. This overloaded Substring method takes the starting and ending index and a Boolean as parameters. The Boolean denotes if the returned string should be converted to upper case. If you pass true in this parameter when calling the extension method, the returned string will be converted to upper case.