Our great sponsors
rr | rrweb | |
---|---|---|
102 | 22 | |
8,621 | 15,553 | |
1.1% | 2.1% | |
9.6 | 8.3 | |
7 days ago | 6 days ago | |
C++ | TypeScript | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rr
- rr: Lightweight Recording and Deterministic Debugging
-
Hermit is a hermetic and reproducible sandbox for running programs
I think this tool must share a lot techniques and use cases with rr. I wonder how it compares in various aspects.
https://rr-project.org/
rr "sells" as a "reversible debugger", but it obviously needs the determinism for its record and replay to work, and AFAIK it employs similar techniques regarding system call interception and serializing on a single CPU. The reversible debugger aspect is built on periodic snapshotting on top of it and replaying from those snapshots, AFAIK. They package it in a gdb compatible interface.
Hermit also lists record/replay as a motivation, although it doesn't list reversible debugging in general.
- Rr: Lightweight Recording and Deterministic Debugging
-
Deep Bug
Interesting. Perhaps you can inspect the disassembly of the function in question when using Graal and HotSpot. It is likely related to that.
Another debugging technique we use for heisenbugs is to see if `rr` [1] can reproduce it. If it can then that's great as it allows you to go back in time to debug what may have caused the bug. But `rr` is often not great for concurrency bugs since it emulates a single-core machine. Though debugging a VM is generally a nightmare. What we desperately need is a debugger that can debug both the VM and the language running on top of it. Usually it's one or the other.
> In general I’d argue you haven’t fixed a bug unless you understand why it happened and why your fix worked, which makes this frustrating, since every indication is that the bug exists within proprietary code that is out of my reach.
Were you using Oracle GraalVM? GraalVM community edition is open source, so maybe it's worth checking if it is reproducible in that.
[1]: https://github.com/rr-debugger/rr
-
So you think you want to write a deterministic hypervisor?
https://rr-project.org/ had the same problem. They use the retired conditional branch counter instead of instruction counter, and then instruction steeping until at the correct address.
-
Is Something Bugging You?
That'll work great for your Distributed QSort Incorporated startup, where the only product is a sorting algorithm.
Formal software verification is very useful. But what can be usefully formalized is rather limited, and what can be formalized correctly in practice is even more limited. That means you need to restrict your scope to something sane and useful. As a result, in the real world running thousands of tests is practically useful. (Well, it depends on what those tests are; it's easy to write 1000s of tests that either test the same thing, or only test the things that will pass and not the things that would fail.) They are especially useful if running in a mode where the unexpected happens often, as it sounds like this system can do. (It's reminiscent of rr's chaos mode -- https://rr-project.org/ linking to https://robert.ocallahan.org/2016/02/introducing-rr-chaos-mo... )
-
When "letting it crash" is not enough
The approach of check-pointing computation such that it is resumable and restartable sounds similar to a time-traveling debugger, like rr or WinDbg:
https://rr-project.org/
https://learn.microsoft.com/windows-hardware/drivers/debugge...
- When I got started I debugged using printf() today I debug with print()
- Rr: Record and Replay Debugger – Reverse Debugger
-
OpenBSD KDE Plasma Desktop
https://github.com/rr-debugger/rr?tab=readme-ov-file#system-...
rrweb
- Rrweb, web session recording and replaying based on DOM changes and events
-
Show HN: Wirequery – Full-stack session replay and more
Interesting project!
How does this compare to rrweb[0], the library that Sentry and many other commercial offerings for frontend monitoring use?
[0]: https://www.rrweb.io/
-
Launch HN: Highlight.io (YC W23) – Open-source, full stack web app monitoring
Congrats on being the only commercial company to actually sponsor rrweb[0] rather than just fork it and contribute absolutely nothing back (or in the case of Sentry - remove their copyright and violate their license).
Seeing as you're "open-source", why chose to fork and detach the project rather than contribute directly to it? With a detached fork, other users can't even compare your changes to the original and pull in fixes. If you truly believed in the spirit of open source, you'd believe in working together and giving back, not just taking advantage of a free lunch.
It feels like all these "open-source" companies are just closed source but with open-source as a marketing gimmick.
[0] https://github.com/rrweb-io/rrweb
-
New website and no sales.
if you want I can help to install www.rrweb.io free, DM me
- Show HN: We’re open-sourcing Requestly- HTTP debugging proxy for Web and Mobile
- FLiPN-FLaNK Stack Weekly 27Feb2023
-
Making YouTube video with React
In the end, I had to experiment quite a few times. First, I tried using rrweb since it was something that was already on my radar. The idea is I would record using that and convert it into a video using rrvideo.
-
Show HN: We’re open-sourcing our session replay tool
I didn't think postHog was a good comparison either,
I knew of rrweb https://www.rrweb.io/
Great to see more open source contendants in the space
-
Mighty is shutting down after 3.5 years
(something like https://www.rrweb.io/)
I'm indie/solo making Linkkraft browser (to make a living from it). Browser to be effective researcher & collector. It visualizes your steps as tree and makes html snapshot for your each step (even steps in SPAs like twitter).
- Ask HN: How does software such as rrweb and OpenReplay work?
What are some alternatives?
CodeLLDB - A native debugger extension for VSCode based on LLDB
openreplay - Session replay and analytics tool you can self-host. Ideal for reproducing issues, co-browsing with users and optimizing your product.
gef - GEF (GDB Enhanced Features) - a modern experience for GDB with advanced debugging capabilities for exploit devs & reverse engineers on Linux
react-use-hotjar - Adds Hotjar capabilities as custom hooks such as init, identify and stateChange
Module Linker - browse modules by clicking directly on "import" statements on GitHub
dark - Darklang main repo, including language, backend, and infra
nbdev - Create delightful software with Jupyter Notebooks
Requestly - 🚀 Most Popular developer tool for frontend developers & QAs to debug web and mobile applications. Redirect URL (Switch Environments), Modify Headers, Mock APIs, Modify Response, Insert Scripts & Record web sessions and share it with your teammates for debugging.
clog-cli - Generate beautiful changelogs from your Git commit history
highlight - highlight.io: The open source, full-stack monitoring platform. Error monitoring, session replay, logging, distributed tracing, and more.
rustfmt - Format Rust code
re-frame-10x - A debugging dashboard for re-frame. X-ray vision as tooling.