dpc
Maybe I jumped to conclusions. After getting back to it and comparing logs between peers it seems more like just Peer-Id=3 dropped its message: `/tmp/devimint-3273235-123/logs/fedimintd-0.log` ``` 2024-03-29T18:12:41.445217Z DEBUG server::module::meta: Received...
Damn, it seems like log file numbers don't correspond to peer-ids ... :D
BTW. Sometimes something else gets stuck, but it's less common, so I'm focused on the common problem. I verified that the peer-3 does return right proposal from `fn consensus_proposal` -...
> Submitting something to consensus doesn't guarantee inclusion, so unless a "best effort" approach is sufficient here we can't delete the key until our submission was accepted. ``` } else...
Why is it always last peer (peer_id=3) that fails to deliver... ? And by always I mean "sometimes". But when it does, it's always that peer. It's not about the...
We had a call with @joschisan and it seems like we had a case of consensus round lockstep, which can be fixed with: https://github.com/fedimint/fedimint/pull/4846 Now everything passes consistently.
Conflict. Rebased.
> I wanted more typed api and more fine grain control to integrator of rpc, eventually I want to use this rpc in fedi app. > > the typed api...
For the record. We had a call with @maan2003 about this one. He punched me over the camera for being annoying. Just kidding, just kidding! We're going to make some...