Andras Slemmer

There **is** a way to do this. In our project we've been using a home-rolled 2-phase build solution until a couple of weeks ago when we switched to naersk, and...

Use `copySources` for adjacent crates

`copySources` is a list of relative paths to folders, relative to `src` (or optionally you can also specify `copySourcesFrom`). naersk when constructing the base source folder (both for the dependencies...

Generally speaking it's best if you point `src` to the "top-level" folder and specify relative paths (strings) with `copySources`. Otherwise if you specify proper nix paths like `./../foo` that will...

The logic is described here: https://github.com/nix-community/naersk/blob/94beb7a3edfeb3bcda65fa3f2ebc48ec6b40bf72/lib.nix#L187 So for each `p` in `copySources`, naersk copies the sources from `$copySourcesFrom/$p` to `$out/$p`. `copySourcesFrom` in return may either be specified directly, or it...

This would be super cool. I think rust async is a bit harder to tackle than goroutines because the low-level machinery is not standardized. But already for sync code it...

I'd recommend looking at the `nitro-cli-config` logic for allocating enclave CPUs, in particular the following function and its comment: https://github.com/aws/aws-nitro-enclaves-cli/blob/8f6ed740b05225512d86163f8b02292668c4b056/bootstrap/nitro-cli-config#L544-L549 So, vcpu 0 must be retained for host usage +...

We had a similar problem. We're using `nix` for reproducible builds, and Dockerfiles+daemon builds don't play well with the build sandbox (and the resulting images are also not reproducible). Thankfully,...

I tried it with Quasar `0.7.9` and Kotlin `1.1.51` and it does the same. Note that this requires instrumentation verification on (`-Dco.paralleluniverse.fibers.verifyInstrumentation=true`)

The main issue is third party libs doing thread-local caching. An example would be netty using threadlocals to store buffers