<gchristensen>
one of the evaluators reliably fails to start with "thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Protocol("the handshake was interrupted: A read attempt return..." how annoying
<LnL>
:/
<gchristensen>
oh, lol
<gchristensen>
its in Sydney
<gchristensen>
maybe the connection startup code in the amqp lib handles slow connections at start poorly
jtojnar has quit [Read error: Connection reset by peer]
jtojnar has joined #nixos-borg
andi- has quit [Ping timeout: 276 seconds]
andi- has joined #nixos-borg
FRidh has quit [Quit: Konversation terminated!]
FRidh has joined #nixos-borg
<LnL>
killing the eval doesn't look super hard
<LnL>
would be much nicer with futures tho :p
<gchristensen>
do it
<gchristensen>
let's start moving to futures
<andi->
use the old futures crate unless they finally stabilized the new version. IIRC 0.2.x was just an itermediate WIP version with broken stuff.
<gchristensen>
ok then maybe don't do it haha
<andi->
The work there is moving towards support of the await/async language features
<andi->
Thats supposed to land sooon? (this month?)
<LnL>
I don't think 0.2 is a thing, is it?
<gchristensen>
check it out, LnL, if it looks good, let's do it
<gchristensen>
I like Rust. I'm not going to quit it even though I don't like futures :)
<gchristensen>
(which means better get living with it)
FRidh has quit [Quit: Konversation terminated!]
<LnL>
I got distracted again... :p
<gchristensen>
I wonder if I can make nixops use a pure-eval mode :evil: