Glauber Costa

I suspect some resource exhaustion is behind the other two tests hanging as well. The placement one, in particular, the only blocking operation it is doing is starting threads.

Thanks. this makes it pretty obvious what is going on. The code assumes that the core IDs exposed by the system are global. But they are not. You will see...

I would also love to understand why the `physical_package_id` is zero in this system =(

Hey Andrey, When I wrote `read_at` and friends I did try to have an API that would take a buffer, and also tried to create traits around our buffers. So...

Thanks @artemyarulin . Adding @shikhar who wrote the original commit. I will be able to take a look at it myself in a couple of days as well

This code is fishy, and I think I may have fixed it by accident (while fixing something else) after 0.6.0 @artemyarulin would you be able to try and reproduce this...

I will reopen because I want to release 0.6.1 with this fix. The next version will change the API considerably in some areas.

I don't immediately see value in an API that is used to just request a stop. The reason for that, is that the way the executor works is exactly that...

In this example you need the file to be kept alive in two places: the shutdown handler, and the normal file operations (since there is no clear way of knowing...

Thanks @thirstycrow . I reproduced this, and I will hunt where this is coming from. Leave this to me. To set expectations, I am about to enter paternity leave so...