Failing Tests as Merge Tokens: A Reproducible Patch Loop for OSS Contributors

·1 views

A proposed contributor workflow for open-source projects argues that every patch submission should begin with a failing test that concretely reproduces the reported bug, rather than a code diff alone. The approach centers on a small machine-readable file, repro.json, stored alongside the test suite to bind a specific bug claim to a runnable command. Contributors first confirm the test fails on the main branch, then make the minimal production code change needed to make it pass on a dedicated fix branch. The method is designed for small OSS libraries and command-line tools, and intentionally limits AI-generated text to code review rather than authoring production patches. Maintainers are encouraged to reject pull requests that lack such a hermetic, self-contained reproduction step.

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)

Developer Builds Local Markdown Vault to Carry Personal Context Across AI Tools

A developer created SelfContext after growing frustrated with having to re-explain personal history, goals, and past decisions at the start of every new AI session. Existing solutions like provider memory, chat history, and note folders failed to reliably retain the context that actually mattered. SelfContext is a local layer of plain Markdown files paired with skills that instruct an existing AI agent to ingest, retrieve, and maintain that context over time. The vault runs entirely on disk with no proprietary server, database, or custom interface, making it portable across different AI tools and harnesses. The project distinguishes between what the user said, what sources stated, and what the model inferred, keeping all inferences reviewable so AI suggestions cannot silently overwrite personal goals or preferences.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Tailscale: A WireGuard-Based Mesh VPN That Needs No Port Forwarding

Tailscale is a mesh VPN built on WireGuard that creates a private network, called a tailnet, across a user's devices without requiring a central server to route traffic. Devices connect directly and securely to each other, with Tailscale's infrastructure only facilitating the initial connection negotiation. The service works automatically through NAT and firewalls, and includes features like MagicDNS for stable hostnames, AirDrop-style file transfers, and identity-based SSH access. A free tier is available for personal use and is popular among hobbyists for self-hosting applications such as Nextcloud or Home Assistant. Getting started requires only installing the client on two devices and signing in with an existing account from providers like Google or GitHub.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Agent Memory's Core Flaw: Notes Are Written Before Questions Exist

A technical analysis published on DEV Community argues that poor agent memory notes are not a matter of effort or prompt quality, but a structural design flaw. At the time a note is written, the future queries it must serve do not yet exist, making write-time precision fundamentally undefined rather than merely difficult. The piece draws on a 1960s information-science concept called anticipatory indexing, attributed to Robert Fairthorne, to show this problem predates AI agents. Unlike demand forecasting, note writing offers no recurring feedback signal against which a writer's output can be measured or improved. The author concludes that the solution is not a better writing process but a different unit of storage altogether.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Five Windows DIR Command Flags That Make File Searches Faster

The Windows DIR command, run in Command Prompt, lists files and folders in the current directory along with their size and last write time. Several switches extend its usefulness beyond basic listing: /a reveals hidden and system files, while /s recursively searches through subfolders using a filename pattern. The /b flag outputs bare filenames with no headers, making it ideal for piping results into scripts, and /o: allows sorting by name, date, or size without touching a mouse. Combining flags — such as dir /b /s /o:-d *.dll — lets users retrieve targeted, sorted file lists in a single command. Microsoft's official DIR reference on Microsoft Learn provides the complete list of available parameters for deeper exploration.

0 comments Read more at DEV Community