Rich Brown

@eitsupi Thanks for #5133. Since you were just looking at this area ov `prqlc`, I wonder if the proposal above might be related (or perhaps you could give a judgement...

Here's where it stops: (Again, I apologize that I don't know much about the node compilation environment for prqlc. I'm happy to provide more info as needed...) ``` vscode ➜...

@max-sixty @eitsupi Sorry for the delayed response. Same error with a slighly newer commit... I included the entire log file. ``` vscode ➜ /workspaces/prql (main) $ git log commit 9206f53d5b3dc8382e1724cf0b249d86b6cc981a...

@max-sixty - other oddness - `cargo clean` gives an os error 16. I have tried removing all containers, images, volumes, and Docker caches with no change to the underlying error...

Closing in favor of an updated report at #5007

SOLVED: See #5018

> In fact, now mini PCs using Intel N100 CPU is so cheap... We're network testing nerds, who have lots of hardware lying around that we can throw into the...

>> I just realized that it might be possible to measure both "WiFi bloat" and "ISP bloat" > > You can only measure one of them in a single test....

> The latency peer measures latency from itself to the server, in addition to the regular client to server latency measurement. OK, now I understand. How had you envisioned that...

I had not thought of that. For clarity, let me see if I understand what the Latency peer does: - The Crusader client instructs a Latency Peer to begin measuring...