remleduff

Sure, but that captures the screenshots again pointlessly, doesn't it? The "current" directory is going to be identical after these two invocations of loki.

My goal is that step one just verifies that the reference are up to date (it generates "current" and fails if "current" is different from "references") Step 2 is just...

I've been looking at this layer lately, and ran across a similar problem. The quickest, but maybe not most correct fix is to change meta-rust/recipes-devtools/rust/libstd-rs.inc: from: S = "${RUSTSRC}/src/libstd" to:...

This could potentially be fixed by https://github.com/oblador/loki/pull/478

If you're running docker-in-docker, it'd be worth checking if https://github.com/oblador/loki/pull/478 helps. Particularly the timeout for 127.0.0.1 seems similar to the error I was seeing.

I'll look into this, I'm interested at least. My thought is to basically switch the code after the fork call, and make the child start the payload, and the parent...

> Haha, I did the exact same thing. It went like this: > > 1. "WOW, this script running thing is AMAZING!!!!" > 2. "Wait... but now VSCode has no...

You've probably seen this already, but Windows 10 has been making large changes (improvements) to console handling. Is it better to have a wait-and-see attitude on this one, and just...

@KevinVandy Do I need to do anything for this? It seems like the automated fixes are correct, but when I click through to the workflow its status is "failed".