# reproducibility Computational reproducibility is obtaining consistent results using the same data, computational steps, methods, code, and analysis conditions. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Why Agentic AI Challenges Traditional Enterprise Change Management DevFeed: [Why Agentic AI Challenges Traditional Enterprise Change Management]() Original publisher: [Read original article]() Author: flashdba Published: 2026-06-02T12:56:04Z Content type: opinion Language: en Sources: [flashdba]() Topics: [Artificial Intelligence](), [reproducibility](), [Testing](), [Deployment]() Tags: [agentic](), [agentic-ai](), [ai](), [cloud](), [databases](), [databases-and-agentic-ai](), [deployment](), [inferencing](), [performance](), [release](), [reproducibility](), [testing]() ### AI overview The article argues that enterprise change management depends on software behaving reproducibly. Agentic AI can produce different outputs from the same inputs, weakening the assumptions behind testing, UAT sign-off, approval gates, and rollback procedures. ### Source excerpt Enterprise change management was built around software that behaves reproducibly - and that assumption is load-bearing in ways that only become visible when agentic AI removes it. ## Using Dolt's Versioned SQL Database for Feature-Store Point-in-Time Reads DevFeed: [Using Dolt's Versioned SQL Database for Feature-Store Point-in-Time Reads]() Original publisher: [Read original article]() Published: 2026-05-15T00:00:00Z Content type: opinion Language: en Sources: [Alex Korbonits]() Topics: [feature-store](), [Git](), [reproducibility](), [Databases](), [SQL]() Tags: [dedupe](), [feature-store](), [git](), [reproducibility](), [rfc](), [row-number](), [sql](), [sql-database]() ### AI overview This article describes a prototype Feast offline-store plugin backed by Dolt, a version-controlled SQL database. It argues that Dolt's revision-based reads can provide point-in-time feature retrieval and reproducible training snapshots without the usual append-only log deduplication CTEs. Tests on toy datasets produced identical results with shorter queries, though the article presents this as an early spike rather than a production benchmark. ### Source excerpt A weekend spike asked whether Dolt's AS OF reads could replace the ROW_NUMBER dedupe at the heart of every feature store's point-in-time join. Four weeks later, the RFC is quiet and the plugin's get_historical_features works end-to-end against a live Dolt server. Notes on building anyway. ## Meet Guix at FOSDEM DevFeed: [Meet Guix at FOSDEM]() Original publisher: [Read original article]() Author: Ludovic Courtès Published: 2026-01-22T13:00:00Z Content type: article Language: en Sources: [GNU Guix -- Blog]() Topics: [FOSDEM](), [Package Management](), [reproducibility](), [systems]() Tags: [ci-cd](), [community](), [fosdem](), [guix-days](), [package-management](), [reproducibility](), [systems](), [talks]() ### AI overview The Guix community will participate in FOSDEM with talks on package management and reproducibility, bioinformatics workflows, Guile development, build systems, functional reactive programming, container images, and GNU/Hurd. About sixty Guix contributors will then gather for Guix Days on February 2-3. ### Source excerpt It's that time of the year again: next week is FOSDEM time! As in previous years , many Guix people will be in Brussels. Right after FOSDEM, about sixty of us will gather on February 2-3 for the Guix Days! First things first: Guix presence at FOSDEM. On Saturday, January 31st : In Name resolution in package management systems -- A reproducibility perspective , Gábor Boskovits will look will look at how several package managers refer to packages and how this affects reproducibility. Simon Tournier will... ## Nix Weekly Recap: 2024-02-25 DevFeed: [Nix Weekly Recap: 2024-02-25]() Original publisher: [Read original article]() Published: 2024-02-25T00:00:00Z Content type: article Language: en Sources: [nixpkgs.news]() Topics: [Nix](), [Development](), [reproducibility](), [Terraform](), [HackSquad]() Tags: [announcement](), [apt](), [community](), [google-summer-of-code](), [mentorship](), [prometheus](), [pull-requests](), [python](), [recap](), [repository](), [reproducibility](), [rust](), [terraform](), [weekly]() ### AI overview A weekly recap of announcements and repository activity in the Nix community, covering configuration visualization, reproducible HTTP/HTTPS responses for sandboxed builds, community funding, Typst support, Google Summer of Code participation, Terraform integration, Nix formatting, XR/AR/VR packages, and various package updates. ### Source excerpt Weekly recap of the announcements and activity in the Nix community and on the NixPkgs package repository. ## Farewell from the Reproducible Builds Summit 2023! DevFeed: [Farewell from the Reproducible Builds Summit 2023!]() Original publisher: [Read original article]() Published: 2023-11-02T00:00:00Z Content type: news Language: en Sources: [reproducible-builds.org]() Topics: [reproducible builds](), [reproducibility](), [builds](), [Embedded Systems]() Tags: [adb](), [apache](), [buildroot](), [builds](), [coreboot](), [debian](), [dockerignore-usage](), [fedora](), [germany](), [github](), [linux](), [maven](), [openwrt](), [org](), [reproducibility](), [reproducible-builds](), [security](), [summit](), [systemd](), [ubuntu]() ### AI overview A recap of the seventh Reproducible Builds summit in Hamburg, Germany, covering project updates, reproducibility practices, verification services, filesystem images and containers, package reproducibility, SBOMs, and related discussions. ### Source excerpt Farewell from the Reproducible Builds summit, which just took place in Hamburg, Germany: This year, we were thrilled to host the seventh edition of this exciting event. Topics covered this year included: Project updates from openSUSE, Fedora, Debian, ElectroBSD, Reproducible Central and NixOS Mapping the "big picture" Towards a snapshot service Understanding user-facing needs and personas Language-specific package managers Defining our definitions Creating a "Ten Commandments" of reproducibility Embedded systems Next steps in GNU Guix' reproducibility Signature storage and sharing Public verification services Verification use cases Web site audiences Enabling new projects to be "born reproducible" Collecting reproducibility success stories Reproducibility's relationship to SBOMs SBOMs for RPM-based distributions Filtering diffoscope output Reproducibility of filesystem images, filesystems and containers Using verification data A deep-dive on Fedora and Arch Linux package reproducibility Debian rebuild archive service discussion ... as well as countless informal discussions and hacking sessions into the night. Projects represented at the venue included: Debian, openSUSE, QubesOS, GNU Guix, Arch Linux, phosh, Mobian, PureOS, JustBuild, LibreOffice, Warpforge, OpenWrt, F-Droid, NixOS, ElectroBSD, Apache Security, Buildroot, Systemd, Apache Maven, Fedora, Privoxy, CHAINS (KTH Royal Institute of Technology), coreboot, GitHub, Tor Project, Ubuntu, rebuilderd, repro-env, spytrap-adb, arch-repro-status, etc. A huge thanks to our sponsors and partners for making the event possible: Event facilitation Platinum sponsor If you weren't able to make it this year, don't worry; just look out for an announcement in 2024 for the next event. ## Finding Non-determinism with nixbuild.net DevFeed: [Finding Non-determinism with nixbuild.net]() Original publisher: [Read original article]() Author: support@nixbuild.net Published: 2021-01-13T00:00:00Z Content type: tutorial Language: en Sources: [nixbuild.net blog]() Topics: [Nix](), [reproducibility](), [reproducible builds](), [builds](), [content addressed store]() Tags: [blog](), [blog-post](), [build](), [reproducibility](), [reproducible-builds]() ### AI overview This blog post explains how to use Nix repeated builds to detect non-deterministic outputs by comparing build results bit for bit. It also describes how nixbuild.net records repeated-build results and can help investigate failures from past builds. ### Source excerpt During the last decade, many initiatives focussing on making builds reproducible have gained momentum. reproducible-builds.org is a great resource for anyone interested in how the work progresses in multiple software communities. r13y.com tracks the current reproducibility metrics in NixOS. Nix is particularly suited for working on reproducibility, since it by design isolates builds and comes with tools for finding non-determinism. The Nix community also works on related projects, like Trustix and the content-addressed store. This blog post summarises how nixbuild.net can be useful for finding non-deterministic builds, and announces a new feature related to reproducibility! Repeated Builds The way to find non-reproducible builds is to run the same build multiple times and check for any difference in results, when compared bit-for-bit. Since Nix guarantees that all inputs will be identical between the runs, just finding differing output results is enough to conclude that a build is non-deterministic. Of course, we can never prove that a build is deterministic this way, but if we run the build many times, we gain a certain confidence in it. To run a Nix build multiple times, simply add the -repeat option to your build command. It will run your build the number of extra times you specify. Suppose we have the following Nix expression in deterministic.nix: let inherit (import {}) runCommand; in { stable = runCommand "stable" {} '' touch $out ''; unstable = runCommand "unstable" {} '' echo $RANDOM > $out ''; } We can run repeated builds like this (note that the --builders "" option is there to force a local build, to not use nixbuild.net): $ nix-build deterministic.nix --builders "" -A stable --repeat 1 these derivations will be built: /nix/store/0fj164aqyhsciy7x97s1baswygxn8lzf-stable.drv building '/nix/store/0fj164aqyhsciy7x97s1baswygxn8lzf-stable.drv' (round 1/2)... building '/nix/store/0fj164aqyhsciy7x97s1baswygxn8lzf-stable.drv' (round 2/2)... /nix/store/65 ## Searching for RH Counterexamples -- Deploying with Docker DevFeed: [Searching for RH Counterexamples -- Deploying with Docker]() Original publisher: [Read original article]() Published: 2021-01-04T09:00:00Z Content type: tutorial Language: en Sources: [Jeremy Kun]() Topics: [Docker](), [Containers](), [reproducibility](), [Database](), [Server]() Tags: [aws](), [containers](), [database](), [docker](), [mathematics](), [programming](), [pytest](), [reproducibility](), [riemann-hypothesis](), [server](), [software]() ### AI overview A tutorial on deploying an application that searches for counterexamples to the Riemann Hypothesis. It explains reproducibility and hermeticity, then uses Docker containers for the database, search application, and planned web server. ### Source excerpt We're ironically searching for counterexamples to the Riemann Hypothesis. Setting up Pytest Adding a Database Search Strategies Unbounded Integers In this article we'll deploy the application on a server, so that it can search for RH counterexamples even when I close my laptop. Servers and containers When deploying applications to servers, reproducibility is crucial. You don't want your application to depend on the details of the computer it's running on. This is a higher-level version of the same principle behind Python virtual environments, but it applies to collections of programs, possibly written in different languages and running on different computers. ## Reproducibility and Old Faithful DevFeed: [Reproducibility and Old Faithful]() Original publisher: [Read original article]() Author: Dominic Steinitz Published: 2018-02-25T09:49:10Z Content type: article Language: en Sources: [Maths, Stats & Functional Programming]() Topics: [reproducibility](), [data](), [dataset](), [R](), [Haskell](), [Nix]() Tags: [data](), [dataset](), [documentation](), [haskell](), [r](), [reproducibility](), [statistics]() ### AI overview This article investigates the provenance and reproducibility of the Old Faithful geyser datasets available in R. It compares the datasets with cited source tables, notes differing observation counts and apparent differences between versions, and reports that one dataset covers continuous observations collected from August 1 to August 15, 1985. The investigation uses Haskell, embedded R, data frames, and Nix. ### Source excerpt Introduction For the blog post still being written on variatonal methods, I referred to the still excellent Bishop (2006) who uses as his example data, the data available in R for the geyser in Yellowstone National Park called "Old Faithful". While explaining this to another statistician, they started to ask about the dataset. Since I ... Continue reading Reproducibility and Old Faithful