Austreelis

I'm a bit confused: Why run `rustup toolchain install` when entering the shell, when rustup tools (including cargo) already install and use the toolchain specified by `rust-toolchain.toml` automatically ? As...

@rustbicycle (on discord) and me tested it, and the rustup-provided cargo (installed with the rustup package) does follow and automatically installs the right toolchain following appropriate rustup overrides as on...

I'm still encountering the same issue, albeit up from a few deciseconds with an empty list to about a second with a big list. Inputs correctly queue up but seems...

@ptruman I encountered the same issue, so I replaced `acme.json` with the following: ```json { "le": { "Account": { "Email": "[email protected]", "Registration": { "body": { "status": "invalid", "contact": [ "mailto:[email protected]"...

Oh this broke the test `error_on_nested_immediate_load_of_subasset` because it partly did what this PR tries to fix: It checks that we indeed get an error from the loader but cannot access...

I expected the conflict, I'll get around that tomorrow now :)

- rebased :3 - I've removed the forwarding of the inner error through `coore::error::Error::source()` because #19478 made it a `BevyError` which doesn't implements the trait. So the only change is...