l0k1
l0k1
There is also a method for building an ultra-slim container for running Go applications, it involves starting first with a full build and then it rips out everything except what...
Is there any specific hints for conditions that trigger this or does it always happen once everything is up and running?
Looking over the `Makefile` I have just become aware there is no option in there for non-test builds with the race flag on. But I can also immediately see from...
I have now replicated the problem, and I can see that indeed the issue comes from there being only one logger created in the signal package and two goroutines using...
> Sorry for the late feedback, I should have commented on #5402 earlier. > > I think we want to keep the protos in the same place as they currently...
> Sorry for the late feedback, I should have commented on #5402 earlier. > > I think we want to keep the protos in the same place as they currently...
> Please also make sure that `make check` runs correctly on your machine. As part of this, I have set up and am syncing bitcoind and btcd on my machine....
I can clear all the linting errors, most of them were nothing I did but happen to be all within the new `rpcservers` folder and don't have many effects outside...
> You don't need to have any node synced as the tests all run on a separate regtest network anyway. So just having the binaries installed should be enough for...
> Did you install a version of `bitcoind` with ZMQ support enabled? oh, that's not default? I built it from source ofc. I'll fix that now. Yes, it passes all...