How a 295-character database field crashed an entire static site build

·1 views

Russian apartment listings site podbor-minuta.ru experienced a full static build failure when a scraped property record contained a 295-character sentence in a field meant to store a neighbourhood name. The page generator used this oversized value to construct a URL path, and the static site builder (Vike) attempted to create a corresponding directory on disk, exceeding the 255-byte filesystem limit for folder names. The bug went undetected for some time because Docker layer caching skipped the affected build step and local builds rarely fetched the corrupted record due to API timeouts, making it visible only in clean CI runs. Developers fixed the issue by adding a segment-length guard in the URL generator — rejecting any path segment over 120 characters — and by filtering out description-like values at the database query level. The incident highlighted that any uncontrolled external data can eventually become a filesystem path, and a single bad record should never be allowed to bring down an entire build.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Gooseworks, YC W23 Startup, Seeks Founding Engineer

Gooseworks, a startup that participated in Y Combinator's Winter 2023 batch, is actively recruiting for a Founding Builder or Engineer role. The position was listed on Y Combinator's job board, signaling an early-stage hiring push. As a founding engineer, the hire would likely play a pivotal role in shaping the company's core product and technical direction. The listing had no public comments or engagement points at the time of posting.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

How One Developer Replaced ChatGPT, Claude, and Perplexity With a Single AI Orchestrator

A developer cancelled paid subscriptions to ChatGPT Pro, Claude Pro, and Perplexity Pro, replacing them with a single tool called Littlebird that acts as an orchestration layer across AI models. Rather than logging into multiple platforms separately, the developer uses Littlebird as a unified front end that routes tasks to appropriate underlying models based on context. The setup is anchored by a Mac Studio, which serves as a local hub storing files, notes, and project data that Littlebird draws on when sending context to external AI tools. Results returned by those external models are written back to the Mac Studio, allowing Littlebird to maintain continuity across conversations without relying on any single vendor's storage. The approach is framed as a way to reduce subscription costs and tool sprawl while keeping data and workflows under personal control.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How ABM Landing Pages Outperform Generic Homepages in Maritime Cybersecurity

Account-based marketing (ABM) landing pages require a fundamentally different approach than generic homepages, particularly in niche industrial sectors like maritime cybersecurity. Using Blackhole Networks as a case study, the analysis highlights how generic homepages fail ABM traffic by lacking focused lead capture, relevant social proof, and sector-specific copy. Rather than directing targeted visitors to a broad homepage, effective ABM pages function more like product pages with a single clear call to action tailored to roles such as port IT leads or fleet security officers. Social proof on these pages should go beyond logo strips, referencing outcomes specific to maritime environments like OT networks, regulatory compliance, and incident response. The piece argues that copy must move away from generic terms like 'digital transformation' and instead reflect the precise language and risk concerns of the maritime sector.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Blogger audits 200 posts, finds three hidden bugs in headings, CSS, and mobile layout

A developer running a long-standing technical blog paused new publishing to conduct a full audit of roughly 200 existing posts, uncovering three structural issues invisible on their own screen. Multiple posts contained conflicting H1 headings caused by the blog theme and post body editor rendering titles independently, resulting in eight duplicate top-level headings across five posts. A screen-reader label on the site's search box was marked with a CSS class intended to visually hide it, but the corresponding style rule was missing entirely, causing layout breakage on narrow mobile viewports. The correct fix used a clip-based CSS pattern to keep the label accessible to assistive technology while removing it from visual display — rather than simply deleting the element. Each fix was deployed as a separate versioned theme update with a recorded checksum, allowing for clean rollback if needed.

0 comments Read more at DEV Community