Our great sponsors
rumqtt | rr | |
---|---|---|
34 | 102 | |
1,473 | 8,621 | |
4.4% | 1.1% | |
8.9 | 9.6 | |
5 days ago | 7 days ago | |
Rust | C++ | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
rumqtt
-
New scalable, fault-tolerant, and efficient open-source MQTT broker
https://github.com/bytebeamio/rumqtt
Disclaimer: have not tried it myself. I was, however, considering using it to replace Mosquitto as a broker.
-
What MQTT crates for use in WASM are out there?
Other crates like https://crates.io/crates/paho-mqtt and https://github.com/bytebeamio/rumqtt are not available for browsers and do not compile to wasm.
- Announcing rumqttd v0.18.0: with improved performance and reduced binary size due to enhanced release profile, while featuring retained and will messages, will delay interval for MQTTv5 and other cool changes!
- Announcing rumqttd v0.17.0 with Shared Subscriptions and Subscription IDs adding up to better MQTTv5 support!
-
rumqttd now supports QoS2 and MQTT over websockets
Recently lot of new contributors showed interest, as well as contributed to rumqtt, so thank you so much everyone for your support <3 Feel free to discuss anything in comments, if you wish to contribute as well, you can look for `good-first-issues` ( or open new issues here )
- Rumqttd now supports MQTTv5 topic alias and message expiry
-
Announcing rumqttd v0.15.0 with MQTTv5 features like Topic Alias and Message Expiry
GitHub release - rumqttd-0.15.0
-
rumqttc 0.21.0 released with MQTT5 support
there is already an issue open for it: https://github.com/bytebeamio/rumqtt/issues/432. It is something that we would love to have, but not something in priority.
I wanted to let you know that rumqttc, a Rust MQTT client library, now supports several new features in MQTT 5 protocol. If you're not familiar with MQTT, it's a lightweight messaging protocol designed for IoT devices with limited resources.
-
Hey Rustaceans! Got a question? Ask here (15/2023)!
I know I should have asked this in their issues, but someone already did and didn't get a response. So I was not sure whether to create another issue, or comment in the same one (and not get a response as well?). So I decided to ask on Reddit first, thank you! https://github.com/bytebeamio/rumqtt/issues/598
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-...
What are some alternatives?
ntex-mqtt - MQTT Client/Server framework for v5 and v3.1.1 protocols
CodeLLDB - A native debugger extension for VSCode based on LLDB
mqtt-broker - A tokio-based MQTT v5 broker written in pure Rust [WIP]
rrweb - record and replay the web
mqtt-rs - MQTT protocol library for Rust
gef - GEF (GDB Enhanced Features) - a modern experience for GDB with advanced debugging capabilities for exploit devs & reverse engineers on Linux
mosquitto - Eclipse Mosquitto - An open source MQTT broker
Module Linker - browse modules by clicking directly on "import" statements on GitHub
futures-batch - An adapter for futures, which chunks up elements and flushes them after a timeout — or when the buffer is full. (Formerly known as tokio-batch.)
nbdev - Create delightful software with Jupyter Notebooks
lora-rs - LoRa and LoRaWAN crates for End Devices
clog-cli - Generate beautiful changelogs from your Git commit history