<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>ITANU Magazine: Software</title><link>https://itanu.org/magazine/desk/software/</link><description>Technology news in nine languages, three editions a day. Every story names its sources and is checked against them.</description><language>en</language><lastBuildDate>Mon, 16 Nov 2026 17:37:51 GMT</lastBuildDate><atom:link href="https://itanu.org/magazine/desk/software/feed.xml" rel="self" type="application/rss+xml"/><item><title>Rust turns on parallel compiler frontend by default in nightly builds</title><link>https://itanu.org/magazine/rust-parallel-compiler-frontend-nightly-default-f6qmkkta/</link><guid isPermaLink="true">https://itanu.org/magazine/rust-parallel-compiler-frontend-nightly-default-f6qmkkta/</guid><pubDate>Mon, 16 Nov 2026 17:37:51 GMT</pubDate><dc:creator>ITANU Magazine newsroom</dc:creator><category>Software</category><description>Rust&apos;s Compiler Team says nightly builds now run the frontend, which does type checking and borrow checking, in parallel by default. It wants to find remaining issues before it stabilizes the feature.</description><content:encoded>&lt;h3&gt;Key points&lt;/h3&gt;&lt;ul&gt;&lt;li&gt;Rust&amp;apos;s Compiler Team says the parallel frontend has been on by default in nightly builds since nightly-2026-11-14.&lt;/li&gt;&lt;li&gt;The frontend, which does type checking and borrow checking, has run on a single thread by default; parallel mode has been an opt-in on nightly for three years.&lt;/li&gt;&lt;li&gt;The team will watch GitHub and Zulip for reported issues over the next few months and plans to stabilize the feature once it is confident it works well.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;Rust&amp;apos;s Compiler Team announced on 16 November 2026 that the Rust compiler&amp;apos;s parallel frontend is now on by default in the nightly channel. The team says the aim is to find any remaining problems before the feature is stabilized. Jakub Beránek wrote the post on behalf of the Compiler Team.&lt;/p&gt;&lt;p&gt;According to the team, the compiler has used multiple threads for a long time in its backend, which is built on LLVM. The frontend, which covers type checking and borrow checking, has run sequentially on one thread, and the team says this limits the compiler&amp;apos;s performance.&lt;/p&gt;&lt;p&gt;The post says the frontend has been able to run in parallel for a long time, but various issues kept it from being the default. Three years ago the team made the parallel mode an opt-in on nightly, with a plan to stabilize it in 2024, a goal it did not reach. Last year Vadim Petrochenkov and several other contributors began a coordinated push that fixed many long-standing issues and improved performance, according to the team. The new default has applied since nightly-2026-11-14.&lt;/p&gt;&lt;p&gt;The team says it especially wants to hear about compiler crashes and about binaries that cannot be reproduced when the parallel frontend is enabled. It also says further performance gains may be possible, because work so far has focused on correctness rather than speed tuning.&lt;/p&gt;&lt;p&gt;Over the next few months, the team says it will watch GitHub and Zulip for reports about the parallel frontend. If no major issues appear and it is confident the feature works well, it intends to stabilize it.&lt;/p&gt;&lt;h3&gt;Sources&lt;/h3&gt;&lt;ol&gt;&lt;li&gt;&lt;a href=&quot;https://blog.rust-lang.org/2026/11/16/enabling-parallel-frontend-on-nightly&quot;&gt;Enabling the parallel frontend on nightly&lt;/a&gt;, Rust Blog&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;ITANU’s newsroom system produced this article with AI and checked it against the sources listed above.&lt;/p&gt;</content:encoded></item><item><title>Microsoft blames months-old bug for global Microsoft 365 outage</title><link>https://itanu.org/magazine/microsoft-months-old-bug-microsoft-365-outage-nkrptpis/</link><guid isPermaLink="true">https://itanu.org/magazine/microsoft-months-old-bug-microsoft-365-outage-nkrptpis/</guid><pubDate>Mon, 16 Nov 2026 17:11:05 GMT</pubDate><dc:creator>ITANU Magazine newsroom</dc:creator><category>Software</category><description>A defect shipped in July to Microsoft 365 networking gateway servers combined with extra Teams traffic and reduced capacity. At the worst point, more than 80% of servers stopped responding.</description><content:encoded>&lt;figure&gt;&lt;img src=&quot;https://itanu.org/assets/magazine-img-794e556d61341ab2-960.jpg&quot; width=&quot;1600&quot; height=&quot;1066&quot; alt=&quot;Aerial view of the Microsoft headquarters campus in Redmond, Washington, with construction cranes and Lake Sammamish beyond.&quot;&gt;&lt;figcaption&gt;File photo: Microsoft headquarters campus redevelopment in Redmond, Washington, 2021 · Atomic Taco / Wikimedia Commons · CC BY-SA 2.0&lt;/figcaption&gt;&lt;/figure&gt;&lt;h3&gt;Key points&lt;/h3&gt;&lt;ul&gt;&lt;li&gt;Microsoft says a bug in a July update to Microsoft 365 networking gateway servers caused the nearly 24-hour outage on 12 November.&lt;/li&gt;&lt;li&gt;Extra traffic after a Teams failover and reduced server capacity also contributed, according to a preliminary report.&lt;/li&gt;&lt;li&gt;At the lowest point, more than 80% of servers were unresponsive.&lt;/li&gt;&lt;li&gt;A final post-incident report is expected later this week.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;Microsoft says a defect in an update it released in July for its Microsoft 365 networking gateway servers was behind the nearly 24-hour worldwide outage on 12 November, BleepingComputer reported.&lt;/p&gt;&lt;p&gt;The disruption started at 11:20 ET on Thursday 12 November and ended at 11:10 ET the next day, when Microsoft confirmed that services were fully restored. Outlook, Exchange Online, Teams and Copilot were affected, and users lost access to email or faced lengthy waits for messages to arrive.&lt;/p&gt;&lt;p&gt;In an initial post-incident report shared through the Microsoft 365 Admin Center, the company named three contributing problems: the previously unnoticed bug, extra traffic following a Teams failover, and reduced server capacity. The update had run for more than three months without trouble, but under certain traffic patterns the bug could overload servers until they stopped responding.&lt;/p&gt;&lt;p&gt;Microsoft executive Charles Lamanna described the bug as a &amp;quot;latent defect&amp;quot; that caused lock contention, which stopped machines from responding. Lock contention happens when several processes wait on the same lock, so work stalls until it is released. Lamanna said the faulty code came from a fix written specifically for the gateway servers, and that neither the fix nor the underlying defect applies to wider Windows deployments. He said Microsoft first observed the issue during an earlier Microsoft 365 update in July 2026.&lt;/p&gt;&lt;p&gt;Petri reports that the defect lay dormant since July 2026 and escaped testing because Microsoft&amp;apos;s validation environments mostly used older hardware, while the bug was more likely to surface on newer servers with higher core counts under specific workloads. Microsoft had recently moved Teams traffic onto the gateways that also serve Exchange Online, and a separate issue had already cut available capacity.&lt;/p&gt;&lt;p&gt;Automated systems then shifted traffic to servers that were still healthy, where the same defect was triggered, according to Petri. Lamanna said the load was spread over ever fewer servers, and within less than two hours the defect had been hit across the fleet; at its lowest point, more than 80% of servers were unresponsive.&lt;/p&gt;&lt;blockquote&gt;&lt;p&gt;We are deeply sorry for the impact to all our customers&lt;/p&gt;&lt;footer&gt;Charles Lamanna, Microsoft&lt;/footer&gt;&lt;/blockquote&gt;&lt;p&gt;Microsoft says its investigation is continuing and that it expects to publish a final post-incident report later this week.&lt;/p&gt;&lt;h3&gt;Sources&lt;/h3&gt;&lt;ol&gt;&lt;li&gt;&lt;a href=&quot;https://bleepingcomputer.com/news/microsoft/microsoft-says-months-old-bug-caused-global-microsoft-365-outage&quot;&gt;Microsoft says months-old bug caused global Microsoft 365 outage&lt;/a&gt;, BleepingComputer&lt;/li&gt;&lt;li&gt;&lt;a href=&quot;https://www.itpro.com/software/microsoft/microsoft-365-outage-company-exec-lifts-lid-on-the-cascading-failure-that-caused-lengthy-disruption&quot;&gt;Microsoft 365 outage: Company exec lifts lid on the &amp;apos;cascading failure&amp;apos; that caused lengthy disruption&lt;/a&gt;, ITPro&lt;/li&gt;&lt;li&gt;&lt;a href=&quot;https://petri.com/microsoft-explains-microsoft-365-outage/&quot;&gt;Microsoft Explains Causes of Microsoft 365 Outage&lt;/a&gt;, Petri&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;ITANU’s newsroom system produced this article with AI and checked it against the sources listed above.&lt;/p&gt;</content:encoded><media:content url="https://itanu.org/assets/magazine-img-794e556d61341ab2-1600.jpg" medium="image" type="image/jpeg" width="1600" height="1066"><media:credit>Atomic Taco / Wikimedia Commons</media:credit><media:description>Aerial view of the Microsoft headquarters campus in Redmond, Washington, with construction cranes and Lake Sammamish beyond.</media:description></media:content></item></channel></rss>
