# make Published articles for make. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Efficient Bulk Hash Insertion with Redis 8.10's HIMPORT DevFeed: [Efficient Bulk Hash Insertion with Redis 8.10's HIMPORT]() Original publisher: [Read original article]() Author: David Maier Published: 2026-08-24T00:00:00Z Content type: article Language: en Sources: [Redis Blog]() Topics: [Redis](), [Ruby](), [Code](), [Command-line interface]() Tags: [article](), [cli](), [code](), [make](), [redis](), [ruby](), [tech]() ### AI overview This article explains how to use Redis 8.10's HIMPORT command with redis-rb to perform more efficient bulk hash insertion in Ruby. It covers connection setup, prepared field sets, automatic preparation, reconnection behavior, the demo CLI, and pipelined imports. ### Source excerpt I'm not a Ruby developer, and my code samples might make that clear. However, there are two reasons I'm using Ruby for the examples in this article: A new release of redis-rb. Its support for a new Redis command: HIMPORT. Getting started Establish... ## Introducing Isolated Projects DevFeed: [Introducing Isolated Projects]() Original publisher: [Read original article]() Author: Alex Semin Published: 2026-08-06T04:00:00Z Content type: release Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Optimization](), [configuration](), [releases](), [Command-line interface]() Tags: [configuration](), [feature](), [gradle](), [make](), [optimization](), [releases]() ### AI overview Gradle introduces Isolated Projects, a performance feature that isolates projects during the configuration phase so they can be processed independently and concurrently. In Gradle 9.7.0, the feature moves from experimental to incubating, with current gains primarily from parallel project configuration. ### Source excerpt Isolated Projects is a Gradle performance feature that speeds up the configuration phase. When the feature is enabled, each project in a build becomes "isolated" from others via boundaries that cannot be crossed. With this guarantee, Gradle can safely operate on each project independently and concurrently. This enables greater utilization of machine resources at configuration time and sets the stage for future caching optimizations. In the latest Gradle 9.7.0 release, Isolated Projects graduates from experimental to incubating. We believe Isolated Projects is the future of Gradle, and we intend to stabilize it and eventually make it the default. In this Gradle version, most of the performance gains come from parallel project configuration. It is not the only optimization these isolation constraints make possible, just the first to ship. It provides speedups across practically all scenarios, including CLI invocations and IDE sync. We invite everyone to try it and share feedback. Adopting Isolated Projects Isolated Projects ships with an extensive guide to adopting it. If you've already upgraded to Configuration Cache, which is a prerequisite, then the process should be familiar. You can enable the feature either via the --isolated-projects command-line flag or with the property org.gradle.isolated-projects=true. It must be enabled with a property to take effect for IDE sync. # gradle.properties org.gradle.isolated-projects=true When Isolated Projects is enabled, it takes precedence over other performance features. You can learn more about how it interacts with other features in this section of the documentation. Since the feature introduces new isolation constraints, you might have to adjust your build logic or upgrade community plugins to take advantage of it. For correctness, Gradle will fail immediately upon encountering the first constraint violation and report the error: You can use the Diagnostics mode to discover many constraint violations at once. All the rep ## libosmocore - libosmocore 1.14.1 released DevFeed: [libosmocore - libosmocore 1.14.1 released]() Original publisher: [Read original article]() Author: osmith Published: 2026-07-22T10:37:33Z Content type: release Language: en Sources: [Open Source Mobile Communications: News]() Topics: [changelog](), [IO](), [cpu](), [scheduling](), [make]() Tags: [2026](), [bug](), [changelog](), [cpu](), [io](), [issue](), [make](), [scheduling](), [tracker]() ### AI overview libosmocore 1.14.1 has been released with fixes to I/O queue handling, CPU scheduling initialization and platform-dependent scheduling support, utility issues, and a missing crypto header in the build configuration. ### Source excerpt Today we've released libosmocore 1.14.1. The changelog over 1.14.0 is as follows: libosmocore (1.14.1) unstable; urgency=medium [ Vadim Yanitskiy ] * osmo_io: iofd_txqueue_dequeue(): fix double next->io_len decrement [ Timur Davydov ] * vty: fix osmo_cpu_sched_vty_init() prototype * vty: make CPU scheduling optional based on platform support [ Oliver Smith ] * utils: fix typos * utils/gsmtap-logsend: close infile before exit [ Alexander Couzens ] * gsm/Makefile.am: add missing kdf/crypto.h -- Oliver Smith Wed, 22 Jul 2026 11:30:55 +0200 ## Issue no.17: Build with joy DevFeed: [Issue no.17: Build with joy]() Original publisher: [Read original article]() Author: Figma Published: 2026-07-02T23:05:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [Canvas](), [Software]() Tags: [community](), [design](), [figma](), [make](), [software](), [vision](), [workflows]() ### AI overview Figma's Config 2026 magazine, "Build with joy," explores how teams evolve workflows, develop creative taste, use motion and color, and imagine the future of software. It also recaps Config launches and introduces a new Figma swag collection. ### Source excerpt The way we make things is changing, but why we make them stays constant--the thrill of seeing a vision come to life. ## Chainguard brings first-party RHEL 9 and RHEL 10 RPM support to Chainguard OS, joins FINOS DevFeed: [Chainguard brings first-party RHEL 9 and RHEL 10 RPM support to Chainguard OS, joins FINOS]() Original publisher: [Read original article]() Published: 2026-05-11T00:00:00Z Content type: news Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [chainguard os](), [chainguard containers](), [Security](), [Critical Infrastructure](), [Package Management](), [Open Source](), [Cloud Native Ecosystem](), [Resilience](), [APK](), [Linux]() Tags: [chainguard](), [chainguard-containers](), [chainguard-finserv](), [chainguard-os](), [cloud](), [cloud-native](), [compatibility](), [compliance](), [container](), [container-images](), [containers](), [critical-infrastructure](), [cve](), [dependencies](), [hardening](), [images](), [linux](), [make](), [mythos](), [open](), [open-source](), [project-glasswing](), [rhel](), [rhel-10](), [rhel-9]() ### AI overview Chainguard announces first-party RHEL 9 and RHEL 10 RPM compatibility for packages in Chainguard Containers built on Chainguard OS. The company also announces that it is joining FINOS to support open source collaboration in financial infrastructure. ### Source excerpt Chainguard adds first-party RHEL 9/10 RPM compatibility and joins FINOS, helping financial institutions modernize securely for the AI-driven threat era. ## Inside Turbopack: Building Faster by Building Less DevFeed: [Inside Turbopack: Building Faster by Building Less]() Original publisher: [Read original article]() Author: Tobias Koppers Published: 2026-01-20T17:00:00Z Content type: article Language: en Sources: [Next.js Blog]() Topics: [Caching](), [Next.js](), [web applications](), [Webpack](), [make](), [Data structures]() Tags: [architecture](), [bugs](), [building](), [cache](), [caching](), [code](), [complexity](), [cpu](), [development](), [make](), [memory](), [next-js](), [performance](), [scale](), [web](), [web-applications]() ### AI overview Turbopack uses fine-grained caching and incremental computation to reduce rebuild work and speed up development for large Next.js applications. The article explains its automatic dependency tracking, research foundations, and contrast with coarse-grained systems such as GNU Make. ### Source excerpt Learn how we built Turbopack with incremental computation to scale development and builds to massive Next.js applications. ## Generating Miniatures for my Frameo Digital Photo Frame DevFeed: [Generating Miniatures for my Frameo Digital Photo Frame]() Original publisher: [Read original article]() Author: Tom Published: 2025-11-28T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [make](), [Software](), [App](), [data](), [Linux](), [Raspberry Pi]() Tags: [app](), [bash](), [camera](), [collection](), [devops](), [digital-photo-frame](), [exiftool](), [files](), [frameo](), [generate](), [go](), [hardware](), [imagemagick](), [linux](), [macos](), [make](), [photo-collection](), [photo-miniatures](), [photos](), [raspberry-pi]() ### AI overview The author describes buying an ARZOPA Frameo digital photo frame and developing a workflow to fit a large photo collection onto its limited storage by generating thumbnails. The workflow uses ImageMagick, ExifTool, parallel processing, and Make on Ubuntu or Debian. ### Source excerpt A story of how I bought a digital photo frame, and how I created a tool to generate miniatures of my photo collection to fit them all on the device. ## 6 winning Figma Makes--and what you can learn from them DevFeed: [6 winning Figma Makes--and what you can learn from them]() Original publisher: [Read original article]() Author: Emma Webster Published: 2025-10-07T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [SVG animations in CSS](), [Code](), [Artificial Intelligence](), [debugging](), [Prompt Engineering]() Tags: [ai](), [animation](), [code](), [creativity](), [debugging](), [figma](), [how-to](), [innovation](), [learn](), [make](), [svg](), [tool]() ### AI overview The article presents six winning Figma Make projects from a global Make-a-thon and extracts lessons for prototyping, product structure, prompting, and iteration. It highlights a frame-by-frame SVG animation tool whose creator used iterative dialogue with AI, explored technical implementation details, and relied on reverting to earlier versions when debugging. ### Source excerpt Winners from our first global Make-a-thon offer insights on how to prototype smarter, structure products better, and push Figma Make further. ## Keep your AGENTS.md in sync -- One Source of Truth for AI Instructions DevFeed: [Keep your AGENTS.md in sync -- One Source of Truth for AI Instructions]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2025-07-03T22:22:12Z Content type: tutorial Language: en Sources: [Kaushik Gopal's Site]() Topics: [AI Development](), [Development](), [Tool]() Tags: [ai-development](), [codex](), [developers](), [maintenance](), [make](), [opencode]() ### AI overview This post describes organizing AI assistant instructions in a single source-of-truth repository. It separates user-level defaults from project-level rules and uses symlinks and a Makefile setup command to share configuration across Claude, Codex, and OpenCode. ### Source excerpt Getting useful results from your AI assistant often comes down to the instructions you give it. Most developers treat that step casually, then wonder why the output is mediocre. One of the simplest ways1 to improve this is to keep one set of master instructions in an AGENTS.md file. In it, you define persistent rules that shape every interaction with the agent. Writing those instructions once is easy enough. Keeping them in sync is the annoying part. If you use more than one tool, things drift fast. So I keep one repo as the source of truth for my AI setup, then wire my tools and projects back to it. This post is the simple version of that setup. Good news Most coding tools have since consolidated around AGENTS.md as the standard. That makes this much simpler than it used to be. I talked about this topic in detail on my AI development podcast: How I organize my AI instructions # I keep my setup at two levels: User-level instructions: my personal defaults that I want available everywhere Project-level instructions: the rules and context that only apply to one repo User level: one source of truth ## I keep my shared AI setup in a single repo. That repo holds the things I want to maintain in one place: AGENTS.md reusable skills/ reusable commands/ compatibility shims like CLAUDE.md Then I wire my local tools back to that repo with one command from the repo's Makefile: make setup That command creates the symlinks for me. I am not updating the same instructions by hand for Claude, Codex, and OpenCode. I edit the shared files once in my repo, and the tools point back to them. At the user level, I keep it direct. The repo is the source of truth, so the tool-specific paths symlink straight to it. For example: ~/.claude/agents -> ~/my-local-directory/aikado/agents ~/.config/opencode/agents -> ~/my-local-directory/aikado/agents So the maintenance story is simple: keep shared defaults in one repo symlink tools back to that repo edit once Project level: thin local scaffolding # ## Using \`make\` to compile C programs (for non-C-programmers) DevFeed: [Using \`make\` to compile C programs (for non-C-programmers)]() Original publisher: [Read original article]() Author: Julia Evans Published: 2025-06-10T00:00:00Z Content type: tutorial Language: en Sources: [Julia Evans]() Topics: [C](), [make](), [Compiler](), [Package manager](), [gcc](), [apt](), [Xcode](), [C++]() Tags: [apt](), [building](), [c](), [c-plus-plus](), [command-line](), [compiler](), [debian](), [dependencies](), [gcc](), [libraries](), [linux](), [mac](), [make](), [packages](), [xcode]() ### AI overview A beginner-oriented guide to compiling C programs from source, covering compiler installation, dependency discovery, and build tools on Ubuntu and macOS. ### Source excerpt I have never been a C programmer but every so often I need to compile a C/C++ program from source. This has been kind of a struggle for me: for a long time, my approach was basically "install the dependencies, run make, if it doesn't work, either try to find a binary someone has compiled or give up". "Hope someone else has compiled it" worked pretty well when I was running Linux but since I've been using a Mac for the last couple of years I've been running into more situations where I have to actually compile programs myself. So let's talk about what you might have to do to compile a C program! I'll use a couple of examples of specific C programs I've compiled and talk about a few things that can go wrong. Here are three programs we'll be talking about compiling: paperjam sqlite qf (a pager you can run to quickly open files from a search with rg -n THING | qf) step 1: install a C compiler This is pretty simple: on an Ubuntu system if I don't already have a C compiler I'll install one with: sudo apt-get install build-essential This installs gcc, g++, and make. The situation on a Mac is more confusing but it's something like "install xcode command line tools". step 2: install the program's dependencies Unlike some newer programming languages, C doesn't have a dependency manager. So if a program has any dependencies, you need to hunt them down yourself. Thankfully because of this, C programmers usually keep their dependencies very minimal and often the dependencies will be available in whatever package manager you're using. There's almost always a section explaining how to get the dependencies in the README, for example in paperjam's README, it says: To compile PaperJam, you need the headers for the libqpdf and libpaper libraries (usually available as libqpdf-dev and libpaper-dev packages). You may need a2x (found in AsciiDoc) for building manual pages. So on a Debian-based system you can install the dependencies like this. sudo apt install -y libqpdf-dev libpaper-dev ## Using if-else Conditionals in a Makefile DevFeed: [Using if-else Conditionals in a Makefile]() Original publisher: [Read original article]() Author: baeldung Published: 2025-06-06T09:36:00Z Content type: tutorial Language: en Sources: [Baeldung - Linux]() Topics: [make](), [Linux](), [Operating system](), [gcc]() Tags: [build](), [building](), [building-make-popular](), [code](), [examples](), [gcc](), [how-to](), [learn](), [linux](), [make](), [optimization](), [os](), [popular](), [programming](), [scripting](), [tutorial]() ### AI overview A tutorial explaining how to use if-else conditional directives in Makefiles. It covers ifeq, ifneq, ifdef, and ifndef, with examples for selecting compiler flags, handling operating-system differences, and assigning default variable values. ### Source excerpt Learn how to use if-else conditional statements inside of Makefiles. The post Using if-else Conditionals in a Makefile first appeared on Baeldung on Linux. Related Stories How to Identify the Package Manager of a Linux System Background Jobs in a Loop in Bash Executing Commands in Gnuplot through Shell Script ## Incident management tool integration DevFeed: [Incident management tool integration]() Original publisher: [Read original article]() Author: Kate Bernacchi-Sass Published: 2025-03-03T21:14:00Z Content type: tutorial Language: en Sources: [The incident.io Blog]() Topics: [incident management](), [incident](), [SRE](), [Monitoring](), [Slack](), [dashboards]() Tags: [code](), [connectors](), [dashboards](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [integration](), [integrations](), [make](), [monitoring](), [outage](), [post](), [post-mortem](), [slack](), [slack-incident](), [source](), [sre](), [tool](), [tools](), [workflows]() ### AI overview This guide explains how integrating monitoring, paging, chat, and ticketing tools can shorten incident response times, reduce repetitive work and burnout, and provide a single source of truth. It covers integrated workflows, practical implementation steps, measurement, and common pitfalls, with an Intercom example involving PagerDuty, Slack, and Jira. ### Source excerpt Incident response slows down when tools don't talk to each other. This post explains how integrating your incident management stack (from monitoring and paging to chat and ticketing) cuts response times, reduces burnout, and creates a single source of truth. Learn practical steps to quickly integrate key tools, avoid common pitfalls, and build workflows that help (not hinder) your team at 2 a.m. ## Docker Bake and Chainguard Images DevFeed: [Docker Bake and Chainguard Images]() Original publisher: [Read original article]() Published: 2025-02-13T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Docker](), [chainguard images](), [configuration](), [Development](), [YAML](), [JSON]() Tags: [bake](), [build](), [chainguard](), [chainguard-images](), [ci-cd](), [cli](), [configuration](), [declarative](), [docker](), [make](), [multiplatform](), [registry](), [variable](), [workflow]() ### AI overview This article introduces Docker Bake, a Docker CLI capability for defining, simplifying, and automating Docker build workflows with declarative files. It explains basic build definitions and shows how Bake can support multistage workflows with Chainguard Images, separate development and production targets, inheritance, multiplatform builds, registry pushes, and variables. Bake files can use HCL, YAML, or JSON, with HCL providing basic string-interpolation functions. ### Source excerpt Docker Bake is a great resource to define build configuration using a declarative file that integrates well with Chainguard Images. See how. ## RAG Trick: Embeddings are Spheres DevFeed: [RAG Trick: Embeddings are Spheres]() Original publisher: [Read original article]() Published: 2024-07-10T00:00:00Z Content type: tutorial Language: en Sources: [Tim Kellogg]() Topics: [Embeddings](), [Retrieval Augmented Generation (RAG)](), [Software Engineering]() Tags: [embeddings](), [make](), [model](), [rag](), [software-design]() ### AI overview This tutorial explains that normalized embeddings lie on a hypersphere and shows how that simplifies similarity calculations. It recommends dot product over other distance measures, notes that cosine similarity is equivalent for normalized vectors, and relates average embeddings to logistic regression. ### Source excerpt This post offers some helpful simplifications you can make when working with RAG or embeddings that help build a working mental model around them. Embeddings typically form a (hyper)sphere, because they're normalized. ## Adding Tailwind CSS to a Hugo blog DevFeed: [Adding Tailwind CSS to a Hugo blog]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2024-07-05T18:36:23Z Content type: tutorial Language: en Sources: [Kaushik Gopal's Site]() Topics: [Tailwind CSS](), [Hugo](), [CSS](), [make](), [Command-line interface]() Tags: [cli](), [css](), [how-to](), [hugo](), [installation](), [make](), [npm](), [tailwind]() ### AI overview A tutorial showing how to add Tailwind CSS v4 to a Hugo site using Tailwind CLI, including installation, CSS file setup, development commands, and a Makefile workflow for running or building Hugo and Tailwind together. ### Source excerpt Updated for Tailwind CSS V4 I veer away from CSS frameworks like Bootstrap because they result in sterilized designs. On a recent side project, I gave Tailwind CSS a try and am now a believer. "Rapidly build modern websites without ever leaving your HTML" makes a lot of sense to me. Case in point: I rebuilt my Hugo theme, Henry, with Tailwind in three days.1 I quite like how it's turned out. Let me show you how to add it to a Hugo theme. This has become even simpler with Tailwind CSS v4. Approach ## I like to keep things as simple as possible. So, it was important for me to use both Hugo & Tailwind as you would independently. I don't use Tailwind as a PostCSS plugin as much of the internet recommends. I prefer Tailwind CLI. Installation ## Let's assume you created your new site with hugo: hugo new site my-blog cd my-blog From this root hugo project directory: # create a package.json file (with default options) npm init -y # install Tailwind CSS as a dependency npm install -D tailwindcss @tailwindcss/cli Let's create the necessary css files for Tailwind to latch on to: mkdir -p my-blog/assets/css touch my-blog/assets/css/input.css touch my-blog/assets/css/theme.css I use the input.css file to help Tailwind wire everything together, and output.css is the final css that Tailwind compiles out. /* input.css */ @import "tailwindcss"; @import "./theme.css"; /* custom css you might want to add as overrides */ That's it! You can now fire up Tailwind & Hugo: # start tailwind npx @tailwindcss/cli \ -i ./assets/css/input.css \ -o ./assets/css/output.css \ --watch # start hugo server hugo server Bonus tip ### Starting Tailwind and Hugo separately in two different shells is a bore. I use a Makefile that conveniently allows me to spin up both processes in parallel. All I have to do when I'm ready to spin up my blog locally is: # runs the default comand which is "run" # it runs both taliwind css & the hugo server in parallel make Sometimes I want to just build the site, not run the ## 重新思考 Go：Channel 不是「消息队列」 DevFeed: [重新思考 Go：Channel 不是「消息队列」]() Original publisher: [Read original article]() Author: Joway Published: 2024-03-31T00:00:00Z Content type: opinion Language: zh Sources: [Random Thoughts]() Topics: [Go Language](), [Processes]() Tags: [cpu](), [csp](), [go](), [input](), [make](), [process](), [queue](), [tech]() ### AI overview This article argues that Go channels are designed primarily for communication and blocking coordination between goroutines, not as robust in-process message queues. It examines blocking when channels are full, uncontrolled consumer throughput, and the resulting pressure on core processing paths. The author concludes that using channels as queues can be a questionable technology choice and suggests a more complete standard-library queue implementation. ### Source excerpt 重新思考 Go 系列：这个系列希望结合工作中在 Go 编程与性能优化中遇到过的问题，探讨 Go 在语言哲学、底层实现和现实需求三者之间关系与矛盾。 Go 语言是一门为实现 CSP 并发模型而设计的语言，这也是它区别于其他语言最大的特色。而为了实现这一点，Go 在语法上就内置了 chan 的数据结构来作为不同协程间通信的载体。 ## Using Makefiles for software builds, Postfix map generation, and project workflows DevFeed: [Using Makefiles for software builds, Postfix map generation, and project workflows]() Original publisher: [Read original article]() Author: Tom Published: 2024-02-16T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [make](), [Hugo](), [Terraform]() Tags: [bash](), [build](), [compilation](), [configuration](), [dependencies](), [devops](), [devops-best-practices](), [environment-management](), [how-to](), [hugo-static-site-generation](), [learn](), [linux](), [macos](), [make](), [makefile-for-hugo](), [makefile-for-terraform](), [parallel](), [terraform](), [terraform-automation]() ### AI overview This tutorial explains how GNU Make manages dependencies, detects changed files, sets variables, and runs tasks in parallel. It also shows a Postfix use case for regenerating map files and alias databases from configuration files. ### Source excerpt Learn how to use Makefiles to streamline your Terraform and Hugo projects, making environment management and static site generation more efficient. ## My pre-commit config for Hugo blog DevFeed: [My pre-commit config for Hugo blog]() Original publisher: [Read original article]() Author: Tom Published: 2024-01-29T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [hooks](), [Hugo](), [Git](), [Optimization](), [make]() Tags: [bash](), [config](), [devops](), [git](), [git-pre-commit-configuration](), [hooks](), [how-to](), [hugo](), [hugo-blog-automation](), [hugo-development-tips](), [linux](), [macos](), [make](), [optimization](), [pre-commit](), [pre-commit-hooks](), [pre-commit-setup](), [static-site-optimization]() ### AI overview A tutorial showing how to configure pre-commit hooks for a Hugo blog. The configuration automates linting, syntax checks, file optimization, and related cleanup tasks when files are committed. ### Source excerpt Learn how to set up and use pre-commit hooks to automate tasks like linting, syntax checks, and optimizations for your Hugo blog. ## GNU/Hurd development updates from Q4 2023 DevFeed: [GNU/Hurd development updates from Q4 2023]() Original publisher: [Read original article]() Published: 2024-01-05T22:22:00Z Content type: news Language: en Sources: [GNU Hurd]() Topics: [gcc](), [Linux](), [CI/CD](), [Testing](), [qemu](), [x86](), [Kernel](), [make]() Tags: [continuous-integration](), [gcc](), [kernel](), [linux](), [make](), [qemu](), [testing](), [x86]() ### AI overview A quarterly update on GNU/Hurd development describes GCC and GNU Mach improvements, proposed continuous integration, expanded testing across environments, x86_64 build infrastructure, IPC changes, and efforts to improve browser support. ### Source excerpt Hello! Welcome to a new qoth. This qoth covers new and interesting GNU/Hurd developments in Q4 of 2023! Details. Samuel Thibault fixed gcc's Hurd's default pie and added static pie support. He also added a whatis command to GNU Mach's kernel debugger, which can determine what an address points to (a stack? a port? some kalloc? ...). He also added hurd-amd64 support to GCC. Samuel requested that the Hurd team set up a continuous integration, so that when developers make code changes, they can be certain that they did not break anything. It turns out that the Hurd supports several different environments: 32 bit, 64 bit, 32-on-64 bit, ACPI, non-ACPI, SMP, non-SMP, Xen, etc. Apparently Flavio has a personal CI, but it is set up in a Debian independent way. If you are interested in helping the Hurd project set up a CI, then please get in touch! Luca Dariz worked on adding some simple GNU Mach user-space tests . With a working MiG, a GNU/Linux machine can run make check in the GNU Mach source code, which will launch qemu to ensure that 32 bit (PAE and non PAE), 32 on 64 bit, and full 64 bit GNU Mach works. We currently do this testing on GNU/Linux, because qemu does not run on the Hurd. Many people worked on the Hurd's new x86_64 bit support. A 64-bit debian buildd is set up, and we can bootstrap a chroot! The hurd-amd64 wanna-build infrastructure is also set up. We are having issues reliably building packages on a 64-bit Hurd, which lead Samuel to uncover and fix a proc leak. Flavio Cruz improved GNU Mach's IPC by reordering mach_msg_type_t fields to byte align msgt_name and msgt_size. He also created a patch series to avoid message resizing for x86_64. He also removed untyped mach RPC code. GNU Mach uses typed IPC. The Hurd could support both typed and untyped, but it appears that the Hurd only uses typed RPC. So it seems best to remove any untyped RPC code. Sergey Bugaev added GNU Mach entry re-coalescing support. Essentially, Mach was not always able to merge two vm e ## Keep your Chainguard Images up to date with digestabot DevFeed: [Keep your Chainguard Images up to date with digestabot]() Original publisher: [Read original article]() Published: 2023-12-18T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [chainguard](), [GitHub Actions](), [Pull Request](), [Security]() Tags: [also](), [chainguard](), [chainguard-images](), [container](), [continuous-integration](), [digestabot](), [dockerfiles](), [github-action](), [helm](), [make](), [merge](), [oidc](), [security](), [vulnerability-automation](), [vulnerability-management]() ### AI overview Chainguard's digestabot is a free GitHub Action that helps keep Chainguard Images and other container assets current. It detects outdated image digests, opens pull requests, and supports testing and secure updates through continuous integration and optional ephemeral OIDC tokens. ### Source excerpt Experience hassle-free updates with Chainguard's digestabot, ensuring your Images stay secure and up-to-date daily. ## Secured #6 - Writing Robust C - Best Practices for Finding and Preventing Vulnerabilities DevFeed: [Secured #6 - Writing Robust C - Best Practices for Finding and Preventing Vulnerabilities]() Original publisher: [Read original article]() Author: Justin Traglia Published: 2023-11-02T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [C](), [Fuzzing/Fuzz testing](), [Library](), [Testing](), [Security](), [LLVM](), [make]() Tags: [c](), [ethereum](), [fuzzing](), [library](), [llvm](), [make](), [research-development](), [security](), [testing](), [vulnerabilities]() ### AI overview The article explains how Ethereum developers secured the c-kzg-4844 C library used by clients to compute and verify KZG commitments for EIP-4844. It covers LibFuzzer-based testing, differential fuzzing against go-kzg-4844, and coverage analysis with LLVM tools. ### Source excerpt For EIP-4844, Ethereum clients need the ability to compute and verify KZG commitments. Rather than each client rolling their own crypto, researchers and developers came together to write c-kzg-4844, a relatively small C library with bindings for higher-level languages. The idea was to create a robust and efficient cryptographic library... ## Making Twig Macros Work Like Functions DevFeed: [Making Twig Macros Work Like Functions]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2023-07-14T18:38:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Programming](), [Development](), [reusable code](), [Code]() Tags: [functions](), [insights](), [just](), [languages](), [learn](), [like](), [macros](), [make](), [manipulate](), [programming](), [programming-languages](), [return](), [returning](), [reusable-code](), [twig](), [value](), [values]() ### AI overview A tutorial on making Twig macros return values that can be manipulated like function results. It demonstrates a sales-calculation macro, whitespace control, and returning a value for further computations such as sales tax. ### Source excerpt Learn how to make Twig macros return values you can manipulate, just like functions in other programming languages ## Indexing by Custom Field in Craft CMS DevFeed: [Indexing by Custom Field in Craft CMS]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2023-06-28T17:13:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System](), [Database](), [migration]() Tags: [article](), [cms](), [content](), [craft](), [custom](), [custom-fields](), [database](), [fields](), [how-to](), [indexes](), [indexing](), [insights](), [learn](), [make](), [migration](), [performance]() ### AI overview A tutorial on adding database indexes for custom fields in Craft CMS through a content migration. It explains that Craft CMS does not automatically index custom fields, so queries filtering on those fields may not scale well as datasets grow. ### Source excerpt Learn how to make a content migration to add database indexes for custom fields in Craft CMS ## Automating customer usage alerts with Tinybird and Make DevFeed: [Automating customer usage alerts with Tinybird and Make]() Original publisher: [Read original article]() Author: David Margulies Published: 2023-05-01T00:00:00Z Content type: tutorial Language: en Sources: [Tinybird]() Topics: [make](), [Automation](), [Low code]() Tags: [automation](), [customer](), [i-built-this](), [low-code](), [make]() ### AI overview The article describes using low-code analytics and automation with Tinybird and Make to help a team become more proactive about customer usage alerts. ### Source excerpt Here's how I used "low-code" analytics and automation to help my team be more proactive. [Next page]()