Fix
We track 23 posts about Fix from 18 engineering blogs. Most active: Google Online Security, Red Hat, Robin Wilson. Latest post: Oct 7, 2026.
Companies writing about Fix
Recent posts
Refactoring The-Internet: Fork, Fix, Farewell to Heroku and hello to Render! (opens on the source site)
With this blog post, we will be taking Dave Haeffner's The-Internet, https://the-internet.herokuapp.com/, a ten-year old web app test site, fork it, investigate using Google AI how to modernize the server architecture, and port it over to a new home at Render.com. Spoilers: The original version, but with updated Ruby architecture: https://the-internet-8uaj.onrender.com/ (takes a minute to spin up the environment) It finally happened. Dave Haefner's The-Internet, a test site I have been using ever since I first started blogging, is now failing to load half the time. It's not the test site's…
Why your non-root container dropped its capabilities (and how to fix it) (opens on the source site)
Red Hat ·
You are a platform engineer running Red Hat OpenShift. A development team runs a monitoring sidecar as a non-root user that needs to perform ICMP ping health checks. They need CAP_NET_RAW, the capability required for raw socket access. Straightforward enough, and the security context constraints (SCC) is configured to allow the capability: The post Why your non-root container dropped its capabilities (and how to fix it) appeared first on Red Hat Developer.
Next.js Chunk Load Error: How to Fix Production Failures (opens on the source site)
Diagnose and resolve intermittent Next.js App Router ChunkLoadError issues in production, from deploy skew and proxy matchers to CDN caching and error boundaries. Continue reading Next.js Chunk Load Error: How to Fix Production Failures on SitePoint.
How to Test and Fix Voice AI Agent Prompts with Twilio Conversation Relay and Cekura (opens on the source site)
Twilio ·
Build and test an AI voice agent using Twilio Conversation Relay and Cekura. Write metrics, run evaluations, and fix prompt bugs.
Why your Kafka topic ignores retention.ms (and how to fix it) (opens on the source site)
Red Hat ·
A customer opened a support case with a deceptively simple complaint: a Kafka topic was configured with a 12-hour retention (retention.ms), yet messages produced on July 24 were still readable 4 days later, on July 28. Nothing was broken. The broker logged no errors. The retention policy was working as designed, but the segment layout and continuous write pattern delayed when the old records could actually be removed. The post Why your Kafka topic ignores retention.ms (and how to fix it) appeared first on Red Hat Developer.
How to fix a weird pandas and pyarrow issue with BirdNetPi (opens on the source site)
Summary: If you get Python crashing immediately in BirdNetPi, try uninstalling the pyarrow Python package. I’ve got a BirdNetPi set up at home. This is a bit of software that runs on a Raspberry Pi and listens on a microphone (I’ve mounted mine on the outside of an upstairs window, using a 3D printed mount/cover […]
Benchmarking Secure-and-Functional Remediation and How Snyk Agent Fix Lifts Frontier-Model Fix Rates by over 14% (opens on the source site)
Snyk ·
A benchmark of secure, functional vulnerability fixes across JavaScript, Java, and Python shows Snyk Intelligence helps frontier models break past a 72–75% performance plateau.
No Dumb Questions: What is the AI bottleneck? How does context engineering fix it? (opens on the source site)
In this No Dumb Questions, Stack's Director of Data Science Michael Foree teaches Phoebe about AI context, context engineering, and what she can do to become a better context engineer.
Flaky Test API Now GA, New Auto-Fix Skill, Skill Quality Improvements (opens on the source site)
You can now identify your flakiest tests through the API and have an AI agent fix them, at a cost of around $1 to $1.50 per fix. What Shipped Flaky Test Data in the API (Generally Available) Flaky test data is now accessible programmatically through the sem-ai API. The API surfaces tests ranked by disruption […] The post Flaky Test API Now GA, New Auto-Fix Skill, Skill Quality Improvements appeared first on Semaphore.
Code is the easy part, or how we refactored half the business to fix a janky script (opens on the source site)
This is a classic startup war story: Someone had built a leaky rowboat. It worked! Then we started flying the rowboat as a Cessna. What we needed was an aircraft carrier.
Linux Troubleshooting: These 4 Steps Will Fix 99% of Errors (opens on the source site)
I’ll admit, I hesitated a bit before writing this post. The whole point of this linuxblog.io and linuxcommunity.io forum is to bring together like-minded Linux users and professionals so we can troubleshoot, share ideas, and learn from one another.Continue reading...
Testing Java Memory Management with Chronicle-FIX using AI (opens on the source site)
While I am sceptical of using AI for release code, it has plenty of uses that previously weren’t practical, such as determining how easy your software is to use. If an AI can “figure it out” with a few hints, then you are on the right track. For me, the value of AI is what you learn using it. For more Techincal Information on Chronicle-FIX What AI Does Well and What It Doesn’t Claude and Codex are effective for producing idiomatic code; for low-latency code, it needs a significant body of example code. In this case, it was able to utilise sample code for benchmarks. If it was being used to…
Testing Java Memory Management with Chronicle-FIX using AI (opens on the source site)
While I am sceptical of using AI for release code, it has plenty of uses that previously weren’t practical, such as determining how easy your software is to use. If an AI can “figure it out” with a few hints, then you are on the right track. For me, the value of AI is what you learn using it. For more Techincal Information on Chronicle-FIX What AI Does Well and What It Doesn’t Claude and Codex are effective for producing idiomatic code; for low-latency code, it needs a significant body of example code. In this case, it was able to utilise sample code for benchmarks. If it was being used to…
Just fix their PR (opens on the source site)
You know what's better than a code review comment? A fix. Lately we've been dealing with an absolute onslaught of pull requests. Feels like half my days go to reviewing code, half to management, and half to writing code. Yes that's too many halfs. See I wasn't even exaggerating (thought I was). 53% of my contributions are code review 🫠 Part of this is because AI now writes 97% of my code. I review that and like to leave the bot comments for things to fix. Feels natural and I don't have to learn a new workflow. Oh a human wrote this code? Here's a comment, please fix. Oh a bot wrote this…
Putting the Tech in Fintech: How We Use FIX to Execute Trades at Scale (opens on the source site)
At Wealthfront, the “tech” in financial technology isn’t just a buzzword—it’s the foundation of everything we build. Beneath the intuitive frontend our clients interact with lies a complex ecosystem of distributed systems. One of the most critical pieces of that backend architecture is the engine that enables us to route massive volumes of trades efficiently. ... Read more
//go:fix inline and the source-level inliner (opens on the source site)
Go ·
The Go Blog //go:fix inline and the source-level inliner Alan Donovan 10 March 2026 Go 1.26 contains an all-new implementation of the go fix subcommand, designed to help you keep your Go code up-to-date and modern. For an introduction, start by reading our recent post on the topic. In this post, we’ll look at one particular feature, the source-level inliner. While go fix has several bespoke modernizers for specific new language and library features, the source-level inliner is the first fruit of our efforts to provide “self-service” modernizers and analyzers. It enables any package author to…
Using go fix to modernize Go code (opens on the source site)
Go ·
The Go Blog Using go fix to modernize Go code Alan Donovan 17 February 2026 The 1.26 release of Go this month includes a completely rewritten go fix subcommand. Go fix uses a suite of algorithms to identify opportunities to improve your code, often by taking advantage of more modern features of the language and library. In this post, we’ll first show you how to use go fix to modernize your Go codebase. Then in the second section we’ll dive into the infrastructure behind it and how it is evolving. Finally, we’ll present the theme of “self-service” analysis tools to help module maintainers and…
How to fix the NBA Draft (opens on the source site)
I read this and then had trouble finding it for a year, I'm writing about it so I have a way to find it... The proposal here is so obviously correct that it's shocking it doesn't come up more often when people discuss the NBA Draft... basically the idea is that you assign a high […]
How to fix osm2pgrouting error ‘relation “__waysXXXX” does not exist’ and speed up the import (opens on the source site)
I don’t seem to have time or energy for long posts these days, but here’s another quick post which might save you some time and frustration. Recently, I’ve been trying to import OpenStreetMap data into a PostGIS database to use with pgRouting. I wanted to import data for the whole of England – which has […]
Rust in Android: move fast and fix things (opens on the source site)
Posted by Jeff Vander Stoep, Android Last year, we wrote about why a memory safety strategy that focuses on vulnerability prevention in new code quickly yields durable and compounding gains. This year we look at how this approach isn’t just fixing things, but helping us move faster. The 2025 data continues to validate the approach, with memory safety vulnerabilities falling below 20% of total vulnerabilities for the first time. Updated data for 2025. This data covers first-party and third-party (open source) code changes to the Android platform across C, C++, Java, Kotlin, and Rust. This post…
Rust in Android: move fast and fix things (opens on the source site)
Posted by Jeff Vander Stoep, Android Last year, we wrote about why a memory safety strategy that focuses on vulnerability prevention in new code quickly yields durable and compounding gains. This year we look at how this approach isn’t just fixing things, but helping us move faster. The 2025 data continues to validate the approach, with memory safety vulnerabilities falling below 20% of total vulnerabilities for the first time. Updated data for 2025. This data covers first-party and third-party (open source) code changes to the Android platform across C, C++, Java, Kotlin, and Rust. This post…
How to Fix Any Bug (opens on the source site)
I’ve been vibecoding a little app, and a few days ago I ran into a bug. The bug went something like this. Imagine a route in a webapp. That route shows a sequence of steps—essentially, cards. Each card has a button that scrolls down to the next card. Everything works great. However, as soon as I tried to also call the server from that button, scrolling would no longer work. It would jitter and break. So, adding a remote call somehow broke scrolling. I wasn’t sure what’s causing the bug. Clearly, the newly added remote server call (which I was doing via React Router actions) was somehow…
CSS fix to prevent orphan icons dropping to a new line (opens on the source site)
When an HTML element becomes too narrow, its content starts to wrap into multiple lines. This is intended behavior and works well in many cases. However, for short text, it doesn't look great when the last word or icon drops to the next line, becoming an orphan. For example, you might see something like this: Click here for more info It doesn't look great when the icon is left alone on its own row. Luckily, there's a simple CSS solution. Solution # Only thing we need to add is a single line of CSS: text-wrap: balance; This property tells the browser to wrap the text in a way that best…
Related topics
This page is generated automatically from the engineering blogs we follow. Every post links to its source, where it was published. See all sources.