future-highway
future-highway
I agree with @dmah42 that we should mimic the underlying API, however, I was thinking of ways to have both. We could have, for example: ```proto message Cell { ......
I didn't remember the discussion either, but my agreement of having a way that is equal to the underlying API has to do with familiarity (for those that have it)...
Addressing this might be a good time to introduce the use of the [Richer error model](https://grpc.io/docs/guides/error/)
Looking for some clarification on 3... Should (a) every signal auraed receives be sent to every executable? Or are we saying (b) we want to add `rpc signal(CellServiceSignalRequest) ...` so...
Some context based on #194 The aurae-executables crate now has an `Executable` and a `NestedAurae` struct. `NestedAurae` uses `clone3` with the proper flags for unsharing the namespaces. In the context...
> > The aurae-executables crate now has an `Executable` and a `NestedAurae` struct. > > i don't understand why these are coupled into the same crate. they should be used...
I think it is appropriate to close this @krisnova. Our current setup is: 1. Use clone3 to start a nested auraed process with the appropriate namespaces unshared 2. Create a...
Glimpsing at the PR, it seems to only allow up to i64 (i.e., u64 would still not work). Need to test after the PR is accepted.
Reviewing the code as it is now, we are almost there. I think we can make this possible in 2 steps: 1. Create a 3rd variant on `CellState` called `Freed`...
#180 implements step 1 and step 2a.