Mathias LANG
Mathias LANG
We should probably use an approach similar to https://github.com/bosagora/agora/commit/77f12a93b10791f8135fe3d15ff2904494060789
Hasn't happened in a while.
This hasn't happened in a while so we probably solved it in one of the CI stabilization PR.
> I have seen this happen right after `VariableBlockSize` multiple times I don't think it's related to `VariableBlockSize` itself, but more to what `VariableBlockSize` is: It's the very first network...
If you guys can update the vibe.d fork to match what's on master that's one we can easily cross off.
Context: https://github.com/bosagora/faucet/blob/834e16342aa5699ded55b90425734012e8135276/source/faucet/main.d#L535 Prints: ``` Feb 11 05:57:13 eu-001.bosagora.io docker[73427]: 2022-02-11 05:57:13,329 Info [faucet.main] - Sending 400000000000 BOA to boa1xz3qed5979y0v0mjjsndh5lcjmyvp9hrcsu78qs4mjw8gugqnkxx25e3qfd ``` Which is wrong, it's sending 400000000000 (400,000,000,000) units, which is...
Upstream: https://github.com/vibe-d/vibe.d/issues/2642
What I was actually thinking about is expose an UNIX socket that would allow one to directly interact with the nodes. This would also allow us to control nodes, e.g....
For the moment this should be added to the admin interface. One example is that we can now dynamically reconfigure loggers: https://github.com/bosagora/agora/blob/2809791954133da4c352d612d7347ee667e65312/source/agora/api/Admin.d#L30-L42