Aspen Smith

Even at the current default of 3 retries, I've lately been seeing this fail an *incredible* amount (I just had to rerun a build 5 times); error message looks something...

@keithduncan oh, to be clear, I don't view this as your fault at *all* - from what I can tell this is entirely AWS being super flaky (unless I'm misunderstanding...

Strong :+1: on this

here's the code that's currently *not* using the Entry API that it'd be nice to be able to use an Entry: https://github.com/glittershark/achilles/blob/master/src/tc/mod.rs#L527-L534 (`vars.0` is a bimap there). Essentially I'm just...

Only in rust-analyzer

Tried this without the `lsp-rust-analyzer-cargo-watch-args`, and the issue is still present. This is basically completely preventing me from using any recent version of rust-analyzer

that `bench` module issue is just a feature flag missing in our project, so not related to rust-analyzer

This is also not working for me using the AWS backend.

:+1: this is pretty huge for me. I love pry-byebug a lot but I can't use it locally since I have to test with Unicorn.

looking at the test failure, it kinda seems to me like the test might have been wrong all along? But I'm not familiar enough with the test to say that...