# failed Published articles for failed. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## "Regex for Rows": Simplifying Pattern Detection in SQL with MATCH\_RECOGNIZE DevFeed: ["Regex for Rows": Simplifying Pattern Detection in SQL with MATCH\_RECOGNIZE]() Original publisher: [Read original article]() Author: Kent Marten; Sergei Fedorov Published: 2026-09-16T17:14:05Z Content type: tutorial Language: en Sources: [Databricks]() Topics: [SQL](), [databricks](), [Cybersecurity](), [Security & Privacy]() Tags: [count](), [cybersecurity](), [databricks](), [failed](), [false-positives](), [functions](), [login](), [partition](), [product](), [real-time](), [regex](), [sql](), [window-functions]() ### AI overview This tutorial explains how Databricks supports SQL MATCH_RECOGNIZE for detecting ordered event patterns. It shows how the clause can simplify sequence detection, including identifying repeated login failures followed by a successful login, compared with complex SQL queries and window functions. ### Source excerpt Imagine you work in cybersecurity and you have a table that tracks login attempts... ## How Split Brain Happens in Distributed Databases and How It Gets Fixed DevFeed: [How Split Brain Happens in Distributed Databases and How It Gets Fixed]() Original publisher: [Read original article]() Published: 2026-03-31T00:00:00Z Content type: tutorial Language: en Sources: [Gaurav Sarma's Blog]() Topics: [Databases](), [Network](), [Replication](), [CAP theorem]() Tags: [consensus](), [databases](), [distributed](), [failed](), [false-positives](), [partition](), [replication](), [split-brain]() ### AI overview This tutorial explains how split brain occurs in distributed databases when a network partition causes multiple nodes to become primary and accept conflicting writes. It discusses why timeout-based failure detection can create false positives and introduces the distributed consensus complexity motivated by this failure mode. ### Source excerpt . [How Split Brain Happens in Distributed Databases and How It Gets Fixed](split-brain-in-distributed-databases-cover... ## Debugging an HTTP streaming issue affecting browser and node-fetch requests behind Cloudflare DevFeed: [Debugging an HTTP streaming issue affecting browser and node-fetch requests behind Cloudflare]() Original publisher: [Read original article]() Author: Nick Khami Published: 2025-08-01T00:00:00Z Content type: article Language: en Sources: [Mintlify Blog]() Topics: [Streaming](), [HTTP](), [debugging](), [Cloudflare](), [fetch]() Tags: [cloudflare](), [curl](), [debugging](), [engineering](), [failed](), [fetch](), [http](), [postman](), [streaming]() ### AI overview This article describes an HTTP response streaming failure at Mintlify: cURL and Postman worked, while node-fetch and browser fetch failed. The investigation identified Cloudflare's automatic compression settings as the cause, and disabling compression resolved the issue. ### Source excerpt We recently encountered a frustrating issue with HTTP response streaming at Mintlify. Our system uses the AI SDK with the Node stream API to forward streams, and suddenly things stopped working properly. The symptoms were confusing: streaming worked perfectly with cURL and Postman, but failed completely with node-fetch and browser fetch. ## SFTP Upload Failures in a Financial Institution's Daily Account Transfer Process DevFeed: [SFTP Upload Failures in a Financial Institution's Daily Account Transfer Process]() Original publisher: [Read original article]() Author: Angie Byron Published: 2024-10-09T16:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Transactions](), [Server](), [Network](), [file](), [Database](), [account](), [Software]() Tags: [account](), [community](), [database](), [failed](), [file](), [financial](), [network](), [server](), [sftp](), [transactions]() ### AI overview A fictional story illustrates a financial institution's real-world migration of its daily sweep process to Temporal. The institution used SFTP to exchange account balances and transfers, but frequent upload and download failures, overloaded servers, and database-load-related query failures regularly required employee intervention. ### Source excerpt The bank on the edge of town was haunted - or at least, that's what folks often said. ## Workflow visualization with Temporal DevFeed: [Workflow visualization with Temporal]() Original publisher: [Read original article]() Author: Alex Tideman Published: 2023-10-10T13:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [ui](), [Front end](), [Cloud](), [Users]() Tags: [events](), [failed](), [filter](), [flow](), [product-news](), [retry](), [visualization](), [workflow](), [zoom]() ### AI overview Temporal introduces a Timeline view in its UI for visualizing workflow events over time. The view uses event groups, spans, points, colors, retry indicators, and filtering and zoom controls to help users understand workflow execution, timing, outcomes, and parallelism. ### Source excerpt See Temporal's new Timeline view for visualizing workflow events, making it easier to track and manage complex workflows with enhanced filtering and navigation. ## Robust queue job handling in Craft CMS DevFeed: [Robust queue job handling in Craft CMS]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2019-08-03T15:37:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System](), [Job](), [async]() Tags: [async](), [avoid](), [cms](), [craft](), [failed](), [here-s](), [how-to](), [independent](), [insights](), [job](), [jobs](), [long-running](), [queue](), [runner](), [stalled](), [tasks](), [uses](), [using]() ### AI overview This tutorial explains how Craft CMS queues long-running tasks and why its default web-request-based queue execution can leave jobs stalled or failed. It discusses using an independent async queue runner. ### Source excerpt Craft CMS uses queue jobs for long-running tasks. Here's how to avoid stalled or failed queue jobs by using an independent async queue runner ## Word 2010 support - Weekly report - Part 2: Installation (cont.) DevFeed: [Word 2010 support - Weekly report - Part 2: Installation (cont.)]() Original publisher: [Read original article]() Published: 2016-11-20T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Environment Variables](), [configuration](), [Software](), [Framework]() Tags: [environment](), [environment-variables](), [error](), [failed](), [framework](), [free](), [function](), [installation](), [open-source](), [os](), [react](), [reactos](), [report](), [software](), [win32](), [winapi]() ### AI overview This second weekly report examines Word 2010 installation on ReactOS. It describes missing environment variables affecting the OSPPSVC service, a failed MSI action with error 1603, and a workaround that allowed installation to finish while leaving the underlying failure unresolved. ### Source excerpt In this second report I continue my investigations on the Word 2010 installation. Last time we saw that our services (and in particular the "Office Software Protection Platform" OSPPSVC service) were started without a complete environment block, and as a result some needed environment variables were missing, causing e.g. OSPPSVC to fail opening some of its files. We now analyse what happens after my local fix (NOTE: I have not committed the fix yet, as I validate it in my local installation first). ## Re-adding failed drive in mdadm DevFeed: [Re-adding failed drive in mdadm]() Original publisher: [Read original article]() Author: Tom Published: 2013-12-12T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Mdadm](), [DRIVE]() Tags: [array](), [automatically](), [failed](), [i](), [issue](), [linux](), [mdadm](), [raid]() ### AI overview A practical account of re-adding a previously failed drive to an mdadm RAID5 array after a hot spare had rebuilt the array. The author reports testing the drive, adding it as a spare, failing the slower replacement drive, removing it, and re-adding the tested drive. ### Source excerpt Yesterday I have problem with fglrx witch cause ugly system reset. After that, one of my drives was marked as failed in RAID5 array. Hotspare was automatically used to rebuild array. But this hotspare is the oldest and slowest drive I've got... After rebuild I've tested failed drive and it was fine - no bad block, no any other issue - so I wanted it running back in array. What I do: ## Contract Awarded to Mike Nordell DevFeed: [Contract Awarded to Mike Nordell]() Original publisher: [Read original article]() Published: 2012-09-12T00:00:00Z Content type: release Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Development](), [Windows]() Tags: [announce](), [completion](), [crash](), [developer](), [development](), [exception](), [failed](), [free](), [graphics](), [http](), [job](), [open-source](), [os](), [react](), [reactos](), [tests](), [win32](), [winapi]() ### AI overview The ReactOS Project announced a community-funded development contract for former contributor Mike Nordell. He will investigate and try to fix crashing or canceled tests, then work on failed tests, with an initial focus on listed gdiplus, kernel32, kmtest, mshtml, ntdll, qmgr, and wininet tests. ### Source excerpt The ReactOS Project is delighted to announce another development contract funded by community donations. Mike Nordell was a previous ReactOS developer that went on sabbatical but continued to drop in to check on the project from time to time. As such, he has considerable experience developing ReactOS and extensive knowledge about the Windows NT architecture. As many people are aware of, ReactOS has a large test suite that checks to see whether specific functionality is working or not. ## fsck.ext4 - Błąd podczas przydzielania struktury icount: Memory allocation failed DevFeed: [fsck.ext4 - Błąd podczas przydzielania struktury icount: Memory allocation failed]() Original publisher: [Read original article]() Author: Tom Published: 2011-09-21T00:00:00Z Content type: tutorial Language: pl Sources: [Tomasz Gągor]() Topics: [Ext4](), [screen]() Tags: [ext4](), [failed](), [fsck](), [linux](), [memory](), [screen]() ### AI overview A Polish technical article describes an fsck.ext4 failure with "Memory allocation failed" while checking an approximately 14 TB filesystem containing hundreds of millions of files and many hard links. It explains the memory constraints involved and suggests using a temporary directory for inode and directory metadata, with fsck run from screen to monitor progress. ### Source excerpt Miałem ostatnio dziwną przygodę: pewien serwer do backupu gdzie ląduje dużo małych plików i dodatkowo tworzonych jest sporo hardlinków zaliczył pada. Co prawda starałem się go grzecznie położyć z pomocą Magic SysRq ale ponieważ nie wiedziałem co było przyczyną awarii fsck wydawał się wskazany. Podczas próby uruchomienia fsck.ext4 na systemie plików o rozmiarze ok 14TB z kilkuset milionami plików po kilkudziesięciu sekundach otrzymywałem komunikat: Błąd podczas przydzielania struktury icount: Memory allocation failed