Urgent.News

What's breaking now, across thousands of outlets.

Tech

I built Rewind: A zero-dependency TIME-TRAVEL DEBUGGER with live in-browser hot-patching (Open for Contributions)

Debugging modern applications is still surprisingly painful. Whether you're building a Python data pipeline, a Node.js microservice, or a Go API, debugging usually boils down to two tedious options: Littering your codebase with console.log() / print() statements and re-running everything. Stepping forward line-by-line in a traditional debugger, accidentally skipping past the exact mutation that…

Rewind is an innovative, open-source universal time-travel debugger that enables developers to debug any codebase without dependencies. It provides sub-microsecond state diffing and an interactive in-browser hot-patching feature for live code adjustments. Designed with three key principles, Rewind offers universal multi-runtime tracing, enabling Python scripts to auto-trace without changes, or wrap any command, service, or server across languages.

Its sub-microsecond circular state diffing prevents memory bloat and circular reference issues, while the in-browser time scrubber and live hot-patching allow developers to directly edit source code and test fixes in memory. Built on standard library primitives, Rewind requires no external dependencies or daemon setups. To get started, simply clone the repository, install dependencies, and test on a multi-step pipeline bug.

Contributions to enhance Rewind are encouraged, and the project is open-source under the MIT license.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

The three-state dark mode toggle is the correct answer

An application should not take away the decision a user has previously selected. That is the main point of the argument. All other details are insignificant.

  • Three-state dark mode toggle proposed as solution
  • Addresses time-of-day bug in two-state toggles
  • Adopted by GitHub, StackOverflow, CodePen

Your zero-downtime deploy is probably fine. Check your p99 before you believe it.

I went looking for dropped requests during a rolling restart and found something more annoying than dropped requests: a deploy that looks perfect and isn't. Setup is deliberately boring.

  • Zero-downtime deploy may appear successful but can fail during process.
  • Lack of signal handling in Node/Express app causes mid-flight requests to die.
  • Monitoring p99 latency, not just error rates, crucial to detect deploy issues.

More from Sunday 6 September →