futures-batch
goblin
futures-batch | goblin | |
---|---|---|
3 | 3 | |
73 | 1,137 | |
- | - | |
0.0 | 7.2 | |
over 1 year ago | 7 days ago | |
Rust | Rust | |
Apache License 2.0 | 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.
futures-batch
-
Hey Rustaceans! Got an easy question? Ask here (52/2021)!
Is there any ready-made way of doing that or do I have to roll my own? I found futures-batch but I can't make it work with tokio channels. I feel like I'm missing something obvious.
- What's your favourite under-rated Rust crate and why?
-
Rust stream processor.
Might be helpful: https://github.com/mre/futures-batch
goblin
-
[ANN] yabridge 4.0, with chainloading, an overhauled backend, and many user experience improvements
On the backend side, a lot has changed. The biggest change is that the dependency on Boost has been completely removed, and everything has been reworked accordingly. This should make packaging easier, as yabridge now no longer depends on any system library other than the basic libraries needed to interact with X11. Some parts of Boost have been replaced by other headers-only libraries, while other parts now simply use custom implementations. All of this is explained in more detail in the 'Packaging notes' section of the changelog. Yabridgectl also lost its dependency on winedump, at least in most cases. It now tries to parse plugin libraries directly using the goblin binary parsing library. This should also speed up the syncing process. I did, however, run into one plugin that this new parser couldn't handle. If that happens then winedump will still be used instead.
-
Crash reporting in Rust
For now the minidump creation is a fairly faithful port of the Breakpad code, but like I said some of that code is really old, so there's probably cases where taking a step back and rethinking the approach based on new kernel or OS capabilities or, instead of recreating process snapshotting for each non-Windows, just have a really good parser for each OSes crash format that does a transform. Rust is a fantastic language for writing those kinds of parsers, so that would definitely be an interesting avenue to investigate, especially since in the Linux case a lot of groundwork has already been done by goblin.
-
What's your favourite under-rated Rust crate and why?
I do security-related projects in Rust, and goblin has been my go-to crate for any type of binary parsing (ELF/PE/Mach-O).
What are some alternatives?
retainer - Minimal async cache in Rust with support for key expirations
pwninit - pwninit - automate starting binary exploit challenges
fast-socks5 - Fast SOCKS5 client/server implementation written in Rust async/.await (with tokio)
autocxx - Tool for safe ergonomic Rust/C++ interop driven from existing C++ headers
sonyflake-rs - 🃏 A distributed unique ID generator inspired by Twitter's Snowflake.
eve-echoes-tools - Collection of tools helping in reverse engineering Eve Echoes
phpass - PHPass, the WordPress password hasher, re-implemented in rust
LIEF - LIEF - Library to Instrument Executable Formats
rumqtt - The MQTT ecosystem in rust
binary-security-check - Moved: https://codeberg.org/koutheir/binary-security-check
enum-map
netease-messiah-tools - Tools working with files in NetEase's Messiah Engine (Primarily aimed towards Diablo Immortal for now)