Reactor Scram
Reactor Scram
Making `Session` into a channel / notification thing would be nice. Then we can ditch the callbacks and have better error handling. Moving crates around will cause merge conflicts and...
.. true, me too. There's just been a lot of refactors and 1,000+ line diffs this month and it's even worse if it means I have to handle a conflict...
Sounds good. Guess who else had a random full channel issue exactly once? https://github.com/firezone/firezone/issues/5880
3 minutes for `sadness-generator` would be really surprising (and hilarious). `--timing` on the Windows 11 aarch64 VM is saying 0.3 seconds to compile it.
@Patticatti Thoughts as far as UX? Right now the flow is: - Open the logs tab - Click Export - Find a place to save the zip - Click Save...
I think because of the IPC split they're in two totally different directories now. The GUI process logs to the user's home dir, and the Tunnel services logs to `C:\ProgramData`...
It shows up correctly in local builds, at least sometimes. At least on Ubuntu Linux. Could it depend on the Git version or something? Even as recent as 1.3.9 it's...
#7202 should have fixed this when it merged
Even on CPU inference I can't get any determinism from the example server at all: ``` $ for x in `seq 5`; do curl -s -X POST --url http://localhost:8080/completion --header...
I could check it out as long as I'm here. I found the directions to run the CI locally, is there anything else I should do to test a patch?...