mycoliza

7 ms·

1.
by mycoliza 1mo ago
there are even images of it on our website!
2.
by mycoliza 11mo ago
In reply to your edit, that section in the RFD includes a link to the full example in the Rust playground. You’ll note that it does not make any use of ‘select!`: https://play.rust-lang.org/?version=stable&mode=debug&amp
3.
by mycoliza 11mo ago
An analogous problem is equally possible with streams: https://rfd.shared.oxide.computer/rfd/0609#_how_you_can_hit_...
4.
by mycoliza 11mo ago
> No, just have select!() on a bunch of owned Futures return the futures that weren't selected instead of dropping them. Then you don't lose state. How does that prevent this kind of deadlock? If the owned future has acquired a
5.
by mycoliza 11mo ago
Indeed, you are correct (and hi Matthias!). After we got to the bottom of this deadlock, my coworkers and I had one of our characteristic "how could we have prevented this?" conversations, and reached the somewhat sad conclusion t
6.
by mycoliza 11mo ago
Yeah, a coworker coming from Go asked a similar question about why Rust doesn't have something like the Go runtime's deadlock detector. Your comment is quite similar to the explanation I gave him. Go, unlike Rust, does not really
7.
by mycoliza 11mo ago
As a member of (Eliza, Sean, John, and Dave), I can second that debugging this was certainly an adventure. I'm not going to go as far as to say that we had fun , since...you can't have a heroic narrative without real struggle. Bu
8.
by mycoliza 11mo ago
We actually don't use Rust async in the embedded parts of our system. This is largely because our firmware is based on a multi-tasking microkernel operating system, Hubris[1], and we can express concurrency at the level of the OS sch
9.
by mycoliza 11mo ago
What could `tokio::select!` do differently here to prevent bugs like this? In the case of `select!`, it is a direct consequence of the ability to poll a `&mut` reference to a future in a `select!` arm, where the future is not dropped sh
10.
by mycoliza 1y ago
As an Oxide employee, let's just say...it does, and it is :)
11.
by mycoliza 2y ago
We also sell computers... :)
12.
by mycoliza 2y ago
The big piece of copper is fed by redundant rectifiers. Each power shelf has six independent rectifiers which are 5+1 redundant if the rack is fully loaded with compute sleds, or 3+3 redundant if the rack is half-populated. Customers who w
13.
by mycoliza 2y ago
We write the security mitigations. We patch the CVEs. Oxide employs many, perhaps most, of the currently active illumos maintainers --- although I don't work on the illumos kernel personally, I talk to those folks every day. A big part
14.
by mycoliza 2y ago
We did it as a result of my suggestion, and I'll freely admit that it does seem pretty goofy! The motivation, though, was that we wanted to write tests for the function that would run on a developer's machine using `cargo test`, a
15.
Maitake-sync: async synchronization primitives for no-std Rust(elizas.website)
3 points by mycoliza 3y ago|0 comments
16.
by mycoliza 4y ago
in my use case (a hobby project; https://github.com/hawkw/eclss ), the device and Prometheus are on the same LAN and i have Prometheus set up to discover scrape targets using multicast DNS. this is…probably not what you
17.
by mycoliza 4y ago
hi, i wrote this thing! if you’re wondering why it’s weird, half-finished, or under-documented, it’s because i wrote it in a couple hours to scratch my own itch, and really didn’t expect to be at the top of hackernews today! if this is some
18.
by mycoliza 5y ago
A lot of the Tokio console UI was inspired by `htop`, which provides a pretty similar overview of processes and threads. It doesn't really have the same ability to inspect things like `pthread_mutex` and timerfds etc in the same way th
19.
by mycoliza 5y ago
It's https://typeof.net/Iosevka/ (I took the screenshots).
20.
by mycoliza 5y ago
Yes, we've designed the overall architecture of the system to be modular so that the telemetry can be consumed by a number of different UIs --- we'd love to see someone write web interfaces and/or native GUIs for the console
21.
by mycoliza 5y ago
At my day job ( https://buoyant.io/ ), we're using it to write a reverse proxy/load balancer --- one of the use-cases where you really, absolutely do need asynchronous concurrency. :)
22.
by mycoliza 5y ago
Go has pprof ( https://github.com/google/pprof ), which I've heard good things about --- and, the pprof data model was one of the influences I looked at when designing the Tokio console's wire format. But, I&#x
23.
by mycoliza 5y ago
Yeah, currently, the console knows how to detect TrueColor, but in this case, I just used the ANSI 256 palette rather than picking a better one when TrueColor is available...we should probably fix that! Side note, it turns out that detect
24.
by mycoliza 5y ago
Thank you, that's really nice to hear!
25.
by mycoliza 5y ago
Something like that would definitely be useful! It's not really in scope for this project, which is intended as a telemetry and diagnostics tool, but I can imagine a Rust REPL being useful. Of course, in order to do that, you'd ne
26.
by mycoliza 5y ago
Tokio is a non-profit, community-supported project, although many of us work on it as part of our day jobs. If you want to support Tokio development, you can contribute to it on GitHub Sponsors ( https://github.com/sponsors&#
27.
by mycoliza 5y ago
Yeah, the goal is for `valuable` to replace `tracing`'s (currently much more limited) `Value` trait entirely, when we release `tracing` 0.2. Before making a breaking change, though, we want to release opt-in support for `valuable` in t
28.
by mycoliza 5y ago
(primary author of the console here) you're right that there are too many digits of precision right now...the reason for that is that it's actually _not_ a thoughtful design at all, though I appreciate you saying that it is; I jus
29.
by mycoliza 5y ago
Hi, I'm one of the main authors of `tokio-console`, so if folks have any questions, I'm happy to answer them!
30.
by mycoliza 6y ago
Rust is intended as a systems programming language, it's for people who are writing "the next nginx". It turns out that there are also a bunch of people who want to write webapp servers in Rust, too, but that's never r

More ›