How I work on bug fixes:
1. Reproduce it first
2. Write a test that fails
3. Fix the root cause, not the symptom
4. Run the project's own lint and test suite before opening the PR
6 PRs merged across TypeScript and Python open-source projects this month. Available for TypeScript, Next.js/Supabase and Python work.
Small bugs are worth fixing properly. In openrig, resetting a config value left empty parent objects behind in the config file. It was harmless until the file filled up with {} noise.
Fixed the cleanup and added tests so it stays fixed. Merged.
https://github.com/mvschwarz/openrig/pull/1638
github.com
fix(cli): prune empty parent objects after config reset by arxh80 · Pull Request #1638 · mvschwarz/openrig
Summary Fixes rig config reset <key> leaves empty parent objects in the config file #1620: rig config reset <key> deleted the key but left now-empty parent object literals in the confi…
Two PRs merged into docling-pipelines: the Dropbox and Box connectors can now process a single file when a change event arrives, instead of re-scanning the whole folder.
Input validation, unit tests and docs included.
https://github.com/docling-project/docling-pipelines/pull/348
Building GetSetPaid, a CRM for the UK live-events industry: promoters, venues, agents, artists and suppliers.
Every company gets a private workspace, and the isolation lives in the database itself (Postgres Row Level Security), not just in app code. There are tests that try to...
Fun bug from this week: a JSONPath tool was quietly dropping digits from large numbers. You'd query 12345678901234567890 and get back something close, but wrong.
The cause: JSON gets parsed into JavaScript numbers, which can't hold that many digits exactly. The fix keeps...
